Release notes for Model 204 version 7.6: Difference between revisions
m (→Performance enhancements: Model 204 HPO) |
|||
(56 intermediate revisions by 3 users not shown) | |||
Line 2: | Line 2: | ||
==Overview== | ==Overview== | ||
These release notes contain installation and features information for the Rocket Model 204 version 7.6 release. | These release notes contain installation and features information for the Rocket Model 204 version 7.6 release. | ||
Before beginning your installation, please read through this information about product installation and changes. | Before beginning your installation, please read through this information about product installation and changes. | ||
Line 29: | Line 29: | ||
<li>[[#64-bit addressing and Above The Bar (ATB) storage|STBL, VTBL, and other server tables]] can now be placed above the (2G) bar</li> | <li>[[#64-bit addressing and Above The Bar (ATB) storage|STBL, VTBL, and other server tables]] can now be placed above the (2G) bar</li> | ||
<li>Support for IBM [[#High Performance FICON (zHPF)|zHPF]] (High Performance FICON) I/O interface</li> | <li>Support for IBM [[#High Performance FICON (zHPF)|zHPF]] (High Performance FICON) I/O interface</li> | ||
<li>New [[#Journal and checkpoint processing enhancements|journal and checkpoint write PSTs]] (pseudo subtasks)</li> | <!-- removed; not finished <li>New [[#Journal and checkpoint processing enhancements|journal and checkpoint write PSTs]] (pseudo subtasks)</li> --> | ||
</ul> | </ul> | ||
</td> | </td> | ||
Line 69: | Line 69: | ||
<li><b>IBM z/OS</b> | <li><b>IBM z/OS</b> | ||
<ul> | <ul> | ||
<li> | <li>All IBM supported releases up to and including z/OS 2.3. <br />(For z/OS 2.2, see [[IBM z/OS 2.2 PTF requirement]].)<br /> | ||
(For z/OS 2.1, see [[IBM_z/OS_2.1_compatibility_issue|IBM z/OS 2.1 compatibility issue]].)</li> | |||
<p>Version 1.07 is sufficient for all functionality except for the following features:</p> | |||
<ul> | <ul> | ||
<li>zHPF support requires version 2.1.</li> | <li>zHPF support requires version 2.1.</li> | ||
Line 105: | Line 106: | ||
===Model 204 compatibility with operating systems=== | ===Model 204 compatibility with operating systems=== | ||
For information on Model 204 certification with IBM operating systems, see | For information on Model 204 certification with IBM operating systems, see [[Model 204 system requirements]]. | ||
<div id="Connect* compatibility with Model 204"></div> | <div id="Connect* compatibility with Model 204"></div> | ||
===Connect<sup>★</sup> compatibility with Model 204=== | ===Connect<sup>★</sup> compatibility with Model 204=== | ||
Connect<span class="superstar">★</span> version 7.5 or 7.7 is compatible with Model 204 version 7.6. | |||
For more information on Connect<span class="superstar">★</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">★</span> wiki pages]]. | For more information on Connect<span class="superstar">★</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">★</span> wiki pages]]. | ||
Line 190: | Line 191: | ||
====Utf8ToUnicode and Utf16ToUnicode string methods==== | ====Utf8ToUnicode and Utf16ToUnicode string methods==== | ||
The <var>[[Utf8ToUnicode (String function)|Utf8ToUnicode]]</var> and <var>[[Utf16ToUnicode (String function)|Utf16ToUnicode]]</var> <var>String</var> methods can now handle values that cannot be translated into EBCDIC. The <var>AllowUntranslatable</var> argument, now available for general use and <var>True</var> by default, specifies that such values will be stored into the target Unicode string rather than producing an exception. | The <var>[[Utf8ToUnicode (String function)|Utf8ToUnicode]]</var> and <var>[[Utf16ToUnicode (String function)|Utf16ToUnicode]]</var> <var>String</var> methods can now handle values that cannot be translated into EBCDIC. The <var>AllowUntranslatable</var> argument, now available for general use and <var>True</var> by default, specifies that such values will be stored into the target Unicode string rather than producing an exception. | ||
===New XHTML entities for square-bracket characters=== | |||
By applying zap <code>76Z260</code>, <b>[</b> and <b>]</b> 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: | |||
<p class="code"><nowiki>*/pers[@name="Hector"] </nowiki></p> | |||
Code like this was recommended under version 7.5 of Model 204: | |||
<p class="code">%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) </p> | |||
Under version 7.6, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above: | |||
<p class="code">%myXmldoc:print('*/pers<b>[</b>@name="Hector"<b>]</b>':u)</p> | |||
===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 initially provided by zap maintenance. | |||
==Janus Web Server enhancements== | ==Janus Web Server enhancements== | ||
===Chunked encoding support=== | ===Chunked encoding support=== | ||
Janus Web support for HTTP 1.1 chunked encoding is added. The V7.6 Janus Web Server handles inbound chunked HTTP requests, but it does not send chunked output because it always knows the exact length of the entire response. | Janus Web [[Janus Web Server performance#Janus Web Server and chunked encoding|support for HTTP 1.1 chunked encoding]] is added. The V7.6 Janus Web Server handles inbound chunked HTTP requests, but it does not send chunked output because it always knows the exact length of the entire response. | ||
For more information about chunked encoding, see http://en.wikipedia.org/wiki/Chunked_transfer_encoding. | For more information about chunked encoding, see http://en.wikipedia.org/wiki/Chunked_transfer_encoding. | ||
Line 200: | Line 220: | ||
===SCREENTHROW setting for Janus Web Legacy=== | ===SCREENTHROW setting for Janus Web Legacy=== | ||
The new [[SCREENTHROW and NOSCREENTHROW (JANUS DEFINE parameters)|SCREENTHROW]] setting for Janus Web ports allows Janus Web Legacy applications to trap client errors rather than deferring to the default Janus Web Legacy support error handling behavior. | The new [[SCREENTHROW and NOSCREENTHROW (JANUS DEFINE parameters)|SCREENTHROW]] setting for Janus Web ports allows Janus Web Legacy applications to trap client errors rather than deferring to the default Janus Web Legacy support error handling behavior. | ||
===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 can be removed in version 7.6 (by zap maintenance). | |||
Also, the automatic <var>JANUS WEB ALLOW</var> rule, which allowed any user to access the port without requiring a login, is changed to | |||
require a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access a <i>non-SSL</i> Janus Web port: | |||
<p class="code">JANUS WEB <i>portname</i> DISALLOW * </p> | |||
<p> | |||
This rule applies (with zap 76Z418) in version 7.6, unless overridden by user-added rules.</p> | |||
<blockquote class="note"> | |||
<p><b>Note:</b> With 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: </p> | |||
<p class="code">RESET WEBDFLT=1</p> | |||
</blockquote> | |||
==Fast/Unload enhancements== | ==Fast/Unload enhancements== | ||
Line 206: | Line 239: | ||
[[Fast/Unload overview#fuhpo|Fast/Unload HPO]] (High Performance Option) is a Model 204 7.6 add-on feature that activates zIIP processing for Fast/Unload <i>when invoked by the Fast/Unload Soul Interface</i>. | [[Fast/Unload overview#fuhpo|Fast/Unload HPO]] (High Performance Option) is a Model 204 7.6 add-on feature that activates zIIP processing for Fast/Unload <i>when invoked by the Fast/Unload Soul Interface</i>. | ||
The feature requires setting the <var>[[FUNMTASK parameter|FUNMTASK]]</var> parameter, and it requires purchase of the | The feature requires setting the <var>[[FUNMTASK parameter|FUNMTASK]]</var> parameter, and it requires purchase of the [[#M204 HPO|M204 HPO]] feature. | ||
<p class="note"><b>Note:</b> This feature does not provide zIIP support for PGM=FUNLOAD; that support becomes available with Model 204 7.7. </p> | <p class="note"><b>Note:</b> This feature does not provide zIIP support for PGM=FUNLOAD; that support becomes available with Model 204 7.7. </p> | ||
===FUSI | ===FUSI: new product name for SOUL access to Fast/Unload=== | ||
The [[Fast/Unload SOUL Interface]] (FUSI), purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program. | The [[Fast/Unload SOUL Interface]] (FUSI), purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program. | ||
<!-- Further information TBD, including IODEV 25 threads, etc. --> | <!-- Further information TBD, including IODEV 25 threads, etc. --> | ||
===Change to Fast/Unload installation=== | ===Change to Fast/Unload installation=== | ||
Fast/Unload is no longer loaded as a separate load module. See [[#Notes for system manager and installer|Notes for system manager and installer]]. | Fast/Unload is no longer loaded as a separate load module (when using the Fast/Unload Soul Interface). See [[#Notes for system manager and installer|Notes for system manager and installer]]. | ||
==System management enhancements== | ==System management enhancements== | ||
===Model 204 version number added to SMF records=== | ===Model 204 version number added to SMF records=== | ||
A one byte, hexadecimal representation of the Model 204 version number has been added to both [[Using system statistics#System Management Facility record layout and statistics|SMF records]] (logout and since-last) at offset X'39'. For | A one-byte, hexadecimal representation of the Model 204 version number has been added to both [[Using system statistics#System Management Facility record layout and statistics|SMF records]] (logout and since-last) at offset X'39'. For version 7.6, the value is <code>X'4C'</code> (76 decimal). | ||
==Performance enhancements== | ==Performance enhancements== | ||
=== | ===M204 HPO=== | ||
The approach to zIIP (IBM System z Integrated Information Processor) support in Model 204 prior to version 7.6 is to offload to zIIP only [[Performance monitoring and tuning#Model 204 workload eligible for zIIP offload|certain eligible code]] safe for execution on the zIIP engine. The V7.6 improvements to the zIIP offload make most of the Model 204 code zIIP tolerant: almost all MP-capable code (Model 204 code that may run on an MP subtask) is offloaded to zIIP. Code that cannot be executed on zIIP uses the MP subtask or a maintask. | The approach to zIIP (IBM System z Integrated Information Processor) support in Model 204 prior to version 7.6 is to offload to zIIP only [[Performance monitoring and tuning#Model 204 workload eligible for zIIP offload|certain eligible code]] safe for execution on the zIIP engine. The V7.6 improvements to the zIIP offload make most of the Model 204 code zIIP tolerant: almost all MP-capable code (Model 204 code that may run on an MP subtask) is offloaded to zIIP. Code that cannot be executed on zIIP uses the MP subtask or a maintask. | ||
<p class="note"><b>Note:</b> | <p class="note"><b>Note:</b> | ||
While a limited version of this capability is available to all customers, the | While a limited version of this capability is available to all customers, the fully expanded zIIP support is known as [[Performance monitoring and tuning#off204zip|M204 HPO]], and it requires an additional license. For more information, [[Contacting Rocket Software Technical Support|contact Rocket Software]].</p> | ||
<p> | <p> | ||
This feature is for z/OS systems only. As in previous releases, specifying a nonzero value for the <var>[[AMPSUBZ parameter|AMPSUBZ]]</var> parameter activates zIIP processing.</p> | This feature is for z/OS systems only. As in previous releases, specifying a nonzero value for the <var>[[AMPSUBZ parameter|AMPSUBZ]]</var> parameter activates zIIP processing.</p> | ||
Line 245: | Line 278: | ||
<li>Parameter <var>[[ZQMAX parameter|ZQMAX]]</var> is deprecated. If you have specified a value for <var>ZQMAX</var>, it is now ignored.</li> | <li>Parameter <var>[[ZQMAX parameter|ZQMAX]]</var> is deprecated. If you have specified a value for <var>ZQMAX</var>, it is now ignored.</li> | ||
<li>X'01' | <li>For zIIP processing, if FUND or FUNDLE is linked into the Model 204 load module, the X'01' bit of <var>[[SIRFUNC parameter|SIRFUNC]]</var> must be set or the run is cancelled.</li> | ||
<li>The <var>[[XMEMOPT parameter|XMEMOPT]]</var> X'02' bit was not documented as necessary for zIIPs. It <i>is</i> necessary as of V7.6.</li> | <li>The <var>[[XMEMOPT parameter|XMEMOPT]]</var> X'02' bit was not documented as necessary for zIIPs. It <i>is</i> necessary as of V7.6.</li> | ||
<li>It is now <b><i>strongly recommended</i></b> that customers running MP/204 <b>not</b> set the X'40' bit of the <var>[[SCHDOPT parameter|SCHDOPT]]</var> parameter | <li>It is now <b><i>strongly recommended</i></b> that customers running MP/204 <b>not</b> set the X'40' bit of the <var>[[SCHDOPT parameter|SCHDOPT]]</var> parameter, since MP subtasks will no longer steal work from zIIP SRBs unless they seem overloaded, in which case you probably do not want the <var>SCHDOPT</var> X'40' bit to prevent MP subtasks from helping out.</li> | ||
</ul> | </ul> | ||
====Fast/Unload HPO==== | ====Fast/Unload HPO==== | ||
[[#Fast/Unload HPO|Fast/Unload HPO]] (High Performance Option) is a new product that activates zIIP processing for the <var class="product">Fast/Unload Soul Interface</var> (only). | |||
===64-bit addressing and Above The Bar (ATB) storage=== | ===64-bit addressing and Above The Bar (ATB) storage=== | ||
Line 283: | Line 314: | ||
</ul> | </ul> | ||
<p class="note">'''Notes:''' | <p class="note">'''Notes:''' | ||
The settings for each server table above the bar are independent of each other. <br /> However, you cannot set bits in both SERVNSA and SERVGA.</p> | The settings for each server table above the bar are independent of each other. <br /> However, you cannot set bits in both <var>SERVNSA</var> and <var>SERVGA</var>.</p> | ||
====TBO buffers, the Procedure dictionary, and Longstrings==== | ====TBO buffers, the Procedure dictionary, and Longstrings==== | ||
Line 290: | Line 321: | ||
<li> | <li> | ||
Procedure dictionary pages will be in the above-the-bar buffer pool if <var>[[NUMBUFG parameter|NUMBUFG]]</var> is set.</li> | Procedure dictionary pages will be in the above-the-bar buffer pool if <var>[[NUMBUFG parameter|NUMBUFG]]</var> is set.</li> | ||
<li>TBO and longstring pages will accessed either directly from in-memory CCATEMP, if <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> is set, or from the above-the-bar buffer pool if <var>TEMPPAGE</var> is not set but <var>NUMBUFG</var> is.</li> | <li>TBO and longstring pages will be accessed either directly from in-memory CCATEMP, if <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> is set, or from the above-the-bar buffer pool if <var>TEMPPAGE</var> is not set but <var>NUMBUFG</var> is.</li> | ||
</ul> | </ul> | ||
Line 305: | Line 336: | ||
The new <var>[[#ZHPF (new)|ZHPF]]</var> command displays zHPF capabilities for each data set in a currently opened file. | The new <var>[[#ZHPF (new)|ZHPF]]</var> command displays zHPF capabilities for each data set in a currently opened file. | ||
<!-- removed; not finished; Journal and checkpoint processing enhancements | |||
New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter. | |||
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. | |||
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. | Note: I ask Leonard In what circumstances should these PSTs be invoked by user? From Leonard: Journal and checkpoint project is not finished yet. It is strictly a performance improvement, NSUBTSK should be inspected to be big enough to accommodate 3 more PST. | ||
--> | |||
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. | |||
===Support for OI CHUNK field group members=== | ===Support for OI CHUNK field group members=== | ||
The [[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK attribute]] for DEFINE FIELD was introduced in Model 204 version 7.5 to improve the efficiency of range finds using Ordered Index (OI) processing. The CHUNK attribute can | The [[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK attribute]] for <var>DEFINE FIELD</var> was introduced in Model 204 version 7.5 to improve the efficiency of range finds using Ordered Index (OI) processing. The <var>CHUNK</var> attribute can be specified for field group members. | ||
==Debugging and testing enhancements== | ==Debugging and testing enhancements== | ||
===Unicode linefeed now causes line break on print=== | ===Unicode linefeed now causes line break on print=== | ||
Printing or auditing a | Printing or auditing a <var>Unicode</var> string invokes an [[Unicode#Implicit_Unicode_conversions|implicit conversion to EBCDIC]]. If the string contains a Unicode linefeed character (U+000a), a new line will now be started on the output device, rather than a display of the linefeed character's hex encoding (<code>&#x000A;</code>) as before. <p> | ||
This change should make it much easier to look at <var>Unicode</var> strings that contain formatting linefeeds. The feature works for any display-oriented statements such as <var>Print</var>, <var>Audit</var>, <var>Trace</var>, <var>PrintText</var>, <var>AuditText</var>, <var>TraceText</var>, <var>Text</var>, and so on. </p> | |||
===SoftSpy=== | ===SoftSpy=== | ||
Line 329: | Line 358: | ||
===Janus/TN3270 Debugger=== | ===Janus/TN3270 Debugger=== | ||
<ul> | <ul> | ||
<li>Product name change. <p>The "Sirius Debugger" [[Debugger|product]] name is changed to "TN3270 Debugger."</p></li> | <li>Product name change. | ||
<p> | |||
The "Sirius Debugger" [[Debugger|product]] name is changed to "TN3270 Debugger."</p></li> | |||
<li>Synonym for SIRIUS DEBUG command. <p>A synonym, <var>TN3270 DEBUG</var>, is made available for the <var>[[SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command|SIRIUS DEBUG]]</var> command and all its subcommands.</p> | <li>Synonym for <var>SIRIUS DEBUG</var> command. | ||
</li> | <p> | ||
A synonym, <var>TN3270 DEBUG</var>, is made available for the <var>[[SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command|SIRIUS DEBUG]]</var> command and all its subcommands.</p></li> | |||
</ul> | </ul> | ||
==Compatibility issues== | ==Compatibility issues== | ||
===Unicode linefeed line break=== | ===Unicode linefeed line break=== | ||
While the [[#Unicode linefeed now causes line break on print|Unicode linefeed line break]] feature is likely to make it easier to examine <var>Unicode</var> strings, in theory it could cause a backward-compatibility problem for applications that parse the results of a <var>Print</var> of <var>Unicode</var> data, expecting the <code>&#x000A;</code> values to be present. | |||
===M204XSVC as an SVC=== | |||
(for z/OS, z/VM CMS)<br /> | |||
Zap 76Z043 applies to and enables you to use a Model 204 7.6 load module with an [[Defining the user environment (CCAIN)#204xsvc|M204XSVC]] module from version 7.4 or 7.5 without applying any changes to the SVC. You need to apply this zap only if all of these are true: | |||
<ul> | |||
<li>Your site installed M204XSVC <i><b>as an SVC</b></i> in version 7.4 or 7.5 of Model 204. </li> | |||
<li>M204XSVC is not linked into the Online, or the Online is not APF authorized. </li> | |||
<li>The <var>XMEMSVC</var> parameter is specified in the CCAIN. </li> | |||
</ul> | |||
Once you have applied zap 76Z043, you can use a 7.6 load module with: | Once you have applied zap 76Z043, you can use a 7.6 load module with: | ||
Line 350: | Line 389: | ||
</ul> | </ul> | ||
<p class="note"><b>Note:</b> When a pre-7.6 M204XSVC is used with 7.6, the zHPF feature is not supported and its setting ( | <p class="note"><b>Note:</b> When a pre-7.6 M204XSVC is used with 7.6, the [[Performance monitoring and tuning#High Performance FICON (zHPF)|zHPF feature]] is not supported and its setting (X'10' in <var>[[SYSOPT2 parameter|SYSOPT2]]</var>) is reset with no message issued.</p> | ||
<b>z/VM CMS users:</b> In order to apply this zap to 7.6, you need to relink the M204CMS module as well as the ONLINE module. [[Contacting Rocket Software Technical Support|Contact Technical Support]] for details. | <b>z/VM CMS users:</b> In order to apply this zap to 7.6, you need to relink the M204CMS module as well as the ONLINE module. [[Contacting Rocket Software Technical Support|Contact Technical Support]] for details. | ||
Line 360: | Line 399: | ||
The Online will still come up but <var>APSYPAGE</var> will have no effect. See [[APSYPAGE parameter]] for information about using the <var>RESPAGE</var> parameter instead of <var>APSYPAGE</var>. | The Online will still come up but <var>APSYPAGE</var> will have no effect. See [[APSYPAGE parameter]] for information about using the <var>RESPAGE</var> parameter instead of <var>APSYPAGE</var>. | ||
===IODEV=37 is no longer supported=== | |||
Line-at-a-time terminals used on IBM z/OS via the IBM Network Terminal Option (2741s, teletypes, and teletype-compatibles), specified by <var>[[IODEV parameter|IODEV]]</var>=37, are no longer supported. | |||
===NEBUFF default value is now 40=== | ===NEBUFF default value is now 40=== | ||
The default value of the <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for Fast/Unload SOUL Interface (FUSI) is now 40. (NEBUFF had a default value of 2 in previous versions.) See also [[#FUNL.NEB (new)|FUNL.NEB]]. | The default value of the <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for Fast/Unload SOUL Interface (FUSI) is now 40. (<var>NEBUFF</var> had a default value of 2 in previous versions.) See also [[#FUNL.NEB (new)|FUNL.NEB]]. | ||
=== | ===Unlabeled FDV statement compilation errors=== | ||
Version 7.6 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: | Version 7.6 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 <var>FDV</var>. Such statements are no longer allowed. For example, the following was allowed in older versions of Model 204: | ||
<p class="code"> | <p class="code">a: audit 'About to FDV' | ||
fdv foo | |||
b: frv in a</p> | |||
Inserting SOUL code between a label and an FDV statement | Inserting SOUL code between a label and an <var>FDV</var> statement | ||
is no longer allowed, and so the result of the above is: | is no longer allowed, and so the result of the above is: | ||
<p class="code">M204.0311 Unacceptable statement reference</p> | <p class="code">M204.0311 Unacceptable statement reference</p> | ||
This change was introduced as maintenance in | This change was introduced as zap maintenance in versions 7.5 and 7.6 of Model 204. | ||
===$ListNew cannot be used in Initial clause=== | |||
<var>$ListNew</var> cannot be used in the <var>Initial</var> clause of a [[Using_variables_and_values_in_computation#Declare_statements_for_.25variables|declaration statement]]. | |||
<p>This change was introduced as zap maintenance in versions 7.5, 7.6, and 7.7 of Model 204.</p> | |||
==New and changed commands== | ==New and changed commands== | ||
Line 383: | Line 428: | ||
--> | --> | ||
===SWITCH STREAM (new parameter: RESET)=== | ===SWITCH STREAM (new parameter: RESET)=== | ||
The <var>[[SWITCH STREAM command|SWITCH STREAM]]</var> command has added an optional RESET parameter that | The <var>[[SWITCH STREAM command|SWITCH STREAM]]</var> command has added an optional <var>RESET</var> parameter that causes any disabled parallel GDG members to be reopened during the switch. <var>RESET</var> is valid only for a CCAJLOG stream specified as a Parallel GDG. | ||
===TN3270 DEBUG (new synonym for SIRIUS DEBUG)=== | ===TN3270 DEBUG (new synonym for SIRIUS DEBUG)=== | ||
Line 424: | Line 469: | ||
===FUNL.NEB (new)=== | ===FUNL.NEB (new)=== | ||
The new FUNL.NEB parameter enables you to change the default <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for all subsequent Fast/Unload SOUL Interface (FUSI) requests. The default value of FUNL.NEB is 0, meaning that the original NEBUFF default value (40) is used. You can also specify a value greater than 1 to be the new NEBUFF default. FUNL.NEB=1 is not allowed. | The new <var>[[FUNL.NEB parameter|FUNL.NEB]]</var> parameter enables you to change the default <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for all subsequent Fast/Unload SOUL Interface (FUSI) requests. The default value of <var>FUNL.NEB</var> is 0, meaning that the original <var>NEBUFF</var> default value (40) is used. You can also specify a value greater than 1 to be the new <var>NEBUFF</var> default. <code>FUNL.NEB=1</code> is not allowed. | ||
===FUNMTASK (new)=== | ===FUNMTASK (new)=== | ||
The new <var>[[FUNMTASK parameter|FUNMTASK]]</var> parameter specifies whether Fast/Unload | The new <var>[[FUNMTASK parameter|FUNMTASK]]</var> parameter specifies whether [[Fast/Unload SOUL Interface]] (FUSI) requests are to be executed on a z/OS subtask or on one of these: the Model 204 maintask, an MP/204 subtask, or the zIIP support SRB. | ||
===FUNPGM (obsolete)=== | ===FUNPGM (obsolete)=== | ||
The <var>[[FUNPGM parameter|FUNPGM]]</var> parameter is now obsolete, because the Fast/Unload CSECTs are all linked with the Online and the Fast/Unload load module is no longer loaded as a separate load module. | The <var>[[FUNPGM parameter|FUNPGM]]</var> parameter is now obsolete, because the Fast/Unload CSECTs are all linked with the Online, and the Fast/Unload load module is no longer loaded as a separate load module. | ||
===FUNTSKN (new functionality)=== | |||
As part of support for the [[Fast/Unload SOUL Interface]] (FUSI), setting the <var>[[FUNTSKN parameter|FUNTSKN]]</var> parameter now causes implicit definition of IODEV=25 threads, as many as the value of FUNTSKN. | |||
===LSERVERG (new)=== | ===LSERVERG (new)=== | ||
Line 442: | Line 486: | ||
===MAXOND (new)=== | ===MAXOND (new)=== | ||
The new <var>[[MAXOND parameter|MAXOND]]</var> parameter defines the number of times an | The new <var>[[MAXOND parameter|MAXOND]]</var> parameter defines the number of times an [[Subroutines#On statement|On unit]] can be entered before the evaluation is terminated. | ||
===NEBUFF (changed default value)=== | ===NEBUFF (changed default value)=== | ||
The default value of the <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for Fast/Unload SOUL Interface (FUSI) requests is now 40. (Prior to 7.6, the default NEBUFF value was 2.) See also [[#FUNL.NEB (new)|FUNL.NEB]]. | The default value of the <var>[[Fast/Unload program parameters#NEbuff=n|NEBUFF]]</var> parameter for Fast/Unload SOUL Interface (FUSI) requests is now 40. (Prior to 7.6, the default <var>NEBUFF</var> value was 2.) See also [[#FUNL.NEB (new)|FUNL.NEB]]. | ||
===PWDCOLON (new; 7.6 only)=== | |||
<blockquote class="note"><b>Note:</b> This feature requires zap 76Z291. | |||
<p><var>[[PWDCOLON parameter|PWDCOLON]]</var> is applicable to version 7.6 only; it will be superseded in 7.7 by additional password functionality.</p></blockquote> | |||
<p>The <var>PWDCOLON</var> system parameter allows the use of colons in login passwords.</p> | |||
When <code>PWDCOLON=1</code> is set in CCAIN, users can enter colons in login passwords. Recognizing colons in these passwords also means that users cannot [[LOGIN or LOGON command#Setting a password|change their passwords]] with the existing <var class="term">oldpassword</var>:<var class="term">newpassword</var> construction. When <var>PWDCOLON</var> is on, passwords can only be changed in one of the following ways: | |||
<ul> | |||
<li>using the <var>[[LOGCTL command: Modifying user ID entries in the password table|LOGCTL]]</var> C command (system manager privileges required)</li> | |||
<li>using the <var>[[$Sir_Login]]</var> function call (in Janus Web Server and Janus Sockets applications)</li> | |||
</ul> | |||
===RCVOPT (new setting: X'20')=== | ===RCVOPT (new setting: X'20')=== | ||
Line 458: | Line 514: | ||
===SERVGA (new settings)=== | ===SERVGA (new settings)=== | ||
The <var>[[SERVGA parameter|SERVGA]]</var> parameter now has settings to allocate additional server tables in the ATB swappable-server area. | The <var>[[SERVGA parameter|SERVGA]]</var> parameter now has settings to allocate additional server tables in the ATB swappable-server area. | ||
===SERVNSA (new settings)=== | ===SERVNSA (new settings)=== | ||
The <var>[[SERVNSA parameter|SERVNSA]]</var> parameter now has settings to allocate additional server tables in the ATB non-swappable-server area. | The <var>[[SERVNSA parameter|SERVNSA]]</var> parameter now has settings to allocate additional server tables in the ATB non-swappable-server area. | ||
===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: | |||
<p class="code">M204.1149: SERVSIZE has been set to its minimum value: 65536 | |||
</p> | |||
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: | |||
<p class="code">M204.0163: SERVSIZE increased to 65536 | |||
</p> | |||
<p> | |||
This change was introduced as zap maintenance in version 7.4, 7.5, and 7.6 of Model 204. | |||
</p> | |||
===SYSOPT2 (new setting)=== | ===SYSOPT2 (new setting)=== | ||
Line 469: | Line 538: | ||
<!-- End of new/changed parameter subsections; please keep them alphabetized by parameter name --> | <!-- End of new/changed parameter subsections; please keep them alphabetized by parameter name --> | ||
<!-- ***************************************************************************************** --> | <!-- ***************************************************************************************** --> | ||
==Notes for system manager and installer== | ==Notes for system manager and installer== | ||
===Fast/Unload and FUNPGM=== | ===Fast/Unload and FUNPGM=== | ||
In version 7.6 (of Model 204 and of Fast/Unload), the Fast/Unload CSECTs are all linked with the Online. This | In version 7.6 (of Model 204 and of Fast/Unload), the Fast/Unload CSECTs are all linked with the Online. This changes the implementation of the [[Fast/Unload SOUL Interface|Fast/Unload SOUL Interface (FUSI)]], and it was made primarily to enable the [[#Fast/Unload HPO|use of zIIPs with the FUSI]]. The main implication of this change is that the <var>[[FUNPGM parameter|FUNPGM]]</var> parameter is now obsolete, because Fast/Unload is not loaded as a separate load module. | ||
===CRAM SVC installation is deprecated=== | |||
The CRAM SVC installation has been deprecated as of version 7.5. <br />Installation of CRAM-XDM is described as part of the [[Model 204 installation]]. | |||
==Documentation conversion to wiki format== | ==Documentation conversion to wiki format== | ||
Line 487: | Line 558: | ||
See [[New and updated messages in Model 204 version 7.6]] for details. | See [[New and updated messages in Model 204 version 7.6]] for details. | ||
[[Category: Release notes]] | [[Category: Release notes|Model 204 version 7.6]] |
Latest revision as of 21:22, 6 August 2018
These release notes describe new features, enhancements, and other changes contained in Model 204 version 7.6, generally available in January, 2016.
Overview
These release notes contain installation and features information for the Rocket Model 204 version 7.6 release. Before beginning your installation, please read through this information about product installation and changes.
New in this release
This section summarizes the highlights of Model 204 version 7.6. For a full list of features, refer to the Table of Contents.
Category | Feature |
---|---|
SOUL (User Language) |
|
Performance |
|
Fast/Unload |
|
Janus products |
|
Debugging and testing |
|
Operating system and hardware requirements
Operating system requirements
- IBM z/OS
- All IBM supported releases up to and including z/OS 2.3.
(For z/OS 2.2, see IBM z/OS 2.2 PTF requirement.)
(For z/OS 2.1, see IBM z/OS 2.1 compatibility issue.) - zHPF support requires version 2.1.
- Large (1 MB) page support requires version 1.9.
- Extended address volumes (EAV) requires version 1.12.
Version 1.07 is sufficient for all functionality except for the following features:
On z/OS, Model 204 release 7.6 operates as an APF authorized load module, as required by many 7.6 features.
To run Model 204 unauthorized, contact Technical Support. - All IBM supported releases up to and including z/OS 2.3.
- IBM z/VM
- Versions supported: z/VM version 5.4 through 6.3.
- IBM z/VSE
- Versions supported: z/VSE version 5.1 and 5.2.
Hardware requirements
In general, Model 204 version 7.6 requires the IBM z/890 or above processor.
However, the IBM z10 or above processor is required for the following features:
- large (1 MB) page support
- IBM's High Performance FICON (zHPF) support
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.6.
For more information on Connect★ installation, see the Connect★ wiki pages.
SOUL enhancements
New and changed SOUL statements
The Private keyword has been added to Class declarations, and Friend declarations have been added to Class blocks.
Members of a private class can be accessed only by the class itself or any class declared as a friend of the private class.
New and changed classes and methods
Json class
The Json class has been created to facilitate exchange of data with other platforms using the JSON format. This class contains a large number of methods and also adds three new exception classes: InvalidJsonType, JsonCircularReference, and JsonParseError, and one new enumeration: JsonType. In addition, the JsonParse function was added to the Unicode intrinsic class.
Web class
The Web class has been created as a container for Janus Web Server specific methods. This class contains two new methods: ScreenInputCallback and ScreenOutputCallback. There is also an associated new system type: WebScreenCallback and a new WebScreenException exception class.
"SSL" String methods
These new methods are added:
Method | Description |
---|---|
AES128CBCdecrypt | AES 128-bit key decryption |
AES128CBCencrypt | AES 128-bit key decryption |
AES128decrypt | AES 128-bit key decryption |
AES128encrypt | AES 128-bit key decryption |
AES192CBCdecrypt | AES 192-bit key CBC decryption |
AES192CBCencrypt | AES 192-bit key CBC decryption |
AES192decrypt | AES 192-bit key decryption |
AES192encrypt | AES 192-bit key decryption |
AES256CBCdecrypt | AES 256-bit key CBC decryption |
AES256CBCencrypt | AES 256-bit key CBC decryption |
AES256decrypt | AES 256-bit key decryption |
AES256encrypt | AES 256-bit key decryption |
DEA128CBCdecrypt | DEA 128-bit key decryption |
DEA128CBCencrypt | DEA 128-bit key decryption |
DEA128decrypt | DEA 128-bit key decryption |
DEA128encrypt | DEA 128-bit key decryption |
DEA192CBCdecrypt | DEA 192-bit key CBC decryption |
DEA192CBCencrypt | DEA 192-bit key CBC decryption |
DEA192decrypt | DEA 192-bit key decryption |
DEA192encrypt | DEA 192-bit key decryption |
DEA64CBCdecrypt | DEA 64-bit key CBC decryption |
DEA64CBCencrypt | DEA 64-bit key CBC decryption |
DEA64decrypt | DEA 64-bit key decryption |
DEA64encrypt | DEA 64-bit key decryption |
SHA224digest | 224-bit SHA-2 digest |
SHA256digest | 256-bit SHA-2 digest |
Utf8ToUnicode and Utf16ToUnicode string methods
The Utf8ToUnicode and Utf16ToUnicode String methods can now handle values that cannot be translated into EBCDIC. The AllowUntranslatable argument, now available for general use and True by default, specifies that such values will be stored into the target Unicode string rather than producing an exception.
New XHTML entities for square-bracket characters
By applying zap 76Z260
, [ and ] are newly supported as XMHTL entities (notably in the U method). This provides a better approach to specifying square brackets (such as for XPath expressions) than the formerly recommended use of Static %variables initialized to the correct values.
For example, to produce an XPath expression equivalent to the following:
*/pers[@name="Hector"]
Code like this was recommended under version 7.5 of Model 204:
%lsq is string len 1 static initial('['):u %rsq is string len 1 static initial(']'):u . . . %myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq)
Under version 7.6, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
%myXmldoc:print('*/pers[@name="Hector"]':u)
New default certificate-signing algorithm
Janus Network Security as well as the StringList methods AppendSignedCertificate and AppendSignedClientCertificate methods have changed their default signature algorithm from SHA-1 to SHA-256.
This change is initially provided by zap maintenance.
Janus Web Server enhancements
Chunked encoding support
Janus Web support for HTTP 1.1 chunked encoding is added. The V7.6 Janus Web Server handles inbound chunked HTTP requests, but it does not send chunked output because it always knows the exact length of the entire response.
For more information about chunked encoding, see http://en.wikipedia.org/wiki/Chunked_transfer_encoding.
SCREENTHROW setting for Janus Web Legacy
The new SCREENTHROW setting for Janus Web ports allows Janus Web Legacy applications to trap client errors rather than deferring to the default Janus Web Legacy support error handling behavior.
Janus Web Server default rules
Janus Web used to automatically implement two web server ON rules to set up access to the Janus Web sample home page and to demonstration application procedures. These rules can be removed in version 7.6 (by zap maintenance).
Also, the automatic JANUS WEB ALLOW rule, which allowed any user to access the port without requiring a login, is changed to require a system administrator to explicitly define ALLOW rules to enable users to access a non-SSL Janus Web port:
JANUS WEB portname DISALLOW *
This rule applies (with zap 76Z418) in version 7.6, unless overridden by user-added rules.
Note: With zap 76Z420, you can make the default ALLOW rule as it was in version 7.5 and earlier (
ALLOW *
). To do so, turn on the 1 bit of the WEBDFLT parameter:RESET WEBDFLT=1
Fast/Unload enhancements
Fast/Unload HPO
Fast/Unload HPO (High Performance Option) is a Model 204 7.6 add-on feature that activates zIIP processing for Fast/Unload when invoked by the Fast/Unload Soul Interface.
The feature requires setting the FUNMTASK parameter, and it requires purchase of the M204 HPO feature.
Note: This feature does not provide zIIP support for PGM=FUNLOAD; that support becomes available with Model 204 7.7.
FUSI: new product name for SOUL access to Fast/Unload
The Fast/Unload SOUL Interface (FUSI), purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program.
Change to Fast/Unload installation
Fast/Unload is no longer loaded as a separate load module (when using the Fast/Unload Soul Interface). See Notes for system manager and installer.
System management enhancements
Model 204 version number added to SMF records
A one-byte, hexadecimal representation of the Model 204 version number has been added to both SMF records (logout and since-last) at offset X'39'. For version 7.6, the value is X'4C'
(76 decimal).
Performance enhancements
M204 HPO
The approach to zIIP (IBM System z Integrated Information Processor) support in Model 204 prior to version 7.6 is to offload to zIIP only certain eligible code safe for execution on the zIIP engine. The V7.6 improvements to the zIIP offload make most of the Model 204 code zIIP tolerant: almost all MP-capable code (Model 204 code that may run on an MP subtask) is offloaded to zIIP. Code that cannot be executed on zIIP uses the MP subtask or a maintask.
Note: While a limited version of this capability is available to all customers, the fully expanded zIIP support is known as M204 HPO, and it requires an additional license. For more information, contact Rocket Software.
This feature is for z/OS systems only. As in previous releases, specifying a nonzero value for the AMPSUBZ parameter activates zIIP processing.
User-written $functions and zIIPs
Instead of having to indicate what code should run on zIIP, it is only necessary now to indicate what Assembler code cannot run on zIIP. Customers planning to use zIIP processing must do either of these:
- Inspect any user-written $functions for non-tolerant code (code that uses an SVC instruction or system services that may use SVC, like BSAM, VTAM, task-mode z/OS macros), which must be bracketed with
SRBMODE OFF
andSRBMODE ON
. - Specify
MP=NO
(the default) or no MP setting at all in the function table to cause $functions to run on a maintask. Any other value for MP enables $functions to run on zIIP subtasks.
It is not always obvious whether code can or cannot run on a zIIP subtask. Even if all explicit SVCs and non-task-mode system macros issued by Model 204 have been identified and bracketed, some may be issued implicitly by z/OS or other services, so user testing is important.
Parameter changes for zIIP usage
The following are V7.6 changes to the documented recommendations for the parameters that initiate and control Model 204 zIIP processing:
- Parameter ZQMAX is deprecated. If you have specified a value for ZQMAX, it is now ignored.
- For zIIP processing, if FUND or FUNDLE is linked into the Model 204 load module, the X'01' bit of SIRFUNC must be set or the run is cancelled.
- The XMEMOPT X'02' bit was not documented as necessary for zIIPs. It is necessary as of V7.6.
- It is now strongly recommended that customers running MP/204 not set the X'40' bit of the SCHDOPT parameter, since MP subtasks will no longer steal work from zIIP SRBs unless they seem overloaded, in which case you probably do not want the SCHDOPT X'40' bit to prevent MP subtasks from helping out.
Fast/Unload HPO
Fast/Unload HPO (High Performance Option) is a new product that activates zIIP processing for the Fast/Unload Soul Interface (only).
64-bit addressing and Above The Bar (ATB) storage
Storage above the (2G) bar increases scalability, performance, and growth potential. 64-bit addressing is the de facto standard for Model 204.
- ATB support for FTBL was released with Model 204 version 7.4.
- ATB support for GTBL, NTBL, and QTBL was released with Model 204 version 7.5.
- ATB support for STBL, VTBL, and several other tables is added in Model 204 version 7.6.
When using non-swappable ATB server space, each user gets SERVNSSZ bytes of ATB space, even if the thread is logged out or running resident requests. For greater efficiency, Model 204 also provides swappable ATB server areas that can supplement or replace the non-swappable areas. These swappable ATB server areas are controlled by the SERVGA and SERVGSZ parameters.
As more features use ATB buffers, it is a good idea to reevaluate your ATB and BTB buffer usage.
STBL, VTBL, and other tables in ATB storage
STBL, VTBL, and several other tables can now be placed into swappable or non-swappable server storage area above the bar.
To store a table in non-swappable ATB storage:
To store a table in swappable ATB storage:
Notes:
The settings for each server table above the bar are independent of each other.
However, you cannot set bits in both SERVNSA and SERVGA.
TBO buffers, the Procedure dictionary, and Longstrings
64-bit addressing support for TBO buffers, the Procedure dictionary, and Longstrings is new in version 7.6:
- Procedure dictionary pages will be in the above-the-bar buffer pool if NUMBUFG is set.
- TBO and longstring pages will be accessed either directly from in-memory CCATEMP, if TEMPPAGE is set, or from the above-the-bar buffer pool if TEMPPAGE is not set but NUMBUFG is.
High Performance FICON (zHPF)
Model 204 version 7.6 supports IBM's High Performance FICON (zHPF) feature, which allows faster I/O by limiting the number of interactions between the channel and the device.
Required hardware and software:
- CPU: z10 and higher
- z/OS version: 2.01
- Disk subsystem: Contact your IT department to verify that your disk subsystem has the zHPF feature available and activated.
zHPF is not supported on z/CMS, z/VSE, or z/OS running under z/VM.
The new ZHPF command displays zHPF capabilities for each data set in a currently opened file.
Support for OI CHUNK field group members
The CHUNK attribute for DEFINE FIELD was introduced in Model 204 version 7.5 to improve the efficiency of range finds using Ordered Index (OI) processing. The CHUNK attribute can be specified for field group members.
Debugging and testing enhancements
Unicode linefeed now causes line break on print
Printing or auditing a Unicode string invokes an implicit conversion to EBCDIC. If the string contains a Unicode linefeed character (U+000a), a new line will now be started on the output device, rather than a display of the linefeed character's hex encoding (

) as before.
This change should make it much easier to look at Unicode strings that contain formatting linefeeds. The feature works for any display-oriented statements such as Print, Audit, Trace, PrintText, AuditText, TraceText, Text, and so on.
SoftSpy
As of version 7.5, the code for SoftSpy, the debugging, testing, and performance-tuning product, has been included in the Model 204 nucleus, significantly simplifying SoftSpy installation. SoftSpy remains a separately licensed Model 204 add-on product.
For more information about SoftSpy version 7.6, see the SoftSpy 7.6 release notes.
Janus/TN3270 Debugger
- Product name change.
The "Sirius Debugger" product name is changed to "TN3270 Debugger."
- Synonym for SIRIUS DEBUG command.
A synonym, TN3270 DEBUG, is made available for the SIRIUS DEBUG command and all its subcommands.
Compatibility issues
Unicode linefeed line break
While the Unicode linefeed line break feature is likely to make it easier to examine Unicode strings, in theory it could cause a backward-compatibility problem for applications that parse the results of a Print of Unicode data, expecting the 

values to be present.
M204XSVC as an SVC
(for z/OS, z/VM CMS)
Zap 76Z043 applies to and enables you to use a Model 204 7.6 load module with an M204XSVC module from version 7.4 or 7.5 without applying any changes to the SVC. You need to apply this zap only if all of these are true:
- Your site installed M204XSVC as an SVC in version 7.4 or 7.5 of Model 204.
- M204XSVC is not linked into the Online, or the Online is not APF authorized.
- The XMEMSVC parameter is specified in the CCAIN.
Once you have applied zap 76Z043, you can use a 7.6 load module with:
- M204XSVC version 7.4
- M204XSVC version 7.5 if zap 75Z345 was not applied or was removed by 76Z043. (If zap 75Z345 was applied but 76Z043 was not, message "M204.0077: Errors detected -- run cancelled" is issued and initialization terminates.)
Note: When a pre-7.6 M204XSVC is used with 7.6, the zHPF feature is not supported and its setting (X'10' in SYSOPT2) is reset with no message issued.
z/VM CMS users: In order to apply this zap to 7.6, you need to relink the M204CMS module as well as the ONLINE module. Contact Technical Support for details.
APSYPAGE parameter is obsolete
(applies to z/OS)
The APSYPAGE parameter has been disabled as of version 7.6. If APSYPAGE is non-zero, a warning will appear:
M204.2958: APSYPAGE obsolete as of 7.6
The Online will still come up but APSYPAGE will have no effect. See APSYPAGE parameter for information about using the RESPAGE parameter instead of APSYPAGE.
IODEV=37 is no longer supported
Line-at-a-time terminals used on IBM z/OS via the IBM Network Terminal Option (2741s, teletypes, and teletype-compatibles), specified by IODEV=37, are no longer supported.
NEBUFF default value is now 40
The default value of the NEBUFF parameter for Fast/Unload SOUL Interface (FUSI) is now 40. (NEBUFF had a default value of 2 in previous versions.) See also FUNL.NEB.
Unlabeled FDV statement compilation errors
Version 7.6 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 introduced as zap maintenance in versions 7.5 and 7.6 of Model 204.
$ListNew cannot be used in Initial clause
$ListNew cannot be used in the Initial clause of a declaration statement.
This change was introduced as zap maintenance in versions 7.5, 7.6, and 7.7 of Model 204.
New and changed commands
SWITCH STREAM (new parameter: RESET)
The SWITCH STREAM command has added an optional RESET parameter that causes any disabled parallel GDG members to be reopened during the switch. RESET is valid only for a CCAJLOG stream specified as a Parallel GDG.
TN3270 DEBUG (new synonym for SIRIUS DEBUG)
TN3270 DEBUG is now available as a synonym for the SIRIUS DEBUG command and all its subcommands.
ZHPF (new)
The ZHPF command displays zHPF capabilities for each data set for a currently opened file.
Displayed value | Meaning |
---|---|
Supported: YES |
zHPF-type I/O (called "transport mode I/O") can be used for the data set. |
Supported: NO | Hardware or z/OS support for zHPF functionality is insufficient (for example, when z/OS runs under VM). |
Supported: N/A | zHPF support is not available at all on z/OS or on the hardware level. |
New and changed parameters
CFROPTS (new)
The new CFROPTS system parameter makes it possible to request that Model 204 use strict fair share enqueuing for critical file resource lock conflicts.
DSPOPT (new setting: X'04')
The new X'04' setting for the DSPOPT parameter uses compression for 64-bit in-storage server swapping.
FUNL.NEB (new)
The new FUNL.NEB parameter enables you to change the default NEBUFF parameter for all subsequent Fast/Unload SOUL Interface (FUSI) requests. The default value of FUNL.NEB is 0, meaning that the original NEBUFF default value (40) is used. You can also specify a value greater than 1 to be the new NEBUFF default. FUNL.NEB=1
is not allowed.
FUNMTASK (new)
The new FUNMTASK parameter specifies whether Fast/Unload SOUL Interface (FUSI) requests are to be executed on a z/OS subtask or on one of these: the Model 204 maintask, an MP/204 subtask, or the zIIP support SRB.
FUNPGM (obsolete)
The FUNPGM parameter is now obsolete, because the Fast/Unload CSECTs are all linked with the Online, and the Fast/Unload load module is no longer loaded as a separate load module.
FUNTSKN (new functionality)
As part of support for the Fast/Unload SOUL Interface (FUSI), setting the FUNTSKN parameter now causes implicit definition of IODEV=25 threads, as many as the value of FUNTSKN.
LSERVERG (new)
The new LSERVERG parameter shows the current server size required for the user's tables in the ATB (above the bar) server.
LSERVERN (new)
The new LSERVERN parameter shows the current server size required for the user's tables in the NSA (non-swap area).
MAXOND (new)
The new MAXOND parameter defines the number of times an On unit can be entered before the evaluation is terminated.
NEBUFF (changed default value)
The default value of the NEBUFF parameter for Fast/Unload SOUL Interface (FUSI) requests is now 40. (Prior to 7.6, the default NEBUFF value was 2.) See also FUNL.NEB.
PWDCOLON (new; 7.6 only)
Note: This feature requires zap 76Z291.
PWDCOLON is applicable to version 7.6 only; it will be superseded in 7.7 by additional password functionality.
The PWDCOLON system parameter allows the use of colons in login passwords.
When PWDCOLON=1
is set in CCAIN, users can enter colons in login passwords. Recognizing colons in these passwords also means that users cannot change their passwords with the existing oldpassword:newpassword construction. When PWDCOLON is on, passwords can only be changed in one of the following ways:
- using the LOGCTL C command (system manager privileges required)
- using the $Sir_Login function call (in Janus Web Server and Janus Sockets applications)
RCVOPT (new setting: X'20')
The X'20' bit of the RCVOPT parameter prevents the flushing of dirty pages for a file that does not do pre-imaging (FRCVOPT X'20' set) during a subtransaction checkpoint.
SERVACTG (new)
The SERVACTG parameter shows the swappable size, in bytes, of the ATB server area being used by the current user.
SERVACTV (new)
The SERVACTV parameter shows the swappable size, in bytes, of the BTB server area being used by the current user.
SERVGA (new settings)
The SERVGA parameter now has settings to allocate additional server tables in the ATB swappable-server area.
SERVNSA (new settings)
The SERVNSA parameter now has settings to allocate additional server tables in the ATB non-swappable-server area.
SERVSIZE (new default/minimum value)
The minimum value for SERVSIZE is changed from zero to 65536. If SERVSIZE 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 SERVSIZE was not set but was calculated by the system to a value less than 64K, the following message is issued:
M204.0163: SERVSIZE increased to 65536
This change was introduced as zap maintenance in version 7.4, 7.5, and 7.6 of Model 204.
SYSOPT2 (new setting)
The SYSOPT2 parameter now has a setting to enable zHPF usage.
VTLAPSY (newly documented)
The VTLAPSY parameter, previously undocumented, indicates the name of an APSY subsystem used to provide full-screen login support for IODEV=7 terminals (3270-type).
Notes for system manager and installer
Fast/Unload and FUNPGM
In version 7.6 (of Model 204 and of Fast/Unload), the Fast/Unload CSECTs are all linked with the Online. This changes the implementation of the Fast/Unload SOUL Interface (FUSI), and it was made primarily to enable the use of zIIPs with the FUSI. The main implication of this change is that the FUNPGM parameter is now obsolete, because Fast/Unload is not loaded as a separate load module.
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.
Documentation conversion to wiki format
Rocket Model 204 documentation is being converted from individual manuals in PDF format to a set of cross-linked HTML articles in this integrated wiki, M204wiki.
As of Model 204 version 7.6, most manuals are now in wiki format. The rest remain in PDF format, available in the Rocket M204
folder of the Rocket Software Documentation Library.
For details, see Model 204 documentation.
New and updated messages
See New and updated messages in Model 204 version 7.6 for details.