Release notes for Model 204 version 7.6: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(205 intermediate revisions by 4 users not shown)
Line 1: Line 1:
These release notes list the enhancements and other changes contained in Model 204 version 7.6.
These release notes describe new features, enhancements, and other changes contained in Model 204 version 7.6, generally available in January, 2016.
 
<p style="color:red"><b>******THIS IS A DRAFT DOCUMENT.******</b></p>


==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&nbsp;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.
   
   
==New in this release==
==New in this release==
This section summarizes the new features and enhancements for Model 204 version 7.6.
This section summarizes the highlights of Model 204 version 7.6. For a full list of features, refer to the Table of Contents.
<table>
<table>
<tr class="head"><th>Category</th>
<tr class="head"><th>Category</th>
Line 16: Line 14:
<td>
<td>
<ul>
<ul>
<li>[[#New SOUL statements|Private]] keyword for class declarations; Friend declarations for Class blocks</li>
<li><var>[[#New and changed SOUL statements|Private]]</var> keyword for <var>Class</var> declarations; <var>Friend</var> declarations for <var>Class</var> blocks</li>
<li>[[#Json class|Json class]] for exchanging data with other platforms using the JSON format</li>
<li>[[#Json class|Json class]] for exchanging data with other platforms using the JSON format</li>
<li>[[#Web class|Web class]] as a container for Janus Web Server specific methods</li>
<li>[[#Utf8ToUnicode and Utf16ToUnicode string methods|Utf8ToUnicode and Utf16ToUnicode string methods]] can now handle values that cannot be translated into EBCDIC</li>
<li>[[#Utf8ToUnicode and Utf16ToUnicode string methods|Utf8ToUnicode and Utf16ToUnicode string methods]] can now handle values that cannot be translated into EBCDIC</li>
<li>New [[#"SSL" string methods|"SSL" string methods]] have been added</li>
</ul>
</ul>
</td>
</td>
Line 29: Line 27:
<ul>
<ul>
<li>[[#Massive zIIP offload|Improvements to the zIIP offload]] ensure that almost all Model 204 MP-capable code is offloaded to zIIP</li>
<li>[[#Massive zIIP offload|Improvements to the zIIP offload]] ensure that almost all Model 204 MP-capable code is offloaded to zIIP</li>
<li>Improved zIIP processing for [[#User-written $functions and zIIPs|user-written $functions]]</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>New [[#Journal and checkpoint processing enhancements|journal and checkpoint write PSTs]] (pseudo subtasks)</li>
<li>Support for IBM [[#High Performance FICON (zHPF)|zHPF]] (High Performance FICON) I/O interface</li>
<li>[[#64-bit addressing and Above The Bar (ATB) storage|STBL and VTBL]] can now be placed above the (2G) bar</li>  
<!-- removed; not finished <li>New [[#Journal and checkpoint processing enhancements|journal and checkpoint write PSTs]] (pseudo subtasks)</li> -->
<li>[[#Support for OI CHUNK fields in field groups|CHUNK attribute]] for DEFINE FIELD can now be specified for fields in a field group</li>
<li>support for IBM [[#High Performance FICON (zHPF)|zHPF]] (High Performance FICON) I/O interface</li>
</ul>
</ul>
</td>
</td>
Line 39: Line 35:


<tr>
<tr>
<td>former-Sirius product enhancements</td>
<td>Fast/Unload</td>
<td>
<td>
<ul>
<ul>
<li>[[#SCREENTHROW setting for Janus Web Legacy|New SCREENTHROW setting]] for Janus Web ports to improve error handling for Janus Web Legacy applications</li>
<li><b>[[#Fast/Unload HPO|Fast/Unload HPO]]</b> (High Performance Option) is a new Model 204 V7.6 add-on feature that activates zIIP processing for Fast/Unload.</li>
<li>Janus Web support for HTTP 1.1 [[#Chunked encoding support|chunked encoding]]</li>
<li><b>[[Fast/Unload SOUL Interface]]</b> (<b>FUSI</b>) is the new name for the product formerly known as the Fast/Unload User Language Interface.  The FUSI is purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program.</li>
<li>IPV6 support for Janus TCP/IP Base</li>
<li>Fast/Unload is no longer loaded as a separate load module. See [[#Notes for system manager and installer|Notes for system manager and installer]].</li>  
<li>[[#Changes to Fast/Unload and Fast/Reload|Fast/Unload and Fast/Reload]] can now use 64-bit addressing and Above The Bar (ATB) storage.</li>
<li>RockZap can now run under IBM z/VSE.</li>  
</ul>
</ul>
</td>
</td>
</tr>
</tr>


<tr>
<tr><td>Janus products</td>
<td>
<td><ul><li>[[#SCREENTHROW setting for Janus Web Legacy|New SCREENTHROW setting]] for Janus Web ports to improve error handling for Janus Web Legacy applications</li>
System management</td>
<li>Janus Web Server support for HTTP 1.1 [[#Chunked encoding support|chunked encoding]]</li>
<td>
<li><var>[[#Web class|Web]]</var> class as a container for Janus Web Server specific methods</li>
<ul>
<li>IPV6 support for Janus TCP/IP Base</li></ul></td>
<li>Logout and since-last SMF records now [[#Model 204 version number added to SMF records|show the Model 204 version number]]</li>
</ul>
</td>
</tr>
</tr>


Line 66: Line 57:
<td>
<td>
<ul>
<ul>
<li>[[#Unicode linefeed now causes line break on print|Unicode linefeed]] now causes a line break on print</li>
<li>The "Sirius Debugger" product name is changed to "TN3270 Debugger."  A synonym, <var>TN3270 DEBUG</var>, is now available for the <var>SIRIUS DEBUG</var> command and all its subcommands.</li>
</ul>
</ul>
</td>
</td>
Line 74: Line 65:
==Operating system and hardware requirements==
==Operating system and hardware requirements==
===Operating system requirements===
===Operating system requirements===
<p style="color:red">Requirements for Model 204 version 7.6 are still being determined.</p>
   
   
<ul>
<ul>
<li><b>IBM z/OS</b>  
<li><b>IBM z/OS</b>  
   <ul>
   <ul>
   <li>Versions supported: z/OS version 1.07 through [[Model 204 technical specifications#z/OS 2.1 compatibility issues|2.1]].</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 />
  <p>Version 1.07 is sufficient for all functionality except for the following features:</p>
(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 96:


=== Hardware requirements ===
=== Hardware requirements ===
<p style="color:red">Requirements for Model 204 version 7.6 are still being determined.</p>
Model 204 version 7.6 requires the IBM z/890 or above processor, except for the following feature:
<p>
The large (1 MB) page support feature requires the IBM z10 or above processor. </p>
   
   
In general, Model 204 version 7.6 requires the IBM z/890 or above processor.
<p>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></p>
===Model 204 compatibility with operating systems===
===Model 204 compatibility with operating systems===
<p style="color:red">Content for version 7.6 is still being determined.</p>
 
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]].
http://www.rocketsoftware.com/products/rocket-model-204/technical-information
   
   
<div id="Connect* compatibility with Model 204"></div>
<div id="Connect* compatibility with Model 204"></div>
===Connect* compatibility with Model 204===
Connect<span class="superstar">&#9733;</span> version 7.6 is compatible with all versions of Model 204.
For more information on Connect<sup>&#9733;</sup> installation, see the <var class="book">[[Media:M204_ConnectStarInstallProgram_V75.pdf|Connect* Suite Installation and Programming Guide]]</var>.


See also [[#Connect* enhancements|Connect<span class="superstar">&#9733;</span> enhancements]].
===Connect<sup>&#9733;</sup> compatibility with Model 204===
 
Connect<span class="superstar">&#9733;</span> version 7.5 or 7.7 is compatible with Model 204 version 7.6.
 
For more information on Connect<span class="superstar">&#9733;</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">&#9733;</span> wiki pages]].


==SOUL enhancements==
==SOUL enhancements==


===New SOUL statements===
===New and changed SOUL statements===
<ul>
The <var>[[Classes and Objects#Class block syntax|Private]]</var> keyword has been added to <var>Class</var> declarations, and [[Classes and Objects#Friend declarations|Friend declarations]] have been added to <var>Class</var> blocks.
<li>The [[Classes and Objects#Class block syntax|Private]] keyword has been added to class declarations and [[Classes and Objects#Friend declarations|Friend declarations]] have been added to Class blocks.</li>
 
</ul>
Members of a private class can be accessed only by the class itself or any class declared as a friend of the private class.
===Non-OO enhancements in SOUL===


===New and changed classes and methods===
===New and changed classes and methods===
The LabeledArrayList (or TaggedArrayList) class is to be added.


====Json class====
====Json class====
The [[Json class]] has been created to facilitate exchange of data with other platforms using the [http://en.wikipedia.org/wiki/JSON JSON format]. This class contains a large number of methods and also adds three new exception classes: [[InvalidJsonType class|InvalidJsonType]], [[JsonCircularReference class|JsonCircularReference]], and [[JsonParseError class|JsonParseError]], and one new enumeration: [[Json class#The JsonType enumeration|JsonType]]. In addition, the [[JsonParse (Unicode function)|JsonParse]] function was added to the Unicode intrinsic class.
The <var>[[Json class|Json]]</var> class has been created to facilitate exchange of data with other platforms using the [http://en.wikipedia.org/wiki/JSON JSON format]. This class contains a large number of methods and also adds three new exception classes: <var>[[InvalidJsonType class|InvalidJsonType]]</var>, <var>[[JsonCircularReference class|JsonCircularReference]]</var>, and <var>[[JsonParseError class|JsonParseError]]</var>, and one new enumeration: <var>[[Json class#JsonType enumeration|JsonType]]</var>. In addition, the <var>[[JsonParse (Unicode function)|JsonParse]]</var> function was added to the <var>Unicode</var> intrinsic class.


====Web 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 (Web property)|ScreenInputCallback]] and [[ScreenOutputCallback (Web property)|ScreenOutputCallback]]. There is also an associated new system type: [[WebScreenCallback type|WebScreenCallback]] and a new [[WebScreenException class|WebScreenException]] exception class.
The <var>[[Web class|Web]]</var> class has been created as a container for [[Janus Web Server]] specific methods. This class contains two new methods: <var>[[ScreenInputCallback (Web property)|ScreenInputCallback]]</var> and <var>[[ScreenOutputCallback (Web property)|ScreenOutputCallback]]</var>. There is also an associated new system type: <var>[[WebScreenCallback type|WebScreenCallback]]</var> and a new <var>[[WebScreenException class|WebScreenException]]</var> exception class.
 
===="SSL" String methods====
These new methods are added:
<table>
<tr class="head"><th>Method</th><th>Description</th></tr>
 
<tr><td>[[AES128CBCdecrypt (String function)|AES128CBCdecrypt]]</td><td>AES 128-bit key decryption</td></tr>
 
<tr><td>[[AES128CBCencrypt (String function)|AES128CBCencrypt]]</td><td>AES 128-bit key decryption</td></tr>
 
<tr><td>[[AES128decrypt (String function)|AES128decrypt]]</td><td>AES 128-bit key decryption</td></tr>
 
<tr><td>[[AES128encrypt (String function)|AES128encrypt]]</td><td>AES 128-bit key decryption</td></tr>
 
<tr><td>[[AES192CBCdecrypt (String function)|AES192CBCdecrypt]]</td><td>AES 192-bit key CBC decryption</td></tr>
 
<tr><td>[[AES192CBCencrypt (String function)|AES192CBCencrypt]]</td><td>AES 192-bit key CBC decryption</td></tr>
 
<tr><td>[[AES192decrypt (String function)|AES192decrypt]]</td><td>AES 192-bit key decryption</td></tr>
 
<tr><td>[[AES192encrypt (String function)|AES192encrypt]]</td><td>AES 192-bit key decryption</td></tr>
 
<tr><td>[[AES256CBCdecrypt (String function)|AES256CBCdecrypt]]</td><td>AES 256-bit key CBC decryption</td></tr>
 
<tr><td>[[AES256CBCencrypt (String function)|AES256CBCencrypt]]</td><td>AES 256-bit key CBC decryption</td></tr>
 
<tr><td>[[AES256decrypt (String function)|AES256decrypt]]</td><td>AES 256-bit key decryption</td></tr>
 
<tr><td>[[AES256encrypt (String function)|AES256encrypt]]</td><td>AES 256-bit key decryption</td></tr>
 
<tr><td>[[DEA128CBCdecrypt (String function)|DEA128CBCdecrypt]]</td><td>DEA 128-bit key decryption</td></tr>
 
<tr><td>[[DEA128CBCencrypt (String function)|DEA128CBCencrypt]]</td><td>DEA 128-bit key decryption</td></tr>
 
<tr><td>[[DEA128decrypt (String function)|DEA128decrypt]]</td><td>DEA 128-bit key decryption</td></tr>
 
<tr><td>[[DEA128encrypt (String function)|DEA128encrypt]]</td><td>DEA 128-bit key decryption</td></tr>
 
<tr><td>[[DEA192CBCdecrypt (String function)|DEA192CBCdecrypt]]</td><td>DEA 192-bit key CBC decryption</td></tr>
 
<tr><td>[[DEA192CBCencrypt (String function)|DEA192CBCencrypt]]</td><td>DEA 192-bit key CBC decryption</td></tr>
 
<tr><td>[[DEA192decrypt (String function)|DEA192decrypt]]</td><td>DEA 192-bit key decryption</td></tr>
 
<tr><td>[[DEA192encrypt (String function)|DEA192encrypt]]</td><td>DEA 192-bit key decryption</td></tr>
 
<tr><td>[[DEA64CBCdecrypt (String function)|DEA64CBCdecrypt]]</td><td>DEA 64-bit key CBC decryption</td></tr>
 
<tr><td>[[DEA64CBCencrypt (String function)|DEA64CBCencrypt]]</td><td>DEA 64-bit key CBC decryption</td></tr>
 
<tr><td>[[DEA64decrypt (String function)|DEA64decrypt]]</td><td>DEA 64-bit key decryption</td></tr>
 
<tr><td>[[DEA64encrypt (String function)|DEA64encrypt]]</td><td>DEA 64-bit key decryption</td></tr>
 
<tr><td>[[SHA224digest (String function)|SHA224digest]]</td><td>224-bit SHA-2 digest</td></tr>
 
<tr><td>[[SHA256digest (String function)|SHA256digest]]</td><td>256-bit SHA-2 digest</td></tr>
</table>
 
====Utf8ToUnicode and Utf16ToUnicode string methods====
====Utf8ToUnicode and Utf16ToUnicode string methods====
The [[Utf8ToUnicode (String function)|Utf8ToUnicode]] and [[Utf16ToUnicode (String function)|Utf16ToUnicode]] string 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 and changed $functions===
===New XHTML entities for square-bracket characters===
By applying zap <code>76Z260</code>, <b>&lsqb;</b> and <b>&rsqb;</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.


==Sirius products and product enhancements==
For example, to produce an XPath expression equivalent to the following:
This section describes enhancements to [[Sirius Software product list|the former-Sirius products]].
<p class="code"><nowiki>*/pers[@name="Hector"] </nowiki></p>
Code like this was recommended under version 7.5 of Model&nbsp;204:
===Changes to Janus Web Server===
<p class="code">%lsq is string len 1 static initial('&amp;#x5B;'):u
%rsq is string len 1 static initial('&amp;#x5D;'):u
  . . .  
%myXmldoc:print('*/pers' %lsq '@name="Hector"' %rsq) </p>


====Chunked encoding support====
Under version 7.6, you can instead use the new entities and avoid the declarations, concatenations, and runtime conversions required above:
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.
<p class="code">%myXmldoc:print('*/pers<b>&lsqb;</b>@name="Hector"<b>&rsqb;</b>':u)</p>


For more information about chunked encoding, see http://en.wikipedia.org/wiki/Chunked_transfer_encoding.
===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.


====SCREENTHROW setting for Janus Web Legacy====
This change is initially provided by zap maintenance.
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.


====IPV6 support====
==Janus Web Server enhancements==
IPV6 support for Janus TCP/IP Base is to be added <i>if time permits</i>.


===Changes to Fast/Unload and Fast/Reload===
===Chunked encoding support===
The Fast/Unload and Fast/Reload products are to be equipped with 64-bit addressing and Above The Bar (ATB) storage.
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.  


In addition, <b>Fast/Unload HPO</b> (High Performance Option) is a new Model 204 V7.6 add-on feature that activates zIIP processing for Fast/Unload.
For more information about chunked encoding, see http://en.wikipedia.org/wiki/Chunked_transfer_encoding.


===RockZap for VSE===
===SCREENTHROW setting for Janus Web Legacy===
Support is being added for running RockZap under z/VSE.
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.


===Changes to Janus/TN3270 Debugger===
===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).


====Product name change for Sirius Debugger====
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 "Sirius Debugger" [[Debugger|product]] name is changed to "TN3270 Debugger."
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>


====Synonym for SIRIUS DEBUG command====
==Fast/Unload enhancements==
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.


==File-related enhancements==
===Fast/Unload HPO===
[[Fast/Unload overview#fuhpo|Fast/Unload HPO]] (High Performance Option) is a Model&nbsp;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 [[#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>


===New field attributes===
===FUSI: new product name for SOUL access to Fast/Unload===
<p>
The [[Fast/Unload SOUL Interface]] (FUSI), purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program.
This section lists the new field attributes. For more information on how related attributes work together, see the [[Field design]] topic.</p>
<!-- Further information TBD, including IODEV 25 threads, etc. -->
TBD
 
===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|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 SMF records (logout and since-last) at offset X'39'. For V760, the value is X'4C' = 76 decimal.
A one-byte, hexadecimal representation of the Model&nbsp;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==
   
   
===Massive zIIP offload===
===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&nbsp;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 fully improved zIIP support requires an additional license. For more information, [[Contacting Rocket Software Technical Support|contact Rocket Software]].</p>
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 previously, specifying a nonzero value for the <var>[[NMPSUBZ parameter|NMPSUBZ]]</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>  


====User-written $functions and zIIPs====
====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 may not run on zIIP. Customers planning to use zIIP processing must do either of these:  
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:  
<ul>
<ul>
<li>Inspect any [[Customizing functions and translation tables#Converting user-written functions|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 <code>SRBMODE OFF</code> and <code>SRBMODE ON</code>. </li>
<li>Inspect any [[Customizing functions and translation tables#Converting user-written functions|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 <code>SRBMODE OFF</code> and <code>SRBMODE ON</code>. </li>
Line 207: Line 271:
</ul>
</ul>
<p>
<p>
It is not always obvious if code may or may not run on a zIIP subtask. Even if all explicit SVCs and non-task-mode system macros issued by Model&nbsp;204 have been identified and bracketed, some may be issued implicitly by z/OS or other services, so user testing is important. </p>
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&nbsp;204 have been identified and bracketed, some may be issued implicitly by z/OS or other services, so user testing is important. </p>


====Parameter changes for zIIP usage====
====Parameter changes for zIIP usage====
The following are V7.6 changes to the [[Performance_monitoring_and_tuning#Model 204 parameters for zIIP support|documented recommendations]] for the parameters that initiate and control Model&nbsp;204 zIIP processing:
The following are V7.6 changes to the [[Performance_monitoring_and_tuning#Model 204 parameters for zIIP support|documented recommendations]] for the parameters that initiate and control Model&nbsp;204 zIIP processing:
<ul>
<ul>
<li>Parameter <var>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' becomes the default value of the <var>[[SIRFUNC parameter|SIRFUNC]]</var> parameter.
<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>
<p>
The X'01' bit of <var>SIRFUNC</var> must be set (explicitly or as the default value) for zIIP processing or the run is cancelled.</p></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 not set the X'40' bit of the <var>[[SCHDOPT parameter|SCHDOPT]]</var> parameter as MP subtasks will no longer steal work from zIIP SRBs unless they seem overloaded, in which case one would probably not want the <var>SCHDOPT</var> X'40' bit to prevent MP subtasks from helping out.</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, 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>


===High Performance FICON (zHPF)===
====Fast/Unload HPO====
Model 204 version 7.6 [[Performance monitoring and tuning#High Performance FICON (zHPF)|supports IBM's High Performance FICON (zHPF)]] feature, which allows faster I/O by limiting number of interactions between the channel and the device.
[[#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).
 
Required hardware and software:
<ul>
<li>CPU: z10 and higher </li>
<li>z/OS version: 2.01
<li>Disk subsystem: Contact your IT department to verify that your disk subsystem has the zHPF feature available and activated.</li>
<li><p>zHPF is not supported on z/CMS, z/VSE, or z/OS running under z/VM.</p></li></ul>
 
The new [[#ZHPF command|ZHPF command]] displays zHPF capabilities for each dataset for a currently opened file.
 
===Journal and checkpoint processing enhancements===
<p>
New journal and checkpoint write PSTs (pseudo subtasks) are invoked by the <var>SYSOPT2</var> parameter. </p>
<p>
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&nbsp;204. </p>
<p>
The <var>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.</p>
<!-- 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. -->


===64-bit addressing and Above The Bar (ATB) storage===
===64-bit addressing and Above The Bar (ATB) storage===
Line 251: Line 294:
<li>ATB support for FTBL was released with Model 204 version 7.4.</li>
<li>ATB support for FTBL was released with Model 204 version 7.4.</li>
<li>ATB support for GTBL, NTBL, and QTBL was released with Model 204 version 7.5.</li>
<li>ATB support for GTBL, NTBL, and QTBL was released with Model 204 version 7.5.</li>
<li>ATB support for STBL and VTBL is added in Model 204 version 7.6.</li>
<li>ATB support for STBL, VTBL, and several other tables is added in Model 204 version 7.6.</li>
</ul>  
</ul>  
   
   
Line 258: Line 301:
As more features use ATB buffers, it is a good idea to reevaluate your ATB and BTB buffer usage.
As more features use ATB buffers, it is a good idea to reevaluate your ATB and BTB buffer usage.
   
   
====STBL and VTBL in above the bar storage====
====STBL, VTBL, and other tables in ATB storage====
STBL and VTBL can now be placed into swappable or non-swappable server storage area above the bar.
STBL, VTBL, and several other tables can now be placed into swappable or non-swappable server storage area above the bar.
<p>In order to store a table in ATB storage:</p>
<p>To store a table in non-swappable ATB storage:</p>
<p style="color:red">TBD: any changes to SERVNSSZ or SERVNSA for 7.6</p>
<ul>
<ul>
<li>Increase the <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameter by the corresponding table size.
<li>Increase the <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameter by the corresponding table size.
<li>Set the proper bit in <var>[[SERVNSA parameter|SERVNSA]]</var>:
<li>Set the proper bit in <var>[[SERVNSA parameter|SERVNSA]]</var>.
</ul>
<p>To store a table in swappable ATB storage:</p>
<ul>
<ul>
<li>for STBL set the xxx byte to <code>X'xx'</code>, so the value of <var>SERVNSA</var> is <code>X'........'</code></li>
<li>Increase the <var>[[SERVGSZ parameter|SERVGSZ]]</var> parameter by the corresponding table size.
<li>for VTBL set the xxx byte to <code>X'xx'</code>, so the value of <var>SERVNSA</var> is <code>X'........'</code></li>
<li>Set the proper bit in <var>[[SERVGA parameter|SERVGA]]</var>.
</ul>
</ul>
<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 <var>SERVNSA</var> and <var>SERVGA</var>.</p>
====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:
<ul>
<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 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>
<p class="note">'''Note:'''
The settings for each server table above the bar are independent of each other.
So if FTBL, GTBL, NTBL, QTBL, STBL, and VTBL are all placed above the bar, then <var>SERVNSA</var> should be set to <code>X'........'</code>.</p>


===Support for OI CHUNK fields in field groups===
===High Performance FICON (zHPF)===
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 now be specified for fields in a field group.
Model 204 version 7.6 [[Performance monitoring and tuning#High Performance FICON (zHPF)|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:
<ul>
<li>CPU: z10 and higher </li>
<li>z/OS version: 2.01
<li>Disk subsystem: Contact your IT department to verify that your disk subsystem has the zHPF feature available and activated.</li>
<li><p>zHPF is not supported on z/CMS, z/VSE, or z/OS running under z/VM.</p></li></ul>
 
The new <var>[[#ZHPF (new)|ZHPF]]</var> command displays zHPF capabilities for each data set in a currently opened file.


===64-bit addressing support for TBO buffers, the Procedure dictionary, and Longstrings===
<!-- removed; not finished;  Journal and checkpoint processing enhancements
This support will be new in version 7.6.
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&nbsp;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.
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.
-->
===Support for OI CHUNK field group members===
The [[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK attribute]] for <var>DEFINE FIELD</var> was introduced in Model&nbsp;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====
Printing or auditing a unicode string that contains a unicode linefeed character (u+000a) will now cause a new line to be started on the output device, rather than displaying <code>&#x000A;</code>. This should make it much easier to look at unicode strings that contain formatting linefeeds. This feature works for any display-oriented statements such as Print, Audit, Trace, PrintText, AuditText, TraceText, Text, etc.


====SoftSpy====
===Unicode linefeed now causes line break on print===
As of version 7.5, the SoftSpy debugging, testing, and performance tuning product has been included as part of the Model 204 core product.  
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>&amp;#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>


For more information about SoftSpy version 7.6, see the [http://m204stage.rocketsoftware.com/index.php/Release_notes_for_SoftSpy_V7.6 SoftSpy 7.6 release notes].
===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.  


<div id="Connect* enhancements"></div>
For more information about SoftSpy version 7.6, see the [[Release notes for SoftSpy V7.6|SoftSpy 7.6 release notes]].
==Connect<sup>&#9733;</sup> enhancements==
The 7.6 version of Connect<sup>&#9733;</sup> for JDBC, Connect<sup>&#9733;</sup> for .NET, and Connect<sup>&#9733;</sup> for ODBC is now available. <br />
For more information on Connect<sup>&#9733;</sup> installation, see the <var class="book">[[Media:M204_ConnectStarInstallProgram_V75.pdf|Connect* Suite Installation and Programming Guide]]</var>.


Each Connect<sup>&#9733;</sup> interface contains the latest fixes and enhancements and is compatible with Model 204 version 7.6.
===Janus/TN3270 Debugger===
<ul>
<li>Product name change.
<p>
The "Sirius Debugger" [[Debugger|product]] name is changed to "TN3270 Debugger."</p></li>
 
<li>Synonym for <var>SIRIUS DEBUG</var> 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>
</ul>


==Compatibility issues==
==Compatibility issues==
====Unicode linefeed now causes line break on print====
Printing or auditing a unicode string that contains a unicode linefeed character (u+000a) will now cause a new line to be started on the output device, rather than displaying <code>&#x000A;</code>. This should make it much easier to look at unicode strings that contain formatting linefeeds. This feature works for any display-oriented statements such as Print, Audit, Trace, PrintText, AuditText, TraceText, Text, etc..


While this feature is likely to make it much easier to examine unicode strings, in theory it could cause a backward-compatbility problem for applications that parse the results of a Print of unicode data, expecting the <code>&x#000A;</code> values to be present.
===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>&amp;#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&nbsp;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&nbsp;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:
<ul>
<li>M204XSVC version 7.4</li>
<li>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.)</li>
</ul> 
<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.
 
===APSYPAGE parameter is obsolete===
<p>(applies to z/OS)</p>
The <var>APSYPAGE</var> parameter has been disabled as of version 7.6. If <var>APSYPAGE</var> is non-zero, a warning will appear:
<p class="code">M204.2958: APSYPAGE obsolete as of 7.6</p>
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===
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 <var>FDV</var>. Such statements are no longer allowed. For example, the following was allowed in older versions of Model 204:
<p class="code">a: audit 'About to FDV'
  fdv foo
b: frv in a</p>
Inserting SOUL code between a label and an <var>FDV</var> statement
is no longer allowed, and so the result of the above is:
 
<p class="code">M204.0311 Unacceptable statement reference</p>
 
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 309: 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 will cause any disabled parallel GDG members to be reopened during the switch. RESET is valid only for a CCAJLOG stream specified as a Parallel GDG.
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)===
<var>TN3270 DEBUG</var> is now available as a synonym for the <var>[[SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command|SIRIUS DEBUG]]</var> command and all its subcommands.


===ZHPF (new)===
===ZHPF (new)===
The ZHPF command displays [[#High Performance FICON (zHPF)|zHPF capabilities]] for each data set for a currently opened file. It also indicates (by displaying <code>Supported: YES</code>) if zHPF-type I/O, called "transport mode I/O," can be used for the data set. <code>Supported: NO</code> means that hardware or z/OS support for zHPF functionality is insufficient (for example when z/OS runs under VM), and <code>Supported: N/A</code> means that zHPF support is not available at all on z/OS or on the hardware level.
The <var>[[ZHPF command|ZHPF]]</var> command displays [[#High Performance FICON (zHPF)|zHPF capabilities]] for each data set for a currently opened file.  
<table>
<tr class="head">
<th>Displayed value</th>
<th>Meaning</th>
</tr>
<tr>
<td nowrap><code>Supported: YES</code></td>
<td>zHPF-type I/O (called "transport mode I/O") can be used for the data set.</td>
</tr>
<tr>
<td><code>Supported: NO</code></td> <td>Hardware or z/OS support for zHPF functionality is insufficient (for example, when z/OS runs under VM).</td></tr>
<tr>
<td><code>Supported: N/A</code></td> <td>zHPF support is not available at all on z/OS or on the hardware level.</td>
</tr>
</table>
<!--
<!--
     *************************************************************************************
     *************************************************************************************
Line 319: Line 456:
-->
-->


==Reliability enhancements==
TBD
==New and changed parameters==
==New and changed parameters==
<!--
<!--
Line 333: Line 467:
===DSPOPT (new setting: X'04')===
===DSPOPT (new setting: X'04')===
The new X'04' setting for the <var>[[DSPOPT parameter|DSPOPT]]</var> parameter uses compression for 64-bit in-storage server swapping.
The new X'04' setting for the <var>[[DSPOPT parameter|DSPOPT]]</var> parameter uses compression for 64-bit in-storage server swapping.
===FUNL.NEB (new)===
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)===
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)===
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)===
The new <var>[[LSERVERG parameter|LSERVERG]]</var> parameter shows the current server size required for the user's tables in the ATB (above the bar) server.
===LSERVERN (new)===
The new <var>[[LSERVERN parameter|LSERVERN]]</var> parameter shows the current server size required for the user's tables in the NSA (non-swap area).


===MAXOND (new)===
===MAXOND (new)===
The new <var>[[MAXOND parameter|MAXOND]]</var> parameter defines the number of times an ON unit can be entered before the evaluation is terminated.
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)===
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')===
The X'20' bit of the <var>[[RCVOPT parameter|RCVOPT]]</var> parameter prevents the flushing of dirty pages for a file that does not do pre-imaging (<var>[[FRCVOPT parameter|FRCVOPT]]</var> X'20' set) during a subtransaction checkpoint.
The X'20' bit of the <var>[[RCVOPT parameter|RCVOPT]]</var> parameter prevents the flushing of dirty pages for a file that does not do pre-imaging (<var>[[FRCVOPT parameter|FRCVOPT]]</var> X'20' set) during a subtransaction checkpoint.
===SERVACTG (new)===
The <var>[[SERVACTG parameter|SERVACTG]]</var> parameter shows the swappable size, in bytes, of the ATB server area being used by the current user.
===SERVACTV (new)===
The <var>[[SERVACTV parameter|SERVACTV]]</var> parameter shows the swappable size, in bytes, of the BTB server area being used by the current user.
===SERVGA (new settings)===
The <var>[[SERVGA parameter|SERVGA]]</var> parameter now has settings to allocate additional server tables in the ATB swappable-server area.
===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.
===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&nbsp;204.
</p>
===SYSOPT2 (new setting)===
The <var>[[SYSOPT2 parameter|SYSOPT2]]</var> parameter now has a setting to enable zHPF usage.
===VTLAPSY (newly documented)===
The <var>[[VTLAPSY parameter|VTLAPSY]]</var> parameter, previously undocumented, indicates the name of an APSY subsystem used to provide full-screen login support for IODEV=7 terminals (3270-type).
<!-- ***************************************************************************************** -->
<!-- ***************************************************************************************** -->
<!-- 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==
===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|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==
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.
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 release 7.6, most manuals are now in wiki format. The rest remain in PDF format, available in the M204 folder of the [http://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm  Rocket Software Documentation Library].
As of Model 204 version 7.6, most manuals are now in wiki format. The rest remain in PDF format, available in the <code>Rocket M204</code> folder of the [http://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm  Rocket Software Documentation Library].
   
   
For details, see [[Model 204 documentation]].
For details, see [[Model 204 documentation]].
Line 352: Line 556:
==New and updated messages==
==New and updated messages==
   
   
See [[New and updated messages in Model 204 version 7.6 -- DRAFT|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
  • Fast/Unload HPO (High Performance Option) is a new Model 204 V7.6 add-on feature that activates zIIP processing for Fast/Unload.
  • Fast/Unload SOUL Interface (FUSI) is the new name for the product formerly known as the Fast/Unload User Language Interface. The FUSI is purchased as a separate Fast/Unload option, allows you to invoke Fast/Unload from a SOUL program.
  • Fast/Unload is no longer loaded as a separate load module. See Notes for system manager and installer.
Janus products
  • New SCREENTHROW setting for Janus Web ports to improve error handling for Janus Web Legacy applications
  • Janus Web Server support for HTTP 1.1 chunked encoding
  • Web class as a container for Janus Web Server specific methods
  • IPV6 support for Janus TCP/IP Base
Debugging and testing
  • The "Sirius Debugger" product name is changed to "TN3270 Debugger." A synonym, TN3270 DEBUG, is now available for the SIRIUS DEBUG command and all its subcommands.

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.)
    • Version 1.07 is sufficient for all functionality except for the following features:

      • zHPF support requires version 2.1.
      • Large (1 MB) page support requires version 1.9.
      • Extended address volumes (EAV) requires version 1.12.

    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.

  • 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:

MethodDescription
AES128CBCdecryptAES 128-bit key decryption
AES128CBCencryptAES 128-bit key decryption
AES128decryptAES 128-bit key decryption
AES128encryptAES 128-bit key decryption
AES192CBCdecryptAES 192-bit key CBC decryption
AES192CBCencryptAES 192-bit key CBC decryption
AES192decryptAES 192-bit key decryption
AES192encryptAES 192-bit key decryption
AES256CBCdecryptAES 256-bit key CBC decryption
AES256CBCencryptAES 256-bit key CBC decryption
AES256decryptAES 256-bit key decryption
AES256encryptAES 256-bit key decryption
DEA128CBCdecryptDEA 128-bit key decryption
DEA128CBCencryptDEA 128-bit key decryption
DEA128decryptDEA 128-bit key decryption
DEA128encryptDEA 128-bit key decryption
DEA192CBCdecryptDEA 192-bit key CBC decryption
DEA192CBCencryptDEA 192-bit key CBC decryption
DEA192decryptDEA 192-bit key decryption
DEA192encryptDEA 192-bit key decryption
DEA64CBCdecryptDEA 64-bit key CBC decryption
DEA64CBCencryptDEA 64-bit key CBC decryption
DEA64decryptDEA 64-bit key decryption
DEA64encryptDEA 64-bit key decryption
SHA224digest224-bit SHA-2 digest
SHA256digest256-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('&#x5B;'):u %rsq is string len 1 static initial('&#x5D;'):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 and SRBMODE 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:

  • Increase the SERVNSSZ parameter by the corresponding table size.
  • Set the proper bit in SERVNSA.

To store a table in swappable ATB storage:

  • Increase the SERVGSZ parameter by the corresponding table size.
  • Set the proper bit in SERVGA.

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 (&#x000A;) 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 &#x000A; 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.