m204wiki - User contributions [en]

M204wiki main page

2017-09-11T15:28:30Z

Glw:

Welcome to M204wiki, the platform for Rocket Software Model 204 technical documentation. Here you can find product information, installation and reference documentation and release notes.

M204wiki contains the current version of Model 204 documentation, with release-specific features noted in the text. In some cases, documentation is provided in [[Model 204 documentation|PDF format]].

In addition to plentiful page links, [[Searching M204wiki|M204wiki searching features]] help you quickly locate the information you need.

__TOC__

==Model 204==
<dl>
<dt>Installation
<dd>[[Model 204 installation]]

<dt>Introductions to core Model 204 areas
<dd>[[SOUL|SOUL/User Language]]
 [[File management overview|File management]]
 [[File architecture overview|File architecture]]
 [[Model 204 configurations and operating environments|System management]]

<dt>Commands
<dd>[[List of Model 204 commands]]

<dt>Parameters
<dd>[[List of Model 204 parameters]]

<dt>Security
<dd>[[Model 204 security features]]
 [[Storing security information (CCASTAT)#Overview|Storing security information (CCASTAT)]]
 [[:Category:Security interfaces|Security interfaces]]
 [[Janus Network Security]]

<dt>PDF manuals
<dd>[[Model 204 documentation|Model 204 documentation conversion]]
</dl>

==$Functions==
[[SOUL $functions#Summary of standard functions|SOUL $functions]]

==Messages==
<div id="messages"></div>
<ul>
<li>[[Media:M204_MessagesManual_V75.pdf|Model 204 messages with <code>M204.</code> prefix as of V7.5]]
<ul>
<li>[[New and updated messages in Model 204 version 7.5| <code>M204.</code> messages added/updated in V7.5]] </li>
<li>[[New and updated messages in Model 204 version 7.6| <code>M204.</code> messages added/updated in V7.6]] </li>
<li>[[New and updated messages in Model 204 version 7.7|<code>M204.</code> messages added/updated in V7.7]]</li>
</ul></li>
<li>[[List of Model 204 messages#msir|Model 204 messages with <code>MSIR.</code> prefix]]
<li>[[:Category:Fast/Unload messages|Fast/Unload messages]] </li>
<li>[[:Category:SirAud messages|SirAud messages]] </li>
<li>[[:Category:SirTune data collector messages|SirTune data collector messages]] </li>
<li>[[:Category:RockZap messages|RockZap messages]] </li>
<li>[[Dictionary/204 messages]] </li>
<li>[[SoftSpy messages]] </li>
<li>[[Connect* messages]] </li>
</ul>

==Tools==
<ul>
<li>[[Debugger]] and [[Introduction to SoftSpy|SoftSpy]] </li>
<li>[[SirAud]] - Audit trail analysis</li>
<li>[[SirFact]] - SOUL dump analysis</li>
<li>[[SirLib]] - SOUL code management</li>
<li>[[SirMon]] - Model 204 performance monitor</li>
<li>[[SirPro]] - SOUL programmers' interface</li>
<li>[[SirScan]] - Real-time Model 204 journal queries</li>
<li>[[SirTune]] - SOUL tuning</li>
<li>[[SoulEdit]] - Advanced SOUL-based editor</li>
<li>[[RKWeb]] - Browser-based access to [[RKTools]] members</li>
<li>[[RKTools installation]]</li>
</ul>

==Release notes==
<dl>
<dt>Model 204
<dd>[[Release notes for Model 204 version 7.7|Release notes for Model 204 V7.7]]
<dd>[[Release notes for Model 204 version 7.6|Release notes for Model 204 V7.6]]
<dd>[[Release notes for Model 204 version 7.5|Release notes for Model 204 V7.5]]
<dd>[[Media:M204_ReleaseNotes_V74.pdf|Release notes for Model 204 V7.4 (PDF)]]
<dd>[[Media:M204_ReleaseNotes_V71.pdf|Release notes for Model 204 V7.1 (PDF)]]

<dt>SoftSpy
<dd>[[Release notes for SoftSpy V7.6]]
<dd>[[Release notes for SoftSpy V7.5]]

<dt id="rktools_notes">SOUL tools
<dd>[[Release notes for RKTools V7.7]]
<dd>[[Release notes for RKTools V7.5]]

<dt id="Sirius_Mods_release_notes">Sirius Mods
<dd>[[Release notes for Sirius Mods V8.1]]
 [[Release notes for Sirius Mods V8.0]]
 [[Release notes for Sirius Mods V7.9]]
 [[Release notes for Sirius Mods V7.8]]

<dt id="funRel">Fast/Unload
<dd>[[Release notes for Fast/Unload V4.7]]
 [[Release notes for Fast/Unload V4.6]]
 [[Media:Funrel44New.pdf|Release notes for Fast/Unload V4.4 (PDF)]]
</dl>

==Overviews and tutorials==
<dl>
<dt>Overviews of core Model 204 areas
<dd>[[Introduction to User Language]]
 [[File management overview]]
 [[File architecture overview]]
<dt>OO structures and concepts
<dd>[[Getting started with OOP for User Language programmers]]
 [[Longstrings]]
 [[$lists]]
 [[Sessions]]
 [[Sdaemons]]
 [[Regex processing]]
 [[XML processing in Janus SOAP]]
 [[Unicode]]
</dl>

==Contribute to M204wiki==
Anyone who works with [[Model 204]] is encouraged to contribute to M204wiki, either by providing new content or correcting or improving content. Before you can edit content you must [[M204wiki:Get M204wiki User ID|obtain an M204wiki User ID]].

==Download a local copy of M204wiki==
You can [[M204wiki:Database download|download your own copy of M204wiki]].

Release notes for Model 204 version 7.7

2017-09-08T20:00:00Z

Glw:

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

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

==New in this release==
The table below cites some highlights of Model 204 version 7.7. For a full list of features, refer to the Table of Contents.
<table>
<tr class="head"><th>Category</th>
<th>Feature</th></tr>

<tr>
<td>Performance</td>
<td>
<ul>
<li>Continued expansion of 64-bit addressability. See [[#Elimination of BTB buffers|Elimination of BTB buffers]]. </li>

<li>Greater zIIP processor availability: M204 HPO and Fast/Unload HPO. See [[#zIIP exploitation|zIIP exploitation]]. </li>

<li>zIIP load tuning. See [[#MPDELAY and MPDELAYZ (new)|MPDELAYZ]], [[#SCHDOFLS (new)|SCHDOFLS]], [[#SCHDOPT (change to X'20' bit processing)|SCHDOPT]]. </li>

<li>Essential removal of application limits on the [[#Increase in request limit for number of images, screens, and menus|number of images, screens, and menus]].</li>

<li>Support for large data sets (as many as 16 million tracks) for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]]. See [[System_and_media_recovery#ROLL_BACK_processing.2C_Pass_2|ROLL BACK processing, Pass 2]].</li>
</ul>
</td></tr>

<tr>
<td>Security</td>
<td>
<ul>
<li>Stronger cryptographic algorithms: SHA-384, SHA-512. See [[#"SSL" String methods|"SSL" String methods]], [[#New DigestAlgorithm values|New DigestAlgorithm values]], and [[#New default certificate-signing algorithm|New default certificate-signing algorithm]]. </li>

<li>Longer RSA keys (as many as 4096 bits). See [[#Janus Network Security ciphers and private keys|Janus Network Security ciphers and private keys]]. </li>

<li>Support for [[#Long password support|longer and mixed-case login passwords]]. </li>
</ul>
</td><tr>

<tr>
<td nowrap>Add-on enhancements</td>
<td>
<ul>
<li>A more versatile Fast/Unload through [[#Integration of Fast/Unload with the Online load module|integration with Model 204]]. </li>

<li>Janus products' [[#Support for IPV6|support for the IPV6 network protocol]], expanding the network address space from 32 to 128 bits. </li>
</ul>
</table>

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS versions supported:
<ul>
<li>All IBM supported releases up to and including z/OS [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[IBM z/OS 2.1 compatibility issue|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM versions supported:
<ul>
<li>All IBM supported releases up to and including z/VM 6.3.</li>
</ul>
</li>

<li>IBM z/VSE versions supported:
<ul>
<li>All IBM supported releases up to and including z/VSE 6.1.</li>
</ul>
</li>
</ul>

===Hardware requirements===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

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

Connect★ version 7.5 or 7.7 is compatible with Model 204 version 7.7.

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ wiki pages]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New exception class: WriteError====
<var>[[WriteError class|WriteError]]</var> exceptions are thrown by the <var>Close</var>, <var>WriteBlock</var>, <var>WriteRecord</var>, and <var>WriteRecords</var> methods in the [[Dataset class]] if they encounter a full output <var>Dataset</var> object.

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model 204</var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method might add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

====Resulting element length in "ToXmlDoc" String methods====
Prior to version 7.7 of Model 204, the <var>[[DerToXmlDoc (String function)|DerToXmlDoc]]</var>, <var>[[X509CertificateToXmlDoc (String function)|X509CertificateToXmlDoc]]</var>, <var>[[X509CrlToXmlDoc (String function)|X509CrlToXmlDoc]]</var>, and
<var>[[RSAPrivateKeyToXmlDoc (String function)|RSAPrivateKeyToXmlDoc]]</var> methods failed if input to them created any element in the result <var>XmlDoc</var> with a text child whose length exceeded 650 characters.
An example of such input is a 4096-bit key (which requires 1024 hex characters).

As of version 7.7, the lengths of the created text nodes are not restricted.

====LDAP request length limit====
Prior to version 7.7 of Model 204, the SOUL [[LDAP class#limit|LDAP client buffers]] allowed a limit of 6144 bytes per request. As of 7.7, the limit is increased to 8184.

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

This change is propagated by zap maintenance to version 7.6 of Model 204.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.6 and above, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names can begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign (<tt>-</tt>), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names.

See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details. 

===Assert statement support for Info expressions===
The SOUL <var>[[Assert statement|Assert]]</var> statement allows the optional parameter <var>Info</var> to provide additional output information. As of version 7.7, the <var>Info</var> phrase may contain any valid SOUL expression, including a method call or $function. The expression, which must be enclosed in parentheses, is evaluated only in the case of an <var>Assert</var> failure.

A simple example is:
assert %x gt 0, info ('abc' with 'def') 

<blockquote class="note">
Note: This enhancement introduces a slight backward incompatibility: An <var>Assert</var> statement like the following, whose <var>Info</var> value begins with an opening parenthesis but has no closing parenthesis, compiled without error prior to version 7.7: 
assert %x gt 0, info (

From 7.7 on, such a statement produces a compilation error, because the compiler expects an expression after the open parenthesis. 
</blockquote>

==Security enhancements==
===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters.
 Also, passwords and passphrases can now contain one or more embedded spaces. (Leading and trailing spaces are stripped.)

The long password feature includes support for: 
<ul>
<li><var>[[LOGIN or LOGON command|LOGON]]</var> command</li>
<li><var>[[LOGINCP or LOGONCP command|LOGONCP]]</var> command, used to change a password</li>

<li><var>[[LOGCTL command: Modifying user ID entries in the password table|LOGCTL C USERID]]</var> command</li>

<li><var>[[$Sir_Login]]</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>[[Storing_security_information_(CCASTAT)|CCASTAT]] data sets created with or without password expiration support</li>

<li>Long passwords (passphrases) for use with the following [[Security interfaces overview|external security interfaces]]: CA-ACF2 MVS, Security Server (formerly RACF), and CA-Top Secret</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

For additional security enhancements in version 7.7, see [[#Janus Network Security ciphers and private keys|Janus Network Security ciphers and private keys]] as well as [[#"SSL" String methods|"SSL" String methods]], [[#New DigestAlgorithm values|New DigestAlgorithm values]], and [[#New default certificate-signing algorithm|New default certificate-signing algorithm]].

==Janus product enhancements==

===Support for IPV6===
As of version 7.7, customers can use the [[Janus products]] in an IPV6 (Internet Protocol Version 6) environment. Before this release, all Janus commands and parameters were able to accommodate IPV4 addresses only. IPV6 addresses expand the network address space from 32 to 128 bits.

These parameters, commands, and functions support IPV6 under version 7.7 of Model 204:

<table>
<tr class="head"><th>Commands</th><th>System parameter</th><th>SOUL</th></tr>
<tr><td nowrap>
JANUS CLSOCK and JANUS SRVSOCK 
JANUSDEBUG and JANUS WEB DEBUG 
JANUS DEFINEIPGROUP 
JANUS DEFINE BINDADDR 
JANUS DISIPG 
JANUS DISUSG 
JANUS TRACE 
JANUS WEB ALLOW
</td>

<td nowrap>
TCPTYPE 
(see [[#tcptype|TCPTYPE (new IPV6 values)]])
</td>

<td nowrap>
$Web_IPAddr 
LocalHost (UdpSocket property)
</td></tr>
</table>

===Janus Network Security ciphers and private keys===
Support for certificates signed using [[DigestAlgorithm_enumeration|SHA-384 and SHA-512]] are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

In addition, support is added for RSA keys that are as many as 4096 bits in length. You can now generate and sign 4096-bit keys and use them in client and server certificates using <var class="product">Janus Network Security</var> application as well as its associated and related methods, including:
<table>
<tr class="head"><th>Class</th><th>Method</th></tr>
<tr><td>System</td>
<td><var>[[GeneratedPrivateKey (System function)|GeneratedPrivateKey]]</var></td></tr>

<tr><td rowspan="4">Stringlist</td>
<td><var>[[AppendCertificateRequest (Stringlist function)|AppendCertificateRequest]]</var></td></tr>

<tr><td><var>[[AppendGeneratedPrivateKey (Stringlist subroutine)|AppendGeneratedPrivateKey]]</var></td></tr>

<tr><td><var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var></td></tr>

<tr><td><var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var></td></tr>

<tr><td rowspan="4">String</td>
<td><var>[[CertificateRequest (String function)|CertificateRequest]]</var> </td></tr>

<tr><td><var>[[ClientCertificateRequest (String function)|ClientCertificateRequest]]</var> </td></tr>

<tr><td><var>[[RSAPrivateKeyToXmlDoc (String function)|RSAPrivateKeyToXmlDoc]]</var> </td></tr>

<tr><td><var>[[SignedCertificate (String function)|SignedCertificate]]</var> </td></tr>
</table>

===Janus Web Server rules===
The following changes have been made in version 7.7:
<ul>
<li>Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.</li>

<li>You can now substitute an HTTP method name in the command for a <var>JANUS WEB ON</var> rule. See [[#ON rules (method name substitution)|ON rules (method name substitution)]] for details.</li>

<li>The automatic <var>[[JANUS WEB ALLOW]]</var> rule, which allowed any user to access the port without requiring a login, is changed for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies (after zap 77Z088 in version 7.7, or after zap 76Z418 in version 7.6) unless overridden by user-added rules.

<blockquote class="note">
Note: With version 7.7 zap 77Z090 or version 7.6 zap 76Z420, you can make the default <var>ALLOW</var> rule as it was in version 7.5 and earlier (<code>ALLOW *</code>). To do so, turn on the 1 bit of the <var>[[WEBDFLT parameter|WEBDFLT]]</var> parameter: 
RESET WEBDFLT=1
</blockquote></li>

<li>As described below in [[#JANUS WEB (additional rule support)|JANUS WEB (additional rule support)]], the <var>JANUS WEB</var> command <var>ALLOW</var> and <var>DISALLOW</var> rules are updated to include support for RESTful and WebDAV HTTP methods. </li>
</ul>

===Janus Web access to HTTP authorization and authentication headers===
Under version 7.7, Janus Web lets you access HTTP user authentication headers. You can capture the HTTP "Authorization" request header value, and you can set the "WWW-Authenticate" response header. See [[Janus Web Server security#Authorization and WWW-Authenticate headers|Authorization and WWW-Authenticate headers]].

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Previously (for all versions of <var class="product">Fast/Unload</var> through 4.7), the standalone <code>FUNLOAD</code> load module was downloaded and linked separately and independently from Model 204. Starting with version 7.7 of Model 204:
<ul>
<li><var class="product">Fast/Unload</var> is entirely linked with the Model 204 Online load module. </li>

<li>Maintenance zaps applied to the Online load module include all <var class="product">Fast/Unload</var> maintenance.</li>

<li>The version number of <var class="product">Fast/Unload</var> is the same as the version number of Model 204. </li>

<li>If you are authorized for Fast/Unload, the authorization zap for the ONLINE load module will contain authorization for Fast/Unload. The authorization zap used for previous releases of FUNLOAD should not be applied to the FUNLOAD module in 7.7.</li>
</ul>

Under 7.7, the Online load module can be linked with an ALIAS (the standard one is FUNLOAD) and an alternate ENTRY. This alias is functionally indistinguishable from the standalone <var class="product">Fast/Unload</var> FUNLOAD load module installed for all previous versions of <var class="product">Fast/Unload</var>.

The integration of Fast/Unload with the Online load module also makes additional DDnames available to PGM=FUNLOAD for possible problem diagnosis by Rocket Technical Support. These DDnames are <code>CCASNAP</code>, <code>CCAAUDIT</code>, and <code>CCAPRINT</code>, and they are described in [[Fast/Unload invocation#ccadd|Fast/Unload invocation]].

A significant benefit of running Fast/Unload integrated with Model 204 and not standalone is the ability to take advantage of zIIP processing, as described next in the "zIIP exploitation" section.

===zIIP exploitation===
If you have an authorization zap that contains both of the following, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available:
<ul>
<li><var class="product">[[Performance monitoring and tuning#Offloading Model 204 work to zIIP processors|M204 HPO]]</var>, the zIIP-support product of Model 204

PGM=FUNLOAD automatically supplies the necessary Model 204 parameters to enable zIIP exploitation. </li>

<li>The <var class="product">[[Fast/Unload overview#fuhpo|Fast/Unload HPO]]</var> product </li>
</ul>

===New #VIEW204 function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>[[Fast/Unload PUT statement#PUT|PUT]]</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

For better readability and lower CPU cost than the techniques currently used to achieve the same result, the <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
... PUT info .. AS [format] COUNTED[1|2] 

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

With this feature, you can replace FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 
With: 
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and somewhat more efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>[[Fast/Unload standard functions##strip|#STRIP]]</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#Length prefix for PUT output values|COUNTED]]</var> options for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED2</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>P</var> and <var>N</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the <var>#STRIP</var> first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR %VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements with the following, which outputs a numeric value with leading zeroes stripped: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2

Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.</li>

<li id="optn">The new <var>N</var> option strips neither leading-characters nor trailing-characters.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===FREE command (new message)===
Prior to this release, a successful <var>[[FREE command#msg|FREE]]</var> command was not followed by a message indicating success. Under version 7.7, <var>FREE</var> now indicates success with the following message:
M204.0510: FREE command successful; ddname freed 

Also new in this release, a <var>FREE</var> command that takes no action because the specified file does not exist or is not allocated is now followed by an explanatory message:

M204.0509: No action taken by FREE command; ddname not allocated 

In earlier versions, no such message followed. 

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (additional rule support)===


====Expanded ALLOW/DISALLOW rules====
The <var>[[JANUS WEB]]</var> command <var>ALLOW</var>/<var>DISALLOW</var> rules are updated to include support for these HTTP methods:
<ul>
<li>The RESTful ([https://en.wikipedia.org/wiki/Representational_state_transfer Representational State Transfer]) methods CONNECT, DELETE, OPTIONS, PATCH, and TRACE. </li>

<li>The WebDAV ([http://www.webdav.org/specs/rfc4918.html Distributed Authoring and Versioning]) methods PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK. </li>
</ul>

====ON rules (method name substitution)====
In a version 7.7 <var>[[JANUS WEB ON|JANUS WEB ON]]</var> command, you can now reference the name of the HTTP method that is associated with the incoming request. To do this, specify an <code>M</code> after the escape (<tt>"</tt>) character, as in:

JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'

A GET request for URL <code>/test/foo</code> would result in the file <code>TEST</code> being opened and the command <code>I GET.FOO</code> being issued. A POST for the same URL would result in the command <code>I POST.FOO</code> being issued.

Note: This behavior is a change from past releases, when <code>"M</code> was simply converted to <code>M</code>.

===LOGINCP or LOGONCP (new)===
Because colons are now valid password characters, the <var>[[LOGINCP or LOGONCP command|LOGINCP]]</var> (LOGIN and Change Password) command replaces the former technique for changing passwords using <var>LOGIN</var>.
Before version 7.7, with <var>LOGIN</var>, you specified <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt.
With the <var>LOGINCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGINCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGONCP</var> is a synonym for <var>LOGINCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new and changed values)===
====New values====
The following values have been added to the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The <code>CUSTOM=23</code> value always truncates the user ID to 10 characters.</li>

<li>The <code>CUSTOM=41</code> value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The <code>CUSTOM=42</code> value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

====Changed value====
<ul>
<li>The <code>CUSTOM=11</code> value also supports special-characters for RACF passwords as of version 7.7.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===MPDELAY and MPDELAYZ (new)===
For an [[Performance monitoring and tuning#Multiprocessing .28MP.2F204.29|MP/204]] Online, the <var>[[MPDELAY parameter|MPDELAY]]</var> and <var>[[MPDELAYZ parameter|MPDELAYZ]]</var> parameters are added to improve the efficiency of the MP scheduler. They reduce the cost of starting too many new subtasks for the amount of work to be done.

===NUMBUF and NUMBUFG===
As described below in [[#Elimination of BTB buffers|Elimination of BTB buffers]], setting <var>NUMBUFG</var> greater than 0 in version 7.7 forces <var>NUMBUF</var> to 0 (no buffer pool buffers reside below the bar). Not setting <var>NUMBUFG</var> or setting it to 0 (no buffers above the bar) allows the calculation of BTB buffers to remain as in previous versions.

===SCHDOFL and SCHDOFLZ (new minimum value)===
The new minimum value of <var>[[SCHDOFL parameter|SCHDOFL]]</var> and <var>[[SCHDOFLZ parameter|SCHDOFLZ]]</var> is 0. Before Model 204 7.7, their minimum allowed value was 1.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

===SCHDOPT (change to X'20' bit processing)===
The <var>[[SCHDOPT parameter|SCHDOPT]]</var> X'20' bit prevents the maintask from running work that is intended to run on a zIIP subtask (when zIIP subtasks are defined and activated). As of Model 204 7.7, even when this bit is off, the maintask will run some of the zIIP work only if the zIIP subtasks appear to be saturated. Saturation is defined as a zIIP subtask queue length of at least <code>[[SCHDOFLZ parameter|SCHDOFLZ]]*[[AMPSUBZ parameter|AMPSUBZ]]</code>.

Formerly, this saturation requirement was absent, allowing the maintask to take on more (possibly too much) of the zIIP workload.

===SERVSIZE (new default/minimum value)===
The minimum value for <var>[[SERVSIZE parameter|SERVSIZE ]]</var> is changed from zero to 65536. If <var>SERVSIZE</var> is explicitly set in CCAIN and its value is less than 64K, the following message is issued:
M204.1149: SERVSIZE has been set to its minimum value: 65536


If <var>SERVSIZE</var> was not set but was [[Defining the runtime environment (CCAIN)#Sizing user server areas|calculated by the system]] to a value less than 64K, the following message is issued:
M204.0163: SERVSIZE increased to 65536


This change is propagated by zap maintenance to versions 7.6, 7.5, and 7.4 of Model 204. 

===TCPTYPE (new IPV6 values)===
As part of the version 7.7 [[#IPV6|support for IPV6]], three new optional (IPV6-address-only) values are added to the <var>[[TCPTYPE parameter|TCPTYPE]]</var> parameter:
IBMV6
BPXV6
IUCVV6


==Performance enhancements==

===Elimination of BTB buffers===
As of version 7.7, any use of above-the-bar buffer pool (as invoked by a setting of the <var>[[NUMBUFG parameter|NUMBUFG]]</var> parameter greater than 0) will force all buffer pool buffers above the bar — no below-the-bar buffers will exist. In this case, the <var>[[NUMBUF parameter|NUMBUF]]</var> and <var>[[MINBUF parameter|MINBUF]]</var> parameters will be forced to 0, and the other parameters that affect BTB storage (<var>MAXBUF</var>, <var>SPCORE</var>, <var>LDKBMWND</var>, and <var>NLRUQ</var>) will be ignored.

If you set <var>NUMBUFG</var> to 0, all buffers will be below the bar, and the settings of the BTB-related parameters will be respected and calculated as in pre-7.7 versions.

===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

===Large checkpoint data sets===
Support is added for large data sets (as many as 16 million tracks) for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]]. For details, see [[System_and_media_recovery#ROLL_BACK_processing.2C_Pass_2|ROLL BACK processing, Pass 2]].

==Statistics enhancements==

===BLKO===
The [[Using system statistics#System performance statistics|performance statistic]] BLKO now also reports invisible users that are blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG, and RUNG, you can now approximate USRS (average active users).

For the <var>MONITOR</var> command, the [[ONLINE monitoring#User information in formatted displays|QUE column]] now reports new values OFFO and OFFI instead of OFFQ for invisible users:
<ul>
<li>OFFO is invisible and blocked out. </li>
<li>OFFI is invisible and blocked in. </li>
</ul>

The BLKO QUE value continues to mean blocked out and visible (on some queue), and BLKI means blocked in and visible.

===CCATDIFF and CCATDIFH===
The [[Using system statistics#Description of statistics|CCATDIFF]] user and since-last statistic gets incremented each time a user allocates a CCATEMP page, and it gets decremented each time a user frees a page. Its value is not allowed to drop below zero. In the event of a CCATEMP page shortage, CCATDIFF gives system managers the possibility of determining a particular user that might be primarily responsible.

Note: CCATDIFF is a rough guide, not definitive: it might give false high readings for some users, but it will indicate a user whose usage is extremely extraordinary. 

[[Using system statistics#Description of statistics|CCATDIFH]] is a since-last statistic that reports a request's CCATDIFF since-last highwater mark, useful to retrospectively determine which request was responsible for a massive CCATEMP usage spike. For example, it will record a request that allocated a large number of CCATEMP pages but freed the pages before the request ended.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>[[External Call Facility#module|External Module]]</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

===Running ECF requests under the invoking user’s profile===
Unless the new system parameter <var>[[ECPRIV parameter|ECPRIV]]</var> 4 bit is set, the job invoked by a privileged [[External Call Facility]] statement at a site where an external authorizer (ACF2, RACF, or Top/Secret) is used runs under the external-authorizer profile of the user that invokes the External Call, rather than under the job's external-authorizer profile.

Prior to version 7.7, such a job always ran under the job's external-authorizer profile, so this is a [[#Profile used for running ECF requests|backward compatibility]] issue.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===SoftSpy Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger Client version information display on mainframe===
As of version 7.7 and Client build 64, the <var class="product">Janus/TN3270 Debugger</var> Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]]:
MSIR.1077: Begin debug session, user 3, client: Build: 64, Tag: 2 (Janus debugger session)

This information is not sent if the Debugger Client build number is less than 64, and the mainframe side views all Client versions prior to build 64 as build 63.

The build number, which identifies Client versions, is displayed in the Client Audit Trail tab at start up:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA


You can also view the build number of the Client at any time by selecting Help > About. And as of Client build 65, the build number is displayed by the Client function <var>&&buildNumber()</var>.

===Enforcing use of a minimum version of the Debugger Client===
Normally, when you use the TN3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used.
As of Client build 65 and Model 204 7.7, you can force Clients to have at least a minimum build number in order to invoke a debugging session with your Online. The new Model 204 system parameter <var>[[MINDEBCL parameter|MINDEBCL]]</var> sets such a minimum.

If you set <var>MINDEBCL</var> to a positive value, use a version of the Debugger Client whose build number is less than <var>MINDEBCL</var>, and invoke a debugging session, the debugging session is rejected. An error message is shown in your browser and at the Client, calling for a Client upgrade.

You also see the following error on the Online's Audit Trail (and on the terminal if you are using <code>TN3270 DEBUG ON</code>):
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused


==Compatibility issues==

===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduces an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===JANUS WEB ON -- "M substitution===
In the command for a <var>JANUS WEB ON</var> rule, <code>"M</code> can now be used to specify a method name.
This behavior is a change from past releases, when <code>"M</code> was simply converted to <code>M</code>. See [[#ON rules .28method name substitution.29|JANUS WEB ON rules (method name substitution)]] for details.

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

===Profile used for running ECF requests===
As [[#ecfprofile|described earlier]], the default external-authorizer (ACF2, RACF, or Top/Secret) profile under which a job invoked by a privileged ECF statement runs is changed in version 7.7. Instead of such a job running under the job's external-authorizer profile (as it did prior to 7.7), the job runs by default in 7.7 under the user's external-authorizer profile.

The default behavior can be changed by turning on the new system parameter <var>[[ECPRIV parameter|ECPRIV]]</var> 4 bit.

==Notes for system manager and installer==
===CRAM SVC installation is deprecated===
The CRAM SVC installation has been deprecated as of version 7.5. Installation of CRAM-XDM is described as part of the [[Model 204 installation]].
===Authorization and maintenance zaps===
When you download Rocket M204 product object files, all relevant authorization keys and all current maintenance zaps are pre-applied to the object files as part of the download process.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

File:RKToolsMainMenu77.png

2017-09-08T17:49:38Z

Glw: Glw uploaded a new version of File:RKToolsMainMenu77.png

version 7.7 edition

MediaWiki:Sidebar

2017-08-16T18:05:05Z

Glw:

*  
** What's new|What's New
* SEARCH
* Reference Pages
** SOUL|SOUL/User Language
** Category:Model 204 files|Model 204 files
** Category:System management|System management
** Lists of classes and methods|Classes/methods
** Category:Commands|Commands
** List of Model 204 parameters|Parameters
** SOUL $functions|$Functions
** M204wiki main page#Messages|Messages
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Categories&offset=&limit=500|Categories

* Product Information
** Model_204|Model 204
** Model 204 add-ons and applications|Add-ons and applications
** Release_notes|Release notes
** Installation|Installation
** Model 204 documentation|PDF manuals

* Help-Editing
** Contacting Rocket Software Technical Support|Technical Support
** Searching_M204wiki|Searching tips
** http://sirius-software.com/search_methods|Method search
** Updating_M204wiki|Editing guide

* TOOLBOX

* Toolbox
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:WhatLinksHere&target={{FULLPAGENAMEE}}|What links here
** recentchanges-url|recentchanges
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Upload|Upload file
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:SpecialPages|Special pages

* Print
** {{SERVER}}{{SCRIPTPATH}}/index.php?title={{FULLPAGENAMEE}}&printable=yes|Print this page

* LANGUAGES

MediaWiki:Sidebar

2017-08-16T13:13:57Z

Glw:

*  
** What's new|What's New
* SEARCH
* Reference Pages
** SOUL|SOUL/User Language
** Category:Model 204 files|Model 204 files
** Category:System management|System management
** Lists of classes and methods|Classes/methods
** Category:Commands|Commands
** List of Model 204 parameters|Parameters
** SOUL $functions|$Functions
** M204wiki main page#Messages|Messages
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Categories&offset=&limit=500|Categories

* Product Information
** Model_204|Model 204
** Model 204 add-ons and applications|Add-ons and applications
** Release_notes|Release notes
** Installation|Installation
** Model 204 documentation|PDF manuals

* Help-Editing
** Contacting Rocket Software Technical Support|Technical Support
** Searching_M204wiki|Searching tips
** http://sirius-software.com/search_methods|Method search
** Updating_M204wiki|Editing guide

* TOOLBOX

* Toolbox
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:WhatLinksHere&target={{FULLPAGENAMEE}}|What links here
** recentchanges-url|recentchanges
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Upload|Upload file
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:SpecialPages|Special pages

* Print-Export
** {{SERVER}}{{SCRIPTPATH}}/index.php?title={{FULLPAGENAMEE}}&printable=yes|Print this page

* LANGUAGES

MediaWiki:Sidebar

2017-08-16T13:12:53Z

Glw:

*  
** What's new|What's New
* SEARCH
* Reference Pages
** SOUL|SOUL/User Language
** Category:Model 204 files|Model 204 files
** Category:System management|System management
** Lists of classes and methods|Classes/methods
** Category:Commands|Commands
** List of Model 204 parameters|Parameters
** SOUL $functions|$Functions
** M204wiki main page#Messages|Messages
** /index.php?title=Special:Categories&offset=&limit=500|Categories

* Product Information
** Model_204|Model 204
** Model 204 add-ons and applications|Add-ons and applications
** Release_notes|Release notes
** Installation|Installation
** Model 204 documentation|PDF manuals

* Help-Editing
** Contacting Rocket Software Technical Support|Technical Support
** Searching_M204wiki|Searching tips
** http://sirius-software.com/search_methods|Method search
** Updating_M204wiki|Editing guide

* TOOLBOX

* Toolbox
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:WhatLinksHere&target={{FULLPAGENAMEE}}|What links here
** recentchanges-url|recentchanges
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Upload|Upload file
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:SpecialPages|Special pages

* Print-Export
** {{SERVER}}{{SCRIPTPATH}}/index.php?title={{FULLPAGENAMEE}}&printable=yes|Print this page

* LANGUAGES

M204wiki main page

2017-08-15T15:04:08Z

Glw:

Welcome to M204wiki, the platform for Rocket Software Model 204 technical documentation. Here you can find product information, installation and reference documentation, and release notes.

M204wiki contains the current version of Model 204 documentation, with release-specific features noted in the text. In some cases, documentation is provided in [[Model 204 documentation|PDF format]].

In addition to plentiful page links, [[Searching M204wiki|M204wiki searching features]] help you quickly locate the information you need.

__TOC__

==Model 204==
<dl>
<dt>Installation
<dd>[[Model 204 installation]]

<dt>Introductions to core Model 204 areas
<dd>[[SOUL|SOUL/User Language]]
 [[File management overview|File management]]
 [[File architecture overview|File architecture]]
 [[Model 204 configurations and operating environments|System management]]

<dt>Commands
<dd>[[List of Model 204 commands]]

<dt>Parameters
<dd>[[List of Model 204 parameters]]

<dt>Security
<dd>[[Model 204 security features]]
 [[Storing security information (CCASTAT)#Overview|Storing security information (CCASTAT)]]
 [[:Category:Security interfaces|Security interfaces]]
 [[Janus Network Security]]

<dt>PDF manuals
<dd>[[Model 204 documentation|Model 204 documentation conversion]]
</dl>

==$Functions==
[[SOUL $functions#Summary of standard functions|SOUL $functions]]

==Messages==
<div id="messages"></div>
<ul>
<li>[[Media:M204_MessagesManual_V75.pdf|Model 204 messages with <code>M204.</code> prefix as of V7.5]]
<ul>
<li>[[New and updated messages in Model 204 version 7.5| <code>M204.</code> messages added/updated in V7.5]] </li>
<li>[[New and updated messages in Model 204 version 7.6| <code>M204.</code> messages added/updated in V7.6]] </li>
<li>[[New and updated messages in Model 204 version 7.7|<code>M204.</code> messages added/updated in V7.7]]</li>
</ul></li>
<li>[[List of Model 204 messages#msir|Model 204 messages with <code>MSIR.</code> prefix]]
<li>[[:Category:Fast/Unload messages|Fast/Unload messages]] </li>
<li>[[:Category:SirAud messages|SirAud messages]] </li>
<li>[[:Category:SirTune data collector messages|SirTune data collector messages]] </li>
<li>[[:Category:RockZap messages|RockZap messages]] </li>
<li>[[Dictionary/204 messages]] </li>
<li>[[SoftSpy messages]] </li>
<li>[[Connect* messages]] </li>
</ul>

==Tools==
<ul>
<li>[[Debugger]] and [[Introduction to SoftSpy|SoftSpy]] </li>
<li>[[SirAud]] - Audit trail analysis</li>
<li>[[SirFact]] - SOUL dump analysis</li>
<li>[[SirLib]] - SOUL code management</li>
<li>[[SirMon]] - Model 204 performance monitor</li>
<li>[[SirPro]] - SOUL programmers' interface</li>
<li>[[SirScan]] - Real-time Model 204 journal queries</li>
<li>[[SirTune]] - SOUL tuning</li>
<li>[[SoulEdit]] - Advanced SOUL-based editor</li>
<li>[[RKWeb]] - Browser-based access to [[RKTools]] members</li>
<li>[[RKTools installation]]</li>
</ul>

==Release notes==
<dl>
<dt>Model 204
<dd>[[Release notes for Model 204 version 7.7|Release notes for Model 204 V7.7]]
<dd>[[Release notes for Model 204 version 7.6|Release notes for Model 204 V7.6]]
<dd>[[Release notes for Model 204 version 7.5|Release notes for Model 204 V7.5]]
<dd>[[Media:M204_ReleaseNotes_V74.pdf|Release notes for Model 204 V7.4 (PDF)]]
<dd>[[Media:M204_ReleaseNotes_V71.pdf|Release notes for Model 204 V7.1 (PDF)]]

<dt>SoftSpy
<dd>[[Release notes for SoftSpy V7.6]]
<dd>[[Release notes for SoftSpy V7.5]]

<dt id="rktools_notes">SOUL tools
<dd>[[Release notes for RKTools V7.7]]
<dd>[[Release notes for RKTools V7.5]]

<dt id="Sirius_Mods_release_notes">Sirius Mods
<dd>[[Release notes for Sirius Mods V8.1]]
 [[Release notes for Sirius Mods V8.0]]
 [[Release notes for Sirius Mods V7.9]]
 [[Release notes for Sirius Mods V7.8]]

<dt id="funRel">Fast/Unload
<dd>[[Release notes for Fast/Unload V4.7]]
 [[Release notes for Fast/Unload V4.6]]
 [[Media:Funrel44New.pdf|Release notes for Fast/Unload V4.4 (PDF)]]
</dl>

==Overviews and tutorials==
<dl>
<dt>Overviews of core Model 204 areas
<dd>[[Introduction to User Language]]
 [[File management overview]]
 [[File architecture overview]]
<dt>OO structures and concepts
<dd>[[Getting started with OOP for User Language programmers]]
 [[Longstrings]]
 [[$lists]]
 [[Sessions]]
 [[Sdaemons]]
 [[Regex processing]]
 [[XML processing in Janus SOAP]]
 [[Unicode]]
</dl>

==Contribute to M204wiki==
Anyone who works with [[Model 204]] is encouraged to contribute to M204wiki, either by providing new content or correcting or improving content. Before you can edit content you must [[M204wiki:Get M204wiki User ID|obtain an M204wiki User ID]].

==Download a local copy of M204wiki==
You can [[M204wiki:Database download|download your own copy of M204wiki]].

M204wiki main page

2017-08-15T15:03:54Z

Glw:

Test

Welcome to M204wiki, the platform for Rocket Software Model 204 technical documentation. Here you can find product information, installation and reference documentation, and release notes.

M204wiki contains the current version of Model 204 documentation, with release-specific features noted in the text. In some cases, documentation is provided in [[Model 204 documentation|PDF format]].

In addition to plentiful page links, [[Searching M204wiki|M204wiki searching features]] help you quickly locate the information you need.

__TOC__

==Model 204==
<dl>
<dt>Installation
<dd>[[Model 204 installation]]

<dt>Introductions to core Model 204 areas
<dd>[[SOUL|SOUL/User Language]]
 [[File management overview|File management]]
 [[File architecture overview|File architecture]]
 [[Model 204 configurations and operating environments|System management]]

<dt>Commands
<dd>[[List of Model 204 commands]]

<dt>Parameters
<dd>[[List of Model 204 parameters]]

<dt>Security
<dd>[[Model 204 security features]]
 [[Storing security information (CCASTAT)#Overview|Storing security information (CCASTAT)]]
 [[:Category:Security interfaces|Security interfaces]]
 [[Janus Network Security]]

<dt>PDF manuals
<dd>[[Model 204 documentation|Model 204 documentation conversion]]
</dl>

==$Functions==
[[SOUL $functions#Summary of standard functions|SOUL $functions]]

==Messages==
<div id="messages"></div>
<ul>
<li>[[Media:M204_MessagesManual_V75.pdf|Model 204 messages with <code>M204.</code> prefix as of V7.5]]
<ul>
<li>[[New and updated messages in Model 204 version 7.5| <code>M204.</code> messages added/updated in V7.5]] </li>
<li>[[New and updated messages in Model 204 version 7.6| <code>M204.</code> messages added/updated in V7.6]] </li>
<li>[[New and updated messages in Model 204 version 7.7|<code>M204.</code> messages added/updated in V7.7]]</li>
</ul></li>
<li>[[List of Model 204 messages#msir|Model 204 messages with <code>MSIR.</code> prefix]]
<li>[[:Category:Fast/Unload messages|Fast/Unload messages]] </li>
<li>[[:Category:SirAud messages|SirAud messages]] </li>
<li>[[:Category:SirTune data collector messages|SirTune data collector messages]] </li>
<li>[[:Category:RockZap messages|RockZap messages]] </li>
<li>[[Dictionary/204 messages]] </li>
<li>[[SoftSpy messages]] </li>
<li>[[Connect* messages]] </li>
</ul>

==Tools==
<ul>
<li>[[Debugger]] and [[Introduction to SoftSpy|SoftSpy]] </li>
<li>[[SirAud]] - Audit trail analysis</li>
<li>[[SirFact]] - SOUL dump analysis</li>
<li>[[SirLib]] - SOUL code management</li>
<li>[[SirMon]] - Model 204 performance monitor</li>
<li>[[SirPro]] - SOUL programmers' interface</li>
<li>[[SirScan]] - Real-time Model 204 journal queries</li>
<li>[[SirTune]] - SOUL tuning</li>
<li>[[SoulEdit]] - Advanced SOUL-based editor</li>
<li>[[RKWeb]] - Browser-based access to [[RKTools]] members</li>
<li>[[RKTools installation]]</li>
</ul>

==Release notes==
<dl>
<dt>Model 204
<dd>[[Release notes for Model 204 version 7.7|Release notes for Model 204 V7.7]]
<dd>[[Release notes for Model 204 version 7.6|Release notes for Model 204 V7.6]]
<dd>[[Release notes for Model 204 version 7.5|Release notes for Model 204 V7.5]]
<dd>[[Media:M204_ReleaseNotes_V74.pdf|Release notes for Model 204 V7.4 (PDF)]]
<dd>[[Media:M204_ReleaseNotes_V71.pdf|Release notes for Model 204 V7.1 (PDF)]]

<dt>SoftSpy
<dd>[[Release notes for SoftSpy V7.6]]
<dd>[[Release notes for SoftSpy V7.5]]

<dt id="rktools_notes">SOUL tools
<dd>[[Release notes for RKTools V7.7]]
<dd>[[Release notes for RKTools V7.5]]

<dt id="Sirius_Mods_release_notes">Sirius Mods
<dd>[[Release notes for Sirius Mods V8.1]]
 [[Release notes for Sirius Mods V8.0]]
 [[Release notes for Sirius Mods V7.9]]
 [[Release notes for Sirius Mods V7.8]]

<dt id="funRel">Fast/Unload
<dd>[[Release notes for Fast/Unload V4.7]]
 [[Release notes for Fast/Unload V4.6]]
 [[Media:Funrel44New.pdf|Release notes for Fast/Unload V4.4 (PDF)]]
</dl>

==Overviews and tutorials==
<dl>
<dt>Overviews of core Model 204 areas
<dd>[[Introduction to User Language]]
 [[File management overview]]
 [[File architecture overview]]
<dt>OO structures and concepts
<dd>[[Getting started with OOP for User Language programmers]]
 [[Longstrings]]
 [[$lists]]
 [[Sessions]]
 [[Sdaemons]]
 [[Regex processing]]
 [[XML processing in Janus SOAP]]
 [[Unicode]]
</dl>

==Contribute to M204wiki==
Anyone who works with [[Model 204]] is encouraged to contribute to M204wiki, either by providing new content or correcting or improving content. Before you can edit content you must [[M204wiki:Get M204wiki User ID|obtain an M204wiki User ID]].

==Download a local copy of M204wiki==
You can [[M204wiki:Database download|download your own copy of M204wiki]].

M204wiki:Database download

2017-08-15T14:17:23Z

Glw:

The content of {{SITENAME}} is available for download, provided only that no copyright notices may be removed or altered. The download format is a zip archive that contains both an XML dump of the wiki pages suitable for loading into your own installation of Mediawiki (or one of the many personal wiki implementations) and a tar file with all of the uploaded images and other objects such as PDF files.

==How to download a copy of {{SITENAME}}==
Use one of the following URLs to download a copy of the {{SITENAME}} contents:
{{SERVER}}{{SCRIPTPATH}}/images/M204wiki_full.zip or
{{SERVER}}{{SCRIPTPATH}}/images/M204wiki_current.zip


'''M204wiki_full.zip''' contains the full {{SITENAME}} content (minus user records, security groups and "talk" pages), including all past versions of each page. As of September 2014, this file is approximately 104 megabytes of data, and expected to constantly increase in size.

'''M204wiki_current.zip''' contains only the latest version of each {{SITENAME}} page (minus user records, security groups and "talk" pages). This copy provides the latest version of all material but ''without'' the page history. As of September 2014, this file is approximately 46 megabytes in size, and it is expected to increase in size but to always remain smaller than the "full" version. '''This is probably the copy you want.'''

Both of the above files are refreshed every night, just after midnight Boston time.

===Updating local copies of {{SITENAME}}===
If you make changes to a downloaded copy of the {{SITENAME}} content, then of course those changes will be lost if you refresh the downloaded copy; The download and import process is a full refresh, and no incremental option is currently offered.

If you'd like to contribute to {{SITENAME}}, you will need to [[M204wiki:Get M204wiki User ID|obtain a M204wiki User ID]].

==What to do with your copy of {{SITENAME}}==
Most likely you are downloading a copy of {{SITENAME}} because your <var class="product">Model 204</var> site does not allow internet access. Maintaining a local copy of {{SITENAME}} provides access in a format that can be kept as up-to-date as you like.

If you want to present {{SITENAME}} totally faithful to its original format, you'll want to install a local copy of Mediawiki, the software currently hosting {{SITENAME}}:

http://www.mediawiki.org/wiki/MediaWiki

There are a variety of methods for importing a {{SITENAME}} XML dump and related binary uploads, all explained at the Mediawiki site:

http://www.mediawiki.org/wiki/Manual:Importing_XML_dumps

Once you have a copy of Mediawiki installed, the simplest way to load the M204wiki content in a single step is via the script in <code>maintenance/importDump.php</code> (documentation provided in "Using importDump.php, if you have shell access" at the above link). For example, issue a command like the following (this is the file which was downloaded on September 10, 2014):
php \www\mediawiki\maintenance\importDump.php c:\users\dave\downloads\XC140910.xml

The above command can be run in Windows, if the MoWeS portable reader was installed in the root directory containing <code>\www</code> and the current M204wiki was saved in the above <code>downloads</code> directory.

Alternately, you can forgo the local installation of Mediawiki and use one of the aftermarket readers designed to import and display the Mediawiki XML dump. The most popular one is Wikitaxi (Windows only; no Linux or OS/X version is provided):

http://en.wikipedia.org/wiki/Wikipedia:Database_download#WikiTaxi

A number of other viewing options are explained at the above page.

==See also==
<ul>
<li>The Model 204 homepage: http://model204.rocket-software.com
<li>Mediawiki: http://www.mediawiki.org<
<li>Wikitaxi: http://www.wikitaxi.org
<li>Wikimedia XML dump importing: http://www.mediawiki.org/wiki/Manual:Importing_XML_dumps
<li>Mediawiki XML dump format: http://meta.wikimedia.org/wiki/Help:Export
<li>Wikipedia's information page on using XML database dumps: http://en.wikipedia.org/wiki/Wikipedia:Database_download
</ul>

MediaWiki:Vector.css

2017-08-15T10:24:12Z

Glw:

/* CSS placed here will affect users of the Vector skin */

/* needed to keep content border top from extending too far left */
div#mw-head-base {
margin-left: 11.5em; /* for Vector centering project */
}

/* for view history items - less wrapping from Vector centering */
ul#pagehistory {
font-size: .8em;
}

/* line height of items in diff of history pg */
table.diff {
line-height: 1.2; /* was 1.6 */
}

/* needed to keep content border bottom from extending too far left */
div#footer {
margin-left: 11em;
}

/* move sidebar items to left */
div#mw-panel.collapsible-nav .portal {
margin-left: 1px;
}

#p-logo {
width: 11em;
}

/* next to give headings greater distinction -- slightly bolder, slightly larger */

div#mw-panel div.portal h3 {
font-size: .80em;
font-weight: 600;
}

/* ************************************************* */
/* add origami bar for h1, color change for h2, and make room for new logo */
.mw-body h1 {
color: #050D9E;
font-family: Arial, Helvetica, sans-serif;
background-image: url(images/4/4c/OrigamiBar_87.png);
background-repeat: no-repeat;
background-position: left bottom;
border-bottom: none;
height: 100%;
}

.mw-body h2 {
font-family: Arial, Helvetica, sans-serif;
color: #000000;
border-bottom: 2px solid #AAA;
}

div#content #firstHeading {
padding-bottom: .75em;
margin-bottom: 1em;
}

/* prep for new logo */
div#mw-panel {
top: 100px;
}

div#p-logo {
top:-125px;
left:-15px;
}

/* change/move logo (LocalSettings.php names logo file) */
div#p-logo a {
height:110px;
width:11em;
}

/* ************************************************* */
/* Web team changes */

/* move, enlarge, change color & font of top row of links */
div#p-personal {
top:9px;
font-family: 'Open Sans', sans-serif;
}

div#p-personal ul li {
font-size:1em;
margin-left:2em;
}

div#p-personal ul li a,
div#p-personal ul li a:visited,
div#p-personal ul li a.new,
div#p-personal ul li a.new.visited {
color:#000000;
}

div#mw-head {
top:1em;
}

div#mw-head-base {
height:7em;
}

/* space bet top links and row of tabs below */
#left-navigation {
margin-top:3.5em;
}

#right-navigation {
margin-top:3.5em;
}

/* ************************************************* */

/* changes to reduce excess height of tabs (overwrites some of above) */
div#mw-head-base {
height:6.5em;
}

div.vectorTabs {
height:2em;
}

div.vectorTabs span a {
padding-top:1em;
}

div.vectorTabs ul li {
line-height:.7em;
}

div.vectorTabs li a {
height:1.5em;
}

#ca-watch.icon a {
padding-top:2.4em;
}

div#mw-head div.vectorMenu h3 {
height:2em;
}

div.vectorMenu h3 span {
font-size:.8em;
padding-top:1em;
}

div.vectorMenu h3 a {
height:2.3em;
}

div#p-search form {
margin-top:.2em;
}

div#simpleSearch {
height:1.4em;
margin-top:0;
}

div#simpleSearch input#searchInput {
padding-top:.25em;
font-size:.85em;
}

/* **************************************************************** */

/* added to accommodate M'wiki changes between v23 and v28 */

code {
border:0px none;
padding:0px;
color:inherit;
}

MediaWiki:Sidebar

2017-08-15T10:23:11Z

Glw:

*  
** What's new|What's New
* SEARCH
* Reference Pages
** SOUL|SOUL/User Language
** Category:Model 204 files|Model 204 files
** Category:System management|System management
** Lists of classes and methods|Classes/methods
** Category:Commands|Commands
** List of Model 204 parameters|Parameters
** SOUL $functions|$Functions
** M204wiki main page#Messages|Messages
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Categories&offset=&limit=500|Categories

* Product Information
** Model_204|Model 204
** Model 204 add-ons and applications|Add-ons and applications
** Release_notes|Release notes
** Installation|Installation
** Model 204 documentation|PDF manuals

* Help-Editing
** Contacting Rocket Software Technical Support|Technical Support
** Searching_M204wiki|Searching tips
** http://sirius-software.com/search_methods|Method search
** Updating_M204wiki|Editing guide

* TOOLBOX

* Toolbox
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:WhatLinksHere&target={{FULLPAGENAMEE}}|What links here
** recentchanges-url|recentchanges
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:Upload|Upload file
** {{SERVER}}{{SCRIPTPATH}}/index.php?title=Special:SpecialPages|Special pages

* Print-Export
** {{SERVER}}{{SCRIPTPATH}}/index.php?title={{FULLPAGENAMEE}}&printable=yes|Print this page

* LANGUAGES

Release notes for Model 204 version 7.7

2016-08-01T14:42:02Z

Glw: /* Debugger Client Build 65 */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===SoftSpy Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger Client version information display on mainframe===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected. An error message is also shown by the client.
====Debugger Client Build 65====
Shortly after the GA release of Model 204 Version 7.7, Build 65 of the debugger client will be released. It has better error message display for various connection errors and also for MINDEBCL violations. Although earlier client builds work fine with M204 7.7 and MINDEBCL, we encourage customers to upgrade to Build 65 when it is released to get the improved error reporting. Build 65 also will work fine with M204 releases prior to 7.7.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:36:14Z

Glw: /* Debugger updates */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===SoftSpy Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger Client version information display on mainframe===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected. An error message is also shown by the client.
====Debugger Client Build 65====

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:35:23Z

Glw: /* Debugger version information display */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===SoftSpy Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger Client version information display on mainframe===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected. An error message is also shown by the client.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:34:35Z

Glw: /* Debugger updates */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===SoftSpy Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected. An error message is also shown by the client.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:27:21Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected. An error message is also shown by the client.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:24:54Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:03:12Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and try to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused

The debug session will be rejected.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T14:01:36Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and then attempt to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: ''xx'' < MINDEBCL: ''yy'' debugger client connection refused


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T13:59:52Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and then attempt to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T13:59:11Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and then attempt to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66
debugger client connection refused


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-08-01T13:58:00Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

If you set <var>[[MINDEBCL parameter|MINDEBCL]]</var> to a positive value and then attempt to use a version of the debugger client whose build number is less than MINDEBCL, you will see the following error on the Audit Trail, and on the terminal if you are using <code>TN3270 DEBUG ON</code>:

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-31T12:36:42Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 as build 63.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-31T12:36:19Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

Since client builds before 64 do not transmit their build number, the mainframe side views all client versions prior to build 64 and build 63.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-31T12:33:58Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-31T12:33:25Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.
Build 64 (and up) of the debugger client transmits its build number back to mainframe side when a debugging session is initiated. The mainframe side uses this information to construct the MSIR.1077 message:
MSIR.1077: Begin debug session, user 3, client: Build: 65, Tag: 1 (Janus debugger session)

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:46:14Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting <code>Help->About</code>.
On Debugger client build 65 and up, you may also get the build number from the client function <code>&&buildNumber()</code>.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:44:20Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting Help->About.
On Debugger client build 65 and up, you may also get the build number from the client function &&buildNumber().

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:41:48Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
<pre>
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA
*

</pre>
You may also view the build number of the client at any time by selecting Help->About.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:41:12Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA
*

You may also view the build number of the client at any time by selecting Help->About.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:40:36Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA

You may also view the build number of the client at any time by selecting Help->About.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:33:37Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:32:53Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger workstation client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA
...


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2016-07-30T21:31:59Z

Glw: /* Enforcing use of a minimum version of the Debugger Client */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters. 

This feature includes support for: 
<ul>
<li><var>LOGON</var> command, when used to change a password using <var class="term">oldpw:newpw</var></li>

<li><var>LOGCTL C USERID</var> command</li>

<li><var>$Sir_Login</var> function</li>

<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>

<li>CCASTAT data sets created with or without password expiration support</li>

<li>Long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only; it does not apply to file passwords.

No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

===Large checkpoint data sets===
Support is added for large data sets for the Model 204 Checkpoint facility [[Checkpoints: Storing before-images of changed pages#Creating the CHKPOINT.2FCHKPNT .28and CHKPNTS.29 data set|CHKPOINT or CHKPNTS data sets]].

==Operating system and hardware requirements==

===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New System methods: FastUnload and FastUnloadTask====
The <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class work exactly like their same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> object on which to operate.

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===

The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

This functionality also requires:
<ul>
<li>The V7.7 <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the <var>System</var> class, which work exactly like their
same-named <var>Recordset</var> counterparts but without a <var>Recordset</var> to operate on.</li>

<li>The FUEL code for the Fast/Unload request to contain the <var>[[Fast/Unload Extraction Language (FUEL)#OPEN datafile|OPEN]]</var> statement, just as in standalone Fast/Unload (<code>PGM=FUNLOAD</code>). </li>

<li>The <var>[[Fast/Unload program parameters#NOEnq|NOENQ]]</var> parameter to become meaningful under FUSI.

This will cause Fast/Unload to process the Model 204 file (or files, if multiple files are specified on the FUEL <var>OPEN</var> statement) without the shared DASD enqueuing feature, and thus the processing of the file(s) is read-only at a physical I/O level. </li>
</ul>

Here is an example fragment of read-only processing using FUSI:

text to %fuel = new
OPEN DATAFIL
FOR EACH RECORD
PUT ...
...
OUTPUT
...
END FOR
end text

%(system):FastUnload(input=%fuel, ..., parameters = 'NOENQ, ...')


===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

===PUT statement enhancements===


====Length prefix for PUT output values====

New <var>PUT</var> statement syntax is added to insert a one-byte or two-byte binary integer, containing the byte length of a <var>PUT</var> value, in the output stream before the value.

This addition provides better readability and lower CPU cost than the techniques currently used to achieve the same result.

====COUNTED keyword for AS clause====

The <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function as PUT "info" argument====

New in this version, a #function call is allowed as the <var>PUT</var> <var class="term">info</var> argument. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use this more readable and similarly efficient equivalent:
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===#STRIP function enhancements===


====New #STRIP fourth argument====

The new fourth argument of <var>#STRIP</var> lets you designate a <var>#STRIP</var> first-argument value to be nullified. That is, when the value of the first argument is equal to the value of the fourth argument, <var>#STRIP</var> returns a null string. You might use this optional argument for fields that have a "placeholder value" or "default value" which is not actual data.

This argument can be conveniently combined with the
new <var>[[#COUNTED keyword for AS clause|COUNTED]]</var> option for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.

Combining the new fourth argument, the new <var>COUNTED</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF


You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2


====New #STRIP type options====

<var>LK</var>, <var>N</var>, and <var>P</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>LK</var> option lets you strip leading zeroes from numeric value output.

<var>LK</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2
</li>

<li id="optn">The new <var>N</var> option prevents leading-character stripping, trailing-character stripping, or both.

For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</li>

<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the #STRIP first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.

<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following, which outputs a numeric value with leading zeroes stripped:
<nowiki>%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</nowiki>

You can replace the above statements by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2


Note: A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.
</li>
</ul>

==New and changed commands==


===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===JANUS WEB (rule changes)===

The <var>[[JANUS WEB]]</var> command

===LOGONCP command (LOGON and Change Password)===
Because colons are now valid password characters, this command replaces the former technique for changing passwords using <var>LOGON</var>. That technique let you specify <var class="term">oldpassword</var><tt>:</tt><var class="term">newpassword</var> in response to the <code>M204.0347: Password</code> prompt. With the <var>LOGONCP</var> command, you are prompted and re-prompted for the new password after successful logon:
LOGONCP USER1
M204.0347: Password
M204.0353: USER1 USER1 login 16 JUL 29 12.38
M204.2633: Enter new password
M204.2633: Re-enter new password
M204.0350: New password accepted
M204.0345: CCASTAT updated

<var>LOGINCP</var> is a synonym for <var>LOGONCP</var>.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
The new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum [[Debugger]] Client build number that can be used with that Online.

===SCHDOFLS (new)===
For z/OS system customers using <var class="product">Model 204</var> zIIP support, the new <var>[[SCHDOFLS parameter|SCHDOFLS ]]</var> system parameter helps you to regulate the zIIP processor workload.

<var>SCHDOFLS</var> specifies both of the following:
<ul>
<li>The target number of threads on the zIIP offload queue before a non-SRB MP subtask is dispatched to help the zIIP subtasks. </li>

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>

This parameter applies to z/OS only.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==

===MODEL 6 screen size and back-paging===
As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large <var>[[LOUTPB parameter|LOUTPB]]</var> value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed, even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, <var>LOUTPB</var> was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a <code>MODEL 6</code> screen geometry that requires more than 6142 bytes.

===ECF calls to the IBM IDCAMS utility===
The new <var>IDCAMS</var> option for the <var>External Module</var> statement of the Model 204 [[External Call Facility]] lets a SOUL program invoke IDCAMS without using the SYSIN and SYSPRINT DD statements. Instead, the Model 204 Universal Buffer is used to pass the input lines and receive the output lines from IDCAMS.

==Debugger updates==

===SoftSpy authorization===

SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.

EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, Debugger build 64, the most recent version of the Debugger Client sends its build and tag number to the mainframe, and this information is displayed in message [[MSIR.1077]].

This information is not sent if the Debugger Client build number is less than 64.

===Enforcing use of a minimum version of the Debugger Client===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, lets you specify the minimum build number of a Debugger Client that can be used with an Online.
Normally, when you use the Tn3270 or Janus Debugger, no restrictions are placed on which version of the Debugger Work Station client GUI is used. Versions of the client are identified by a build number, which is displayed in the Audit Tab when the client starts:
2016 07 30 17:21:47 The Rocket Software Debugger Client
2016 07 30 17:21:47 Build: 65 (01 August 2016) Tag: 1 GA
...


==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]

MINDEBCL parameter

2016-07-29T19:30:51Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted. The purpose of this parameter is to allow a system manager to ensure upgrades to the Janus/TN3270 debugger client are done.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

Here is an audit trail fragment showing this error (via SIRSCAN):
13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66
debugger client connection refused
13303016 2 1 AD MSIR.0929: Janus/Tn3270 Debugger worker terminated: 400
Client version too old, please upgrade


If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
MSIR.0942: Debugger GUI port defaulted to 8081
MSIR.0942: Debugger Worker port defaulted to 3226
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:33:20Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

Here is an audit trail fragment showing this error (via SIRSCAN):
13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66
debugger client connection refused
13303016 2 1 AD MSIR.0929: Janus/Tn3270 Debugger worker terminated: 400
Client version too old, please upgrade


If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
MSIR.0942: Debugger GUI port defaulted to 8081
MSIR.0942: Debugger Worker port defaulted to 3226
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:32:35Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

Here is an audit trail fragment showing this error (via SIRSCAN):
13303016 2 1 ER MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 500
debugger client connection refused
13303016 2 1 AD MSIR.0929: Janus/Tn3270 Debugger worker terminated: 400
Client version too old, please upgrade


If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
MSIR.0942: Debugger GUI port defaulted to 8081
MSIR.0942: Debugger Worker port defaulted to 3226
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:11:25Z

Glw:

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
MSIR.0942: Debugger GUI port defaulted to 8081
MSIR.0942: Debugger Worker port defaulted to 3226
MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:10:23Z

Glw:

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
*** MSIR.0942: Debugger GUI port defaulted to 8081
*** MSIR.0942: Debugger Worker port defaulted to 3226
*** 1 MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
*** 2 MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:09:36Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
*** MSIR.0942: Debugger GUI port defaulted to 8081
*** MSIR.0942: Debugger Worker port defaulted to 3226
*** 1 MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
*** 2 MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:06:55Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
*** MSIR.0942: Debugger GUI port defaulted to 8081
*** MSIR.0942: Debugger Worker port defaulted to 3226
*** 1 MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
*** 2 MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T17:05:27Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.

If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command and get a MINDEBCL rejection, a message is displayed on the terminal as well. For example:
R MINDEBCL 66
MINDEBCL 66 Minimum debugger client build supported
TN3270 DEBUG ON DEBONLY 10.5.3.76
*** MSIR.0942: Debugger GUI port defaulted to 8081
*** MSIR.0942: Debugger Worker port defaulted to 3226
*** 1 MSIR.1079: Debugger Client Build: 65 < MINDEBCL: 66 debugger client connection refused
*** 2 MSIR.0914: Debugger Error: Please upgrade your client
ULSPFGLW>

MINDEBCL parameter

2016-07-29T16:07:18Z

Glw: /* Summary */

MINDEBCL parameter

2016-07-29T16:06:52Z

Glw: /* Description */

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>--
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed by the client and written to the audit trail that the Debugger Client does not meet minimum requirements and needs to be updated.
If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command, a message is displayed on the terminal as well.

MINDEBCL parameter

2016-07-29T16:05:28Z

Glw:

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>--
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>

==Description==
The <var>MINDEBCL</var> parameter holds an integer value in the range 0-500 of the minimum [[Debugger]] Client build number that can be used with the Online in which it was set. A value of 0 means that any build of the Debugger Client is accepted.

If the Client build number is earlier than the <var>MINDEBCL</var> setting, the server rejects the Debugger Client, and the request is processed as if debugging were not in place.
A message is displayed (and written to the audit trail) that the Debugger Client does not meet minimum requirements and needs to be updated.
If you are using the <var>TN3270|SIRIUS DEBUG ON</var> command, a message is displayed on the terminal as well.

MINDEBCL parameter

2016-07-25T22:30:54Z

Glw:

{{Template:MINDEBCL parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>--
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On user's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.7</var>
</dl>
==Description==
The <var>MINDEBCL</var> parameter holds an integer value of the minimum debugger client build number that can be used with the Online in which it was set. A value of 0 means that any build of the debugger client is accepted.

If the client build number is earlier than the MINDEBCL setting, the server rejects the debugger client, and the request is processed as if debugging were not in place.
A message is displayed (and written to the audit trail) that the debugger client does not meet minimum requirements and needs to be updated.
If you are using the TN3270/Sirius DEBUG ON command, a message is displayed on the terminal as well.

MSIR.1077 Begin debug session, user (usernum), client: Build: (buildnum), Tag: (tagnum) ((debugname) debugger session)

2016-07-25T22:29:21Z

Glw:

This informational message displays the following about a Janus/Tn3270 Debugger session:
<ul>
<li>Model 204 User number of the thread being debugged</li>
<li>Build number and tag number of the workstation client being used</li>
<li>Debugger in use (Janus or Tn3270)</li>
</ul>

For example:
MSIR.1077: Begin debug session, user 1, client: Build: 64, Tag: 2 (Janus Debugger session)

This message is available as of Model 204 version 7.7. Debugger Client information is available for Client build 64 or later.

If the <var>[[MINDEBCL parameter|MINDEBCL]]</var> parameter is set to a higher build number than the build being used, this message is not produced.

{{Template:MSIR.1077 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.1000 - MSIR.1199]]

MSIR.1077 Begin debug session, user (usernum), client: Build: (buildnum), Tag: (tagnum) ((debugname) debugger session)

2016-07-25T22:28:59Z

Glw:

This informational message displays the following information about a Janus/Tn3270 Debugger session:
<ul>
<li>Model 204 User number of the thread being debugged</li>
<li>Build number and tag number of the workstation client being used</li>
<li>Debugger in use (Janus or Tn3270)</li>
</ul>

For example:
MSIR.1077: Begin debug session, user 1, client: Build: 64, Tag: 2 (Janus Debugger session)

This message is available as of Model 204 version 7.7. Debugger Client information is available for Client build 64 or later.

If the <var>[[MINDEBCL parameter|MINDEBCL]]</var> parameter is set to a higher build number than the build being used, this message is not produced.

{{Template:MSIR.1077 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.1000 - MSIR.1199]]

MSIR.1077 Begin debug session, user (usernum), client: Build: (buildnum), Tag: (tagnum) ((debugname) debugger session)

2016-07-25T22:12:27Z

Glw:

This informational message displays the following information about a Janus/Tn328 Debugger Client session:
<ul>
<li>User number</li>
<li>Build number and tag number </li>
<li>Debugger in use (Janus or Tn3270)</li>
</ul>

For example:
MSIR.1077: Begin debug session, user 1, client: Build: 64, Tag: 2 (Janus Debugger session)

This message is available as of Model 204 version 7.7. Debugger Client information is available for Client build 64 or later.

If the <var>[[MINDEBCL parameter|MINDEBCL]]</var> parameter is set to a higher build number than the build being used, this message is not produced.

{{Template:MSIR.1077 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.1000 - MSIR.1199]]

Release notes for Model 204 version 7.7

2016-07-22T19:58:56Z

Glw: /* Enforcing use of a minimum version of the client debugger */

These release notes list the enhancements and other changes contained in Model 204 version 7.7.

******THIS IS A DRAFT DOCUMENT.******

These release notes list the enhancements and other changes contained in Model 204 version 7.7, which is still in development. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.

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

==New features==

===Long password support===

Logon passwords, maintained in CCASTAT, can now contain up to 127 characters. This feature includes support for: 
<ul>
<li>LOGON command when used to change a password using <var class="term">oldpw:newpw</var></li>
<li>LOGCTL C USERID command</li>
<li>$Sir_Login function</li>
<li>Mixed-case passwords (if the <var>[[CUSTOM parameter|CUSTOM]]</var> parameter includes the value 11)</li>
<li>CCASTAT data sets created with or without password expiration support</li>
<li>long passwords (password phrases) for use with the external security interfaces: ACF2, RACF, or TOPSECRET</li>
</ul>
Note: This feature is available for logon passwords only and does not apply to file passwords.
No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.

==Operating system and hardware requirements==
===Operating system requirements===

<ul>
<li>IBM z/OS
<ul>
<li>Versions supported: z/OS version 1.07 through [[IBM z/OS 2.2 PTF requirement|2.2]].</li>
Version 1.07 is sufficient for all functionality except for the following features:
<ul>
<li>zHPF support requires version [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</li>
<li>Large (1 MB) page support requires version 1.9.</li>
<li>Extended address volumes (EAV) requires version 1.12.</li>
</ul>
</li>
</ul>
On z/OS, Model 204 release 7.7 operates as an APF authorized load module, as required by many 7.7 features. 
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].

<li>IBM z/VM
<ul>
<li>Versions supported: z/VM version 5.4 through 6.3.</li>
</ul>
</li>

<li>IBM z/VSE
<ul>
<li>Versions supported: z/VSE version 5.1 and 5.2.</li>
</ul>
</li>
</ul>

=== Hardware requirements ===

In general, Model 204 version 7.7 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
<ul>
<li>large (1 MB) page support</li>
<li>IBM's High Performance FICON (zHPF) support</li>
</ul>

===Model 204 compatibility with operating systems===

For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]].

==SOUL (User Language) enhancements==

===New and changed classes and methods===

====New default certificate-signing algorithm====
[[Janus Network Security]] as well as the <var>[[Stringlist_class|StringList]]</var> methods <var>[[AppendSignedCertificate (Stringlist function)|AppendSignedCertificate]]</var> and <var>[[AppendSignedClientCertificate (Stringlist function)|AppendSignedClientCertificate]]</var> methods have changed their default signature algorithm from SHA-1 to SHA-256.

This change is propagated by zap maintenance to versions 7.6 and 7.5 of Model 204.

===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
<tr><td>[[SHA384digest (String function)|SHA384digest]]</td><td>SHA-384 digest</td></tr>
<tr><td>[[SHA512digest (String function)|SHA512digest]]</td><td>SHA-512 digest</td></tr>
</table>

====New LoadMsgctl method====
The new <var>[[LoadMsgctl (XmlDoc subroutine)|LoadMsgctl]]</var> method lets you view what <var class="product">Model </var> messages have been affected by <var>[[MSGCTL command|MSGCTL]]</var> commands. The method also displays the current attributes of those messages. 

In addition, to better understand the effect of the <var>MSGCTL</var> command, the [[RKTools]] <code>SIRIUS</code> file will contain a procedure you can use to display the <var>MSGCTL</var> commands that have been specified in the Online session.

====New DigestAlgorithm values====
Values <var>SHA384</var> and <var>SHA512</var> are added to the [[DigestAlgorithm enumeration]].

====Method variable invocation====
[[Method variables]] can now be invoked using <code>%var()</code> or <code>%obj:var()</code>, as in JavaScript.

====X509CertificateToXmlDoc method support for unknown elements====
A certificate's <code><RelativeDistinguishedName></code> element can contain a wide variety of attributes that <var>X509CertificateToXmlDoc</var> does not understand. Under Model 204 7.6 and earlier, this results in a parse exception, but under 7.7 and later, such attributes are added as <code><unknown></code> elements with an <code><ObjectIdentifier></code> element that indicates the ASN.1 object identifier.

Note: You are advised not to refer to such an <code><unknown></code> element in your programs, since future updates to the <var>X509CertificateToXmlDoc</var> method may add support for the element, in which case the element name will change to a proper name. If such an element is of interest, [[Contacting Rocket Software Technical Support|contact Rocket Software technical support]]. 

===New XHTML entities for square-bracket characters===
[ and ] are newly supported as [[XML processing in Janus SOAP#Entity references|XMHTL entities]] (notably in the [[U (String function)#brackets|U method]]). This provides a better approach to specifying square brackets (such as for [[XPath#Some notes on XPath usage|XPath]] expressions) than the formerly recommended use of <var>Static</var> %variables initialized to the correct values.

For example, to produce an XPath expression equivalent to the following:
<nowiki>*/pers[@name="Hector"] </nowiki>
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('&#x5B;'):u
%rsq is string len 1 static initial('&#x5D;'):u
. . .
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) 

Under version 7.7, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)

===Procedure names may begin with zero===
Formerly, a procedure name was not allowed to begin with a zero or a minus sign. As of version 7.7, a procedure name can begin with a zero, and alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a hyphen. For example, <code>00123</code>, <code>-1myproc</code>, and <code>-myproc</code> are valid procedure names. See the <var>[[PROCEDURE command|PROCEDURE]]</var> command for details.

==Janus product enhancements==

===Janus Network Security ciphers===
Support for certificates signed using SHA-384 and SHA-512 are added to [[Janus Network Security]]. This makes it possible to generate certificates signed with these algorithms and to accept server or client certificates signed with these algorithms.

===Janus Web Server default rules===
Janus Web used to automatically implement [[Defining Web rules#Notes|two web server ON rules]] to set up access to the Janus Web sample home page and to demonstration application procedures. These rules were removed in version 7.6 (by zap maintenance) and are not present in version 7.7.

Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to the following to force login for any URL on a Janus Web port:
JANUS WEB portname ALLOW * USER *

This rule applies, in version 7.6 (by zap maintenance) and in version 7.7, unless overridden by user-added rules.

==Fast/Unload enhancements==

===Integration of Fast/Unload with the Online load module ===

Starting with version 7.7 of Model 204, Fast/Unload is entirely linked with the Model 204 Online load module, maintenance zaps applied to the Online load module will include all Fast/Unload maintenance, and the version number of Fast/Unload is the same as the version number of Model 204.

Previously (for all versions of Fast/Unload through version 4.7), the standalone FUNLOAD load module was downloaded and linked separately and independently from Model 204.

===zIIP exploitation===
If you have an authorization zap that contains the base zIIP support product of Model 204 and contains the Fast/Unload HPO product, your standalone PGM=FUNLOAD jobs will run on a zIIP processor, if one is available. See [[Fast/Unload overview#fuhpo|Fast/Unload HPO]].

===Physical read-only file access with FUSI===
The [[Fast/Unload SOUL Interface]] (FUSI) will support read-only file access at the physical I/O level.

===PUT statement enhancements===


====Length prefix for PUT output values====

New PUT statement syntax is added so that a one-byte or two-byte binary integer, containing the byte length of the PUT value, is placed in the output stream before the value. The purpose of this addition is to improve the readability and CPU cost over the techniques currently used to achieve the same result.

====New #STRIP argument====

The new fourth argument of #STRIP

====New #STRIP type options====

The new <var>LK</var> option of the <var>#STRIP</var> function, together with the other new Fast/Unload <var>PUT</var> features, can be used to strip leading zeroes from numeric value output.

This allows FUEL code such as the following:
%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF 

To be replaced by the more readable and efficient: 
PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2


The new <var>N</var> option of <var>#STRIP</var> . . .

====COUNTED keyword for AS clause====

The AS clause of a PUT statement will now allow the COUNTED keyword:
<nowiki>... PUT info .. AS [type] COUNTED[1|2] </nowiki>

For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.

This feature will allow FUEL code such as the following: 
%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL 

To be replaced by the more readable and more efficient:
PUT %VAL AS COUNTED2 

====#function call as "info" phrase====

New in this version, a #function call is allowed as the "info" phrase. For example, instead of FUEL code such as the following:
%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
PUT %VAL 
You can use the more readable (similarly efficient):
PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) 

===New #VIEW function===
The <var>[[Fast/Unload standard functions#.23VIEW204: Value of Model 204 parameter|#VIEW204]]</var> function returns the value of the [[List of Model 204 parameters|Model 204 parameter]] you specify as an argument.

==New and changed commands==

===DISPLAY MODMAP (new parameter: <var>UEX</var>)===
The <var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> command now has a <var>UEX</var> parameter that displays the entry point addresses of all defined user exits.

===JANUS DEFINE (new parameter: <var>SSLTRUST</var>)===
The <var>[[JANUS DEFINE]]</var> command now has an <var>[[SSLTRUST (JANUS DEFINE parameter)|SSLTRUST]]</var> parameter that indicates that the certificate presented by the other side of a TLS/SSL connection is to be accepted even if it is not signed by a known certifying authority.

===ZHPF (new parameters: filename and *)===
The <var>[[ZHPF command|ZHPF]]</var> command checks zHPF ability for the file currently opened by the user.

As of Model 204 7.7, you can specify parameters to <var>ZHPF</var>:
<ul>
<li><var class="term">filename</var>, to check a specific file</li>
<li>An asterisk (<tt>*</tt>), to check local files opened by all users</li>
</ul>

==New and changed parameters==


===CUSTOM (new values)===
The following values have been added to the <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter in this release:
<ul>
<li>The CUSTOM=23 value always truncates the userid to 10 characters.</li>

<li>The CUSTOM=41 value allows recording of data on successful RACF user logins. The login data is shown in RACFRW batch reports.</li>

<li>The CUSTOM=42 value allows the editing of procedure names containing the following special characters: comma, equal sign, space, single quote, semicolon.</li>
</ul>

===LFSCB (new default/minimum value)===
The default (and minimum) value of <var>[[LFSCB parameter|LFSCB]]</var> is now 8 bytes.

===LITBL (new default/minimum value)===
The default (and minimum) value of <var>[[LITBL parameter|LITBL]]</var> is now 8 bytes.

===MINDEBCL (new)===
A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set in an Online to specify the minimum debugger client build number that can be used with that Online.

==Performance enhancements==

===Journal and checkpoint processing enhancements===

New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. 

A dual mode of operation (with and without write PSTs) is available: if the new PSTs are not created (for any reason), the journal and checkpoint processing continues as it does in version 7.5 of Model 204. 

The <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter is also crucial: If <var>SYSOPT2</var> indicates new PSTs but <var>NSUBTKS</var> is too low, the Online will not come up.



===Increase in request limit for number of images, screens, and menus===
These limits are increased to 4095 per request:
<ul>
<li>The total number of [[Images|images]] for all blocks (formerly 256)</li>

<li>The maximum number of [[Menu statement or block#Menus and screens|menus and screens]] combined (formerly 256)</li>
</ul>

==Statistics enhancements==
===BLKO===
The performance statistic BLKO now reports invisible users as blocked out. In previous releases, invisible users were not reported and BLKO remained virtually zero. The new BLKO value is more precise, and by summing BLKO, WTSV, BLKI, REDY, SWPG and RUNG, you can now approximate USRS (average active users).

For the MONITOR command, the QUE column now reports BLKO instead of OFFQ for invisible users and displays new values OFFO and OFFI.
OFFO is invisible and blocked out; OFFI is invisible and blocked in.
BLKO now means blocked out and on some queue. BLKI now means blocked in and on some queue.

==Other enhancements==
===MODEL 6 screen size and back-paging===

As of Model 204 version 7.7 (and 7.5 or 7.6 with maintenance applied), a large LOUTPB value for [[Terminal MODEL 6 support|MODEL 6]] geometries is allowed even if screen back-paging has been enabled.

In previous releases, during initialization, if back-paging was enabled for the IODEV, LOUTPB was automatically reset to the limit that supported back-paging.

Back-paging will now be disabled for any terminal with a MODEL 6 screen geometry that requires more than 6142 bytes.

==Debugger Updates==
===SoftSpy authorization===
SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.
EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.

===Error message for DBCSENV===

As in previous releases, SoftSpy is not supported in a DBCS (double-byte character set) environment. As of version 7.7, if the CCAIN parameter DBCSENV is set to a non-zero value, the SPY command is rejected with the following message:
Message 207: SoftSpy may not be used in a DBCS environment.

===Debugger version information display===
As of version 7.7, debugger build 64, the most recent version of the debugger client sends its build and tag number to the mainframe, and this information is displayed in message MSIR.1077.

This information is not sent if the debugger client build number is less than 64.

===Enforcing use of a minimum version of the debugger client===

A new system parameter, <var>[[MINDEBCL parameter|MINDEBCL]]</var>, can be set to specify the minimum debugger client build number that can be used with an Online.

==Compatibility issues==
===APSYPAGE parameter cannot be non-zero===
(Applies to the IBM z/OS system.)
The <var>APSYPAGE</var> parameter was disabled (but still allowed) in version 7.6. As of version 7.7, if <var>APSYPAGE</var> is non-zero, the Online will not come up and the following error message will appear:

M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative

See [[APSYPAGE parameter]] for information about alternatives to <var>APSYPAGE</var>.

===Unlabeled FDV statement compilation errors===
Version 7.7 introduced an edge case incompatibility by disallowing code which is very questionable or clearly wrong; that is, previously the compiler allowed pretty much any statements between the label and the FDV. Such statements are no longer allowed.

For example, the following was allowed in older versions of Model 204:
 a: audit 'About to FDV'
fdv foo
b: frv in a

Inserting SOUL code between a label and an FDV statement is no longer allowed, and so the result of the above is:

M204.0311 Unacceptable statement reference

This change was also introduced as maintenance in both version 7.5 (as zaps 75Z408 and 75Z414) and version 7.6 (as zaps 76Z175 and 76Z182).

===KOMM addressing changes===
<ul>
<li>KU is no longer 4K addressable from KOMM. It has been relocated to KOMM+1100 and must be addressed using grande (‘G’) instructions.</li>
<li>KHEOC has been renamed to KGEOC.</li>
<li>KUUSRNO has been renamed to KBUSRNO.</li>
<li>In addition, all KUP… fields have been removed and replaced by their 64-bit equivalent KUG… fields. 
For example, before 7.7, VTBL might be addressed by using <code>L R1,KUPVT</code>. 
As of version 7.7, that reference would require <code>LG R1,KUGVT</code>.</li>
</ul>

For context, see [[Customizing functions and translation tables#Converting user-written functions|Converting user-written functions]].

===Journal format compatibility===
A recovery code error unintentionally allowed recovery to be run using Model 204 7.6 against a version 7.5 journal, and vice versa. Although the error was benign because the journal formats were the same in those versions, mixing of journal versions and Model 204 versions is no longer allowed.

==New and updated messages==

See [[New and updated messages in Model 204 version 7.7 -- DRAFT|New and updated messages in Model 204 version 7.7]] for details.

[[Category: Release notes]]