Difference between revisions of "Release notes for Model 204 version 7.9 (Beta)"

From m204wiki
Jump to navigation Jump to search
(Created page with "These release notes list the enhancements and other changes contained in Model 204 version 7.9, <b><i>which is still in development</i></b>. Until the commercial release of th...")
 
Line 1: Line 1:
 +
<b>THIS PAGE IS UNDER CONSTRUCTION!</b>
 
These release notes list the enhancements and other changes contained in Model 204 version 7.9, <b><i>which is still in development</i></b>. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.  
 
These release notes list the enhancements and other changes contained in Model 204 version 7.9, <b><i>which is still in development</i></b>. Until the commercial release of the software, Rocket reserves the right to add to, remove, or change anything described herein.  
  
Line 6: Line 7:
  
 
==New in this release==
 
==New in this release==
−
The table below cites some highlights of Model&nbsp;204 version 7.9. For a full list of features, refer to the Table of Contents.
 
−
<p>See also the [[#Compatibility issues|Compatibility]] section for possible issues.</p>
 
−
<table>
 
−
<tr class="head"><th>Category</th>
 
−
<th>Feature</th></tr>
 
−
<tr>
 
−
<td>SOUL</td>
 
−
<td>
 
−
<ul>
 
−
<li>The new [[#AmIndependent method|AmIndependent]] method returns TRUE for daemons spawned by [[RunIndependently (Daemon subroutine)|RunIndependently]].
 
−
</li>
 
−
<li>The Object class now supports the [[#Support for copying Object class objects|copy and deepCopy methods]].
 
−
</li>
 
−
</ul>
 
−
</td></tr>
 
  
−
<tr>
 
−
<td>Janus Web</td>
 
−
<td>
 
−
<ul>
 
−
<li>[[#Web Sockets|Janus Web Sockets]] are now supported.</li>
 
−
</ul>
 
−
</td></tr>
 
−
 
−
<tr>
 
−
<td nowrap>Networking</td>
 
−
<td>
 
−
<b>Note:</b> The two-phase commit and commit exits features are licensed and purchased separately from Model 204.
 
−
<ul>
 
−
<li>Two-phase commit. A Model 204 online can now be configured to use two-phase commit (2PC). The Janus internal socket API is used for the calls to the coordinator. JANUS commands are used for all 2PC configuration. A new JANUS port type has been added: 2PC.</li>
 
−
<li>[[Application_Subsystem_development#Commit_exits|Commit exits]] are now supported. The commit exit runs within the APSY, which is defined by the <var>[[Application_Subsystem_development#COMMITX parameter|COMMITX]]</var> parameter and uses normal APSY processing.  </li>
 
−
</ul></td></tr>
 
−
 
−
<tr>
 
−
<td>ECF tables</td>
 
−
<td>
 
−
<ul>
 
−
<li>The new <var>[[#DISPLAY ECF|DISPLAY ECF]]</var> command and <var>[[#Managing ECF tables more efficiently|EXTERNAL REMOVE]]</var> statement enable more efficient management of [[#Managing ECF tables more efficiently|ECF tables]].</li>
 
−
</ul>
 
−
</td></tr>
 
−
<tr>
 
−
<td>Performance</td>
 
−
<td>
 
−
<ul>
 
−
<li>[[#MP/204 offload improvements|MP/204 offload improvements]] -- application code for these SOUL statements is now fully offloadable:
 
−
<ul>
 
−
<li><var>File Records In/On</var></li>
 
−
<li><var>Remember</var></li>
 
−
<li><var>Position</var></li>
 
−
<li><var>Sort Values</var></li>
 
−
<li><var>Reset Header/Trailer</var></li>
 
−
<li><var>Find and Print Count</var></li>
 
−
<li><var>Find All Values</var></li>
 
−
<li><var>For Each Value</var></li>
 
−
</ul>
 
−
</li>
 
−
</ul>
 
−
</td></tr>
 
−
 
−
<tr>
 
−
<td>Security</td>
 
−
<td>
 
−
<ul>
 
−
<li>CA-Top Secret can [[#CA-Top Secret can disallow CCASTAT logins|disallow CCASTAT logins]].</li>
 
−
<li>[[#DEFUSER can specify a jobname not authorized to access M204|DEFUSER]] can specify a jobname not authorized to access M204.</li>
 
−
</ul>
 
−
</td></tr>
 
−
 
−
<tr>
 
−
<td nowrap>System enhancements</td>
 
−
<td>
 
−
<ul>
 
−
<li>The <var>[[MONITOR command|MONITOR <var>USERS</var>]]</var> command output displays [[#New wait types for daemon/master waits|two new wait types]].</li>
 
−
</ul></td></tr>
 
−
 
−
 
−
<tr>
 
−
<td nowrap>AUDIT204 enhancements</td>
 
−
<td>
 
−
<ul>
 
−
<li>The new TIMEHH parameter on the <var>[[#FORMAT command|FORMAT]]</var> command of the AUDIT204 utility provides greater time stamp precision.</li>
 
−
</ul></td></tr>
 
−
 
−
<tr>
 
−
<td nowrap>New commands</td>
 
−
<td>
 
−
<ul>
 
−
<li><var>[[#DISPLAY ECF|DISPLAY ECF]]</var> displays details from ECF tables, or the current status of users accessing ECF modules.</li>
 
−
</ul></td></tr>
 
−
 
−
<tr>
 
−
<td nowrap>New parameters</td>
 
−
<td>
 
−
<ul>
 
−
<li><var>[[#ENQTIME|ENQTIME]]</var> specifies the number of milliseconds waited for each record locking retry wait.</li>
 
−
<li><var>[[#EVALOPT|EVALOPT]]</var> controls the cancellation of a request on truncation of string data.</li>
 
−
<li><var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</var> can be used to cancel a runaway transaction and prevent it from filling the checkpoint data set.</li>
 
−
<li><var>[[#NLDAPBUF|NLDAPBUF]]</var> allows the number of LDAP buffers allocated during startup to be set in CCAIN.</li>
 
−
<li><var>[[#SERV4G|SERV4G]]</var> allows testing of server tables that span a 4-gigabyte boundary.</li>
 
−
<li><var>[[#WEBDFLT|WEBDFLT]]</var> changes the default JANUS WEB ALLOW rule back to ALLOW.</li>
 
−
</ul></td></tr>
 
−
 
−
<tr>
 
−
<td nowrap>Janus and TN3270 debuggers</td>
 
−
<td>
 
−
<ul>
 
−
<li>The debuggers can now view or watch the values of [[#Access to exposed variables|variables exposed to local routines/methods]].</li>
 
−
<li>When execution pauses, the debuggers now [[#Subroutine or method display|display the subroutine or method]] being executed.</li>
 
−
</ul></td>
 
−
</tr>
 
−
 
−
<tr>
 
−
<td nowrap>User/system statistics</td>
 
−
<td>
 
−
<ul>
 
−
<li><var>[[#MPR, MBO, MCP, and RCV|MPR, MBO, MCP, and RCV]]</var> provide high water mark transaction information in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</var> parameters.
 
−
</li>
 
−
<li>[[#DKWTS and DKWTMICS|New system statistics]] DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.</li>
 
−
</ul></td></tr>
 
−
</table>
 
  
 
==Operating system and hardware requirements==
 
==Operating system and hardware requirements==
  
 
===Operating system requirements===
 
===Operating system requirements===
−
 
−
<ul>
 
−
<li><b>IBM z/OS versions supported:</b>
 
−
  <ul>
 
−
  <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]].)</li>
 
−
  <p>Version 1.07 is sufficient for all functionality except for the following features:</p>
 
−
    <ul>
 
−
    <li>zHPF support requires version [[IBM z/OS 2.1 compatibility issue|2.1]].</li>
 
−
    <li>Large (1 MB) page support requires version 1.9.</li>
 
−
    <li>Extended address volumes (EAV) requires version 1.12.</li>
 
−
    </ul>
 
−
  </li>
 
−
</ul>
 
−
On z/OS, Model 204 release 7.9 operates as an APF authorized load module, as required by many 7.9 features. <br />
 
−
To run Model 204 unauthorized, [[Contacting Rocket Software Technical Support|contact Technical Support]].
 
−
 
−
<li><b>IBM z/VM versions supported:</b>
 
−
  <ul>
 
−
  <li>All IBM supported releases up to and including z/VM 6.4.</li>
 
−
  </ul>
 
−
</li>
 
−
 
−
<li><b>IBM z/VSE versions supported:</b>
 
−
  <ul>
 
−
  <li>All IBM supported releases up to and including z/VSE 6.1.</li>
 
−
  </ul>
 
−
</li>
 
−
</ul>
 
  
−
===Hardware requirements===
 
−
 
−
In general, Model 204 version 7.9 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>
 
  
−
===Connect<sup>&#9733;</sup> compatibility with Model 204===
+
==System Enhancements==
−
 
 
−
Connect<span class="superstar">&#9733;</span> version 7.5 or 7.7 is compatible with Model 204 version 7.9.
 
−
 
 
−
For more information on Connect<span class="superstar">&#9733;</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">&#9733;</span> wiki pages]].
 
−
 
 
−
==SOUL (User Language) enhancements==
 
−
===AmIndependent method===
 
−
The <var>AmIndependent</var> method returns TRUE for daemons spawned by <var>[[RunIndependently_(Daemon_subroutine)|RunIndependently]]</var>. (The action of <var>[[AmDaemon_(Daemon_property)|AmDaemon]]</var> remains unchanged.)
 
−
 
 
−
The following table shows the values returned by <var>AmIndependent</var> versus <var>AmDaemon</var> for different daemon types:
 
−
<table>
 
−
<th>Type</th>
 
−
<th>AmDaemon</th>
 
−
<th>AmIndependent</th>
 
−
<tr>
 
−
<td>$COMBG</td>
 
−
<td>False</td>
 
−
<td>False</td>
 
−
</tr>
 
−
<tr>
 
−
<td>Independent daemon</td>
 
−
<td>False</td>
 
−
<td>True</td></tr>
 
−
<tr>
 
−
<td>Other daemon</td>
 
−
<td>True</td>
 
−
<td>False</td>
 
−
</tr>
 
−
<tr>
 
−
<td>Web, etc.</td>
 
−
<td>False</td>
 
−
<td>False</td>
 
−
</tr></table>
 
−
 
 
−
===EndsWith function===
 
−
The [[EndsWith (String function)|EndsWith String function]] determines if one string ends with the characters in another. This is analogous to the [[StartsWith and IsStartOf (String functions)|StartsWith function]] except, of course, it checks the end of a string rather than the start.
 
−
 
 
−
The following code snippet:
 
−
<p class="code>printText {~="War and Peace":endsWith("Peace")}
 
−
printText {~="War and Peace":endsWith("War")}
 
−
</p>
 
−
displays:
 
−
<p class="output">"War and Peace":endsWith("Peace")=True
 
−
"War and Peace":endsWith("War")=False
 
−
</p>
 
−
 
 
−
===$ProcOpn===
 
−
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:
 
−
 
 
−
<p class="code">%result = $procOpn('0123', 'MYFILE')</p>
 
−
 
 
−
Support for such procedure names was initially introduced at V7.7, and this feature of <var>$ProcOpn</var> is enabled in V7.7 with the application of zap 77z054.
 
−
 
 
−
===Allow parentheses to surround a boolean enumeration object===
 
−
The following sample code:
 
−
<p class="code">  begin                                     
 
−
  variables are undefined                 
 
−
  %isValid is boolean initial (True)     
 
−
  if (%isValid) then                 
 
−
      print 'in IF'                           
 
−
  end if                                 
 
−
  end  </p>     
 
−
 
 
−
will now compile and run successfully, since this syntax:
 
−
 
 
−
<p class="syntax">if (%isValid) then </p>
 
−
 
 
−
is logically equivalent to this:
 
−
 
 
−
<p class="syntax">if %isValid then </p>
 
−
 
 
−
Prior to V7.8 the presence of parentheses surrounding the boolean enumeration object would have caused a compilation error. This change is enabled in V7.7 with the application of zap 77z370.
 
−
 
 
−
===Support for copying Object class objects===
 
−
The Object class now supports the copy and deepCopy methods. For example, an Object object can be copied as follows:
 
−
<p class="code">  begin             
 
−
  %x is object object
 
−
  %y is object object
 
−
  %y = new           
 
−
  %x = %y:copy       
 
−
  end </p>
 
−
 
 
−
This change is enabled in v7.7 with the application of zap 77z076, and within V7.6 with the application of zap 76z412.
 
−
 
 
−
===Assignment of enumeration values to method variables===
 
−
Enumeration values can now be assigned to method variables whose result is an enumeration. So, for example, the following code:
 
−
<p class="code">  begin                                             
 
−
  enumeration colour                                 
 
−
      public                                         
 
−
        value red                                   
 
−
        value white                                 
 
−
        value blue                                   
 
−
      end public                                     
 
−
  end enumeration                                   
 
−
  %func    is function getColour is enumeration colour
 
−
  local function getColour is enumeration colour     
 
−
      return blue                                     
 
−
  end function                                       
 
−
  %func    = getColour                               
 
−
  %func    = (colour):red                           
 
−
  printText {~=%(Local):(%func)}                     
 
−
  end  </p>
 
−
 
 
−
will produce this result:
 
−
 
 
−
  <p class="syntax"> %(Local):(%func)=red </p>
 
−
 
 
−
whereas previously this line: 
 
−
 
 
−
  <p class="syntax"> %func    = (colour):red </p> 
 
−
 
 
−
would have been rejected with this message:
 
−
 
 
−
  <p class="syntax">MSIR.0993: Assignment invalid: mismatch between method and method variable </p>
 
−
 
 
−
This change is enabled in V7.7 with the application of zap 77z128.
 
−
 
 
−
===Optional output method parameters===
 
−
Prior to this release output parameters could not be optional or have default values. In this release output parameters can be specified as <var>Optional</var>, and a default value can be specified with <var>Default</var>. One related change is that if a <var>Len</var> value is specified with <var>Optional</var> or <var>Default</var> <var>Output</var>, it indicates the length of the hidden target for the output parameter if none was passed. For all other <var>Output</var> parameters, <var>Len</var> is meaningless, just as it was before Model 204 V7.8. The following is an example of the use of an optional output parameter:
 
−
<p class="code">function getRemote( -
 
−
  %target is string len 32, %errorReason is string len 80 optional output -
 
−
) is float
 
−
  ...
 
−
</p>
 
−
In this example, if <code>%errorReason</code> is not specified in a call and then set to a value longer than 80 bytes it will be truncated to 80 bytes. However, if a string of a different length is passed, the length of that string will determine truncation behavior.
 
−
 
 
−
==External Call Facility enhancements==
 
−
===Managing ECF tables more efficiently===
 
−
There are two new features to help manage ECF tables more efficiently, avoid conditions where the table can fill, and prevent the definition of further entities.
 
−
 
 
−
The first feature is the new <var>DISPLAY ECF</var> command, which displays the contents of ECF tables and also the current status of users accessing ECF modules. See more details of the <var>[[#DISPLAY ECF|DISPLAY ECF]]</var> command below.
 
−
 
 
−
The second feature is a new <var>EXTERNAL REMOVE</var> statement with the following syntax:
 
−
 
 
−
<p class="syntax">EXTERNAL REMOVE <span class="term">modulename</span></p>
 
−
 
 
−
This statement causes the entry for the named module to be removed from the module table. The table entry is then placed on a free chain of entries and can be reused by issuing the <var>[[External_Call_Facility#External_Module_statement|EXTERNAL MODULE]]</var> statement. This allows the module table to be managed with redundant entries removed, without having to recycle the ONLINE.
 
−
 
 
−
An <var>EXTERNAL REMOVE</var> statement will return <code>$status/$statusd</code> values of <code>0/0</code>, and most other status values that can be returned by the <var>EXTERNAL REMOVE</var> statement are already documented in the ECF return codes table. If an <var>EXTERNAL REMOVE</var> is attempted against a module that is currently being called (in use), then <code>$status/$statusd</code> will return the values <code>20/1</code> (module unavailable).
 
−
 
 
−
==System enhancements==
 
−
 
 
−
===New wait types for daemon/master waits===
 
−
 
 
−
Two new wait types, viewable on the <var>[[MONITOR_command|MONITOR]] USERS</var> command output, have been implemented as follows:
 
−
 
 
−
<code>57</code> - Means a daemon thread waiting for its master thread  <br />   
 
−
<code>58</code> - Means a master thread waiting for one of its daemon threads
 
−
 
 
−
This change is enabled in V7.7 with the application of zap 77z410.
 
−
 
 
−
===Snap formatting changes===
 
−
Date/time stamps in the page headers of snaps will now be shown in normal format, rather than in Julian format as in previous versions. So in the following example, a particular snap header under v7.7 or previous versions would show as:
 
−
 
 
−
<p class="syntax">SNAPID    1  19226.060155  M204.0022: Bug .. nnnnn              PAGE    1 </p>
 
−
 
 
−
whereas the same snap header under v7.8 would show as:
 
−
 
 
−
<p class="syntax">SNAPID    1  2019/08/14 06:01:06  M204.0022: Bug .. nnnnn        PAGE    1 </p>
 
−
 
 
−
Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.9 should be marginally smaller than the same snap generated under previous versions, assuming the same <var>[[SNAPCTL parameter|SNAPCTL]]</var> settings.
 
−
 
 
−
===Call stack trace for problem diagnosis===
 
−
A  call stack trace is now provided to help diagnose and resolve common errors. To enable the stack trace, do either of the following:
 
−
<ul>
 
−
<li>Set the <var>[[SIRFACT parameter|SIRFACT]] X'01'</var> bit.</li>
 
−
<li>Set the <var>[[DEBUGUL parameter|DEBUGUL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. <p>(<var>DEBUGUL</var> provides a similar facility with an include trace of procedures leading to the error, but this might not be potentially as useful as the call trace.)</p>
 
−
</li>
 
−
</ul>
 
−
 
 
−
The call stack trace can assist in diagnosing run-time errors that might occur, as illustrated by the following "Variable too small for result" and "MBSCAN exceeded" examples.
 
−
 
 
−
====Variable too small for result====
 
−
When the stack trace is enabled, a "variable too small" error results in the following message:
 
−
 
 
−
<p class="syntax">M204.2966: Error at line n, procedure ''procname'' in file ''procfile''</p>
 
−
 
 
−
which identifies the line within a procedure where the error is occurring, in addition to the usual message:
 
−
 
 
−
<p class="syntax">M204.0552: Variable too small for result</p>
 
−
 
 
−
Any subsequent M204.2966 messages indicate the point in the code from where the code in error was called. For example, a stack of three subroutine calls leading to a "variable too small" error might result in the following messaging:
 
−
<p class="syntax">M204.0552: Variable too small for result                            M204.2966: Error at line 978, procedure DOCOOLSTUFF in file COOLFILE
 
−
M204.2966: Called from line 1215, procedure FOOBAR.CLASS in file CLASSES
 
−
M204.2966: Called from line 378, procedure SILLY.CLASS in file CLASSES
 
−
M204.2966: Called from line 187, procedure P.ROCKANDROLL in file APSYFILE
 
−
</p>
 
−
 
 
−
This information should help in diagnosing the problem.
 
−
 
 
−
If the error occurs within a command level program rather than a procedure, then the M204.2966 message is replaced by an M204.2967 message, and a similar error condition to the above with a preceding call stack might be audited as follows:
 
−
<p class="syntax">  M204.0552: Variable too small for result             
 
−
  M204.2967: Error at line 14 of command level program 
 
−
  M204.2967: Called from line 5 of command level program
 
−
  M204.2967: Called from line 3 of command level program </p>
 
−
 
 
−
If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 
−
<p class="syntax">  M204.0552: Variable too small for result
 
−
  M204.2968: Error: no debug info </p>
 
−
 
 
−
====MBSCAN exceeded====
 
−
Similarly to the handling of the "variable too small for result" error, the call stack can also be used to diagnose errors where the value of <var>[[MBSCAN parameter|MBSCAN]]</var> is exceeded as a result of a direct search of Table B records.
 
−
<p>Again, under V7.8, with either the <var>SIRFACT X'01'</var> bit set or <var>DEBUGUL</var> set, if a long request occurs as a result of exceeding <var>MBSCAN</var>, then initially the following message is produced, as before:</p>
 
−
<p class="syntax">M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''</p>
 
−
followed by a DYRWT prompt message. If the user replies 'N' to the prompt, or if the request is run in an environment (such as a batch job) where the default response is 'N', the following message is produced after the M204.0569 message:
 
−
<p class="syntax">Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''</p>
 
−
 
 
−
where ''mm'' is the current setting of <var>MBSCAN</var>. The M204.2969 message is followed by M204.2966 messages displaying the call stack trace. Thus, if the following code is run from procedure MYPROC.MBSCAN against the demo database, with an <var>MBSCAN</var> setting of 10:
 
−
<p class="syntax">  b                         
 
−
  call sub1                 
 
−
  sub1: subroutine           
 
−
  fd1:                       
 
−
      in clients fd city = ONTARIO
 
−
              end find       
 
−
      fr fd1                     
 
−
        pai                     
 
−
        print                   
 
−
      end for                   
 
−
  end subroutine             
 
−
  end </p>
 
−
 
 
−
then the following messages are produced, assuming any prompts are responded to with an 'N':
 
−
<p class="syntax">  M204.0569: File CLIENTS, Find: Table B records to be searched = 3415
 
−
  Cancelling request: M204.2969: MBSCAN (10) exceeded, records to be searched = 3415 
 
−
  M204.2966: Error at line 6, procedure MYPROC.MBSCAN in file MYPROC
 
−
  M204.2966: Called from line 3, procedure MYPROC.MBSCAN in file MYPROC  </p>
 
−
 
 
−
===appendJournalData===
 
−
The <var>[[AppendJournalData_(Stringlist_function)|AppendJournalData]]</var> function is now more tolerant of an outstanding BUMP request. Previously, if <var>AppendJournalData</var> was called to inadvertently retrieve a large amount of journal data, typically when called implicitly from within SirScan, then any outstanding BUMP request wouldn't be honored until all of the data had been retrieved, at which point the BUMP request would be completed, and all data would be lost.
 
−
 
 
−
Now, the <var>AppendJournalData</var> process checks for outstanding BUMP requests before each track I/O is executed, thus avoiding excessive I/Os against the journal and long waits for the BUMP of such a process to complete.
 
−
 
 
−
==Editor enhancements==
 
−
<p>The [[Model 204 full-screen editor#exit|Model 204 editor]] has been enhanced to not hold a lock on a procedure being edited. Instead the timestamp of the procedure on disk is compared against that of the edited procedure when it was loaded or last saved. If different, the save is not allowed. New commands <var>SSAVE</var>, <var>EEND</var>, and <var>GGO</var> are available to force the save in this situation.</p>
 
−
<p>In addition, the <var>GO</var> command no longer updates the procedure on disk before <var>INCLUDE</var>ing it if it has not been modified in the editor.</p> 
 
−
==AUDIT204 enhancements==
 
−
===FORMAT command===
 
−
TIMEHH is a new parameter used with the FORMAT command of the [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#AUDIT204_utility|AUDIT204]] utility.  It indicates that timestamps, printed at the beginning of each line of output, should include hundredths of a second. Requires no other arguments.
 
−
<p><b>NOTE:</b> This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.</p>
 
−
For example:
 
−
<p class="syntax">//CCAIN DD *
 
−
FORMAT YEARFORM 4
 
−
TIMEHH
 
−
TYPE ER MS LI</p>
 
−
 
 
−
==Recovery enhancements==
 
−
===Media Recovery in a multi-user environment===
 
−
It is now possible to perform media recovery by issuing the <var>REGENERATE</var> command to roll forward selected files in a multi-user environment, with the media recovery being carried out by different users with system manager privileges. The new USING option allows for the specification of a ddname for the input journal stream to be used by the <var>REGENERATE</var> command. Previously media recovery was restricted to single user batch jobs, using the CCAGEN ddname for the input journal. For more details, see the <var>[[#REGENERATE|REGENERATE]]</var> command below.
 
−
 
 
−
===MERGEJ now supports up to 99 input journals===
 
−
The MERGEJ utility, used to merge journals with overlapping timestamps prior to running Media Recovery, now supports up to 99 input SORTINnn journals to be merged. For this release it is still the case that any previously merged journal must be defined as SORTIN01 to the MERGEJ run, and thus that the MERGEJ run can not accept more than one previously merged journal as input.
 
−
 
 
−
This change is also enabled in V7.7 with the application of 77z487.
 
−
 
 
−
==Security enhancements==
 
−
===CA-Top Secret can disallow CCASTAT logins===
 
−
The [[CA-Top_Secret_interface|CA-Top Secret]] interface now recognizes the <code>DEFACID=</code>, setting and does not allow CCASTAT logins in the online if <code>DEFACID</code> is set to null. (There is no attempt to log on M204USR.) Therefore, to disallow CCASTAT logons, set DEFACID=, in [[CA-Top_Secret_interface#Preparing_a_TOPSPARM_parameter_module_with_TOPSGEN|TOPSPARM]]. CCASTAT will be opened because it contains file and group passwords, but it will not be used for logons if CCASTAT logons are not allowed.
 
−
 
 
−
===CUSTOM=11 and mixed cased input===
 
−
The <var>[[CUSTOM_parameter|CUSTOM]]</var> parameter <var>CUSTOM=11</var> setting no longer requires that a <var>*LOWER</var> command be issued prior to a <var>LOGCTL</var> command (to add or change a  password) to preserve mixed case input. Prior to this release, with <var>CUSTOM=11</var> in place, *LOWER had to be issued before a <var>LOGCTL</var> command, otherwise any mixed case password strings would automatically be translated into uppercase. This change is enabled in V7.7 with the application of zap 77z108.
 
−
 
 
−
===DEFUSER can specify a jobname not authorized to access M204===
 
−
When specifying DEFUSER=JOBNAME and VALIDAT=LOGON in the RACFGEN parms for an ONLINE, if the specified jobname (the owning id for the ONLINE job) isn't authorized to use Model 204 via RACF, any LOGIN commands specifying no userid will now succeed (previously such a LOGON would have failed). This enables users to submit jobs with USE $JOB, whereby the string USER=jobname will be added to the submitted JCL. This in turn is useful if the specified jobname has dataset access privileges to datasets required by the submitted jobs, even if the jobname itself isn't authorized to use M204.
 
−
 
 
−
==Janus product enhancements==
 
−
 
 
−
===Web API calls available on transactional daemons===
 
−
Transactional daemons can now use the Janus Web API, mostly $functions that begin with <var>$web</var>. The new [[$Web_Api|$web_api function]] makes it possible to test if the Janus Web API is available, whether on a Janus Web Server thread or one of its transactional daemons.
 
−
 
 
−
===Web Sockets===
 
−
Web Sockets are now supported in Janus Web Server.
 
−
 
 
−
The Web Socket protocol provides various advantages over the HTTP protocol:
 
−
<ul>
 
−
<li>Web Sockets allow full-duplex communication.</li>
 
−
<li>Efficient framing of payload data uses minimal overhead.</li> 
 
−
<li>The Web Socket protocol is end-user extensible.</li> 
 
−
<li>Most importantly, Web Sockets can be deployed completely within an existing HTTP/HTTPS framework.</li>
 
−
</ul>
 
−
 
 
−
To implement Web Sockets, you must enable the Janus Web port for Web Socket upgrades with the new <var>WEBSOCKET</var> parameter. The WEBSOCKET option can be specified on either the port definition or the JANUS WEB rule for the URL.
 
−
Likewise, an individual Janus Web rule can either allow or disallow Web Socket connections with the <var>WEBSOCKET</var> and <var>NOWEBSOCKET</var> parameters, respectively.
 
−
 
 
−
For details on implementing Web Sockets, see the [[WebSocket_(Socket_function)|WebSocket]] wiki page.
 
−
 
 
−
===$Web_Form_Parm_Binary===
 
−
Janus Web now defers ASCII to EBCDIC translation of form parameter values until a value is requested. This makes it possible to retrieve the exact values sent by the client rather than a translated version. This is important if a form parameter value is UTF-8 encoded and contains non-7-bit ASCII characters (for example if a form parameter contains XML). The [[$Web_Form_Parm_Binary]] function returns the exact value sent by a client for a form parameter with no character translation.
 
−
 
 
−
===Janus Web Server access rule===
 
−
The automatic <var>[[JANUS WEB ALLOW]]</var> rule, which allowed any user to access the port without requiring a login, is changed <i>for non-SSL ports</i> to the following:
 
−
<p class="code">JANUS WEB <i>portname</i> DISALLOW *
 
−
</p>
 
−
<p>
 
−
This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
 
−
The rule applies unless overridden by user-added rules.
 
−
</p>
 
−
<blockquote class="note">
 
−
<p><b>Note:</b> To revert from this change in the JANUS DEFINE default and make the default
 
−
non-SSL <var>ALLOW</var> rule as it was in version 7.5 and earlier (<code>ALLOW *</code>), turn on the 1 bit of the <var>[[WEBDFLT parameter|WEBDFLT]]</var> parameter: </p>
 
−
<p class="code">RESET WEBDFLT=1</p>
 
−
</blockquote>
 
−
 
 
−
===Increase in pending accepts for Janus BPX ports===
 
−
The default number of pending accepts for Janus BPX server ports has been increased from 3 to 12, thus reducing the likelihood that a pending accept may fail with the message
 
−
 
 
−
<p class="code">MSIR.0019 Connection request rejected for port (port), MAXCON exceeded</p>
 
−
 
 
−
The actual number of pending accepts to be supported on the port can be set with the new parameter MAXPEND, set on the <var>[[JANUS_DEFINE|JANUS DEFINE]]</var> command, where MAXPEND can vary from 3 up to a maximum value of 32. The change to the default value is enabled in V7.7 with the application of zap 77z269.
 
−
 
 
−
===TCP listen backlog increased===
 
−
 
 
−
The [[Program_Communication_facilities#LISTEN_call|TCP listen]] backlog has been increased from 16 to 1024 under z/OS.
 
−
 
 
−
This update tells the TCP stack to queue up a maximum of 1024 such requests before dropping any. This increased backlog reduces, or in most cases eliminates, the likelihood of a connection request drop, other than in exceptional circumstances, such as a denial of service attack. This change is enabled in V7.7 with the application of zap 77z340.
 
−
 
 
−
===Defer the freeing of XMLSCREEN input XML===
 
−
 
 
−
The freeing of <var>[[XMLSCREEN_and_NOXMLSCREEN_(JANUS_DEFINE_parameters)|XMLSCREEN]]</var> input XML is now deferred until the next Read Screen or session termination. This means that if an application error is detected, the input XML can be retrieved with [[$Web_Input_Content|$Web_Input_Content]] and then logged for problem analysis.
 
−
 
 
−
Prior to this release the XML received from the client was freed immediately after being used to set the input data for a Read Screen, rendering it unavailable for problem determination.
 
−
 
 
−
This change is enabled in V7.7 with the application of zap 77z368.
 
−
 
 
−
===XMLSCREEN and Janus Web Legacy blank stripping===
 
−
 
 
−
xmlScreens and Janus Web Legacy screens now adhere to the same standard as standard screen processing in terms of stripping leading blanks from input fields defined as [[Full-screen_feature#DEBLANK_or_NODEBLANK_option|DEBLANK]] (either explicitly or implicitly).
 
−
 
 
−
This change is enabled in V7.7 with the application of zap 77z400.
 
−
 
 
−
===SSL input buffer size===
 
−
 
 
−
The default value of <var>[[SSLIBSIZE_(JANUS_DEFINE_parameter)|SSLIBSIZE]]</var> has been increased to 16384 + 128, or 16512. This size should ensure correct communication with all TLS spec compliant applications. It is the maximum size allowed unless you use <var>[[CUSTOM_parameter#Using_CUSTOM.3D.2818.29|CUSTOM=18]]</var>.   
 
−
 
 
−
This change is enabled in V7.7 with the application of zap 77z415.
 
−
 
 
−
===Increasing LDAP buffers===
 
−
 
 
−
The number of LDAP buffers allocated at startup can now be changed by setting the <var>NLDAPBUF</var> parameter in CCAIN. See below for details on <var>[[#NLDAPBUF|NLDAPBUF]]</var>.
 
−
 
 
−
===Increase URL length returned with $web_form_action===
 
−
With this release the maximum Janus Web Server incoming URL that can be handled by <var>$web_form_action</var> is increased from 512 bytes to 1280 bytes. This change is enabled in V7.7 with the application of zaps 77z424 and 77z448.
 
−
 
 
−
===Maximum RBSIZE setting increased===
 
−
The maximum value for RBSIZE, set on the <var>[[JANUS DEFINE|JANUS DEFINE]]</var> command, is now increased to 16777215 (previously the maximum was 65534). RBSIZE specifies the RPC or Request Buffer size.  On a Web port, the Janus request buffer holds browser request information such as header data, cookies, and form data. On other port types, it holds RPC input and output parameters. This change is enabled in V7.7 with the application of zap 77z427.
 
−
 
 
−
===Limiting the production of MSIR.0019 and MSIR.0020 messages===
 
−
The production of the following messages
 
−
 
 
−
<p class="code">MSIR.0019 Connection request rejected for port (port), MAXCON exceeded</p>
 
−
 
 
−
<p class="code">MSIR.0020 Connection request rejected for port (port), no SDAEMONS available</p>
 
−
 
 
−
is now limited to a maximum of one each per time interval set by the <var>[[MAXAUSEW_parameter|MAXAUSEW]]</var> parameter ( minimum seconds between <var>[[MAXAUSER_parameter|MAXAUSER]]</var> warnings, which defaults to 10 seconds ). This avoids flooding the journal / jlog with these messages in situations where the number of connections on a port has been exceeded ( MSIR.0019 ), or the the number of available daemon threads has been exceeded ( MSIR.0020 ).
 
−
 
 
−
This change is available in V7.8 with the application of zap 78z011, and within V7.7 with the application of 77z466
 
  
 
==Debugger enhancements==
 
==Debugger enhancements==
 
These enhancements apply to the Janus and TN3270 debuggers.  
 
These enhancements apply to the Janus and TN3270 debuggers.  
  
−
===Access to exposed variables===
 
−
The debuggers can now view or watch the values of variables exposed to local routines/methods. Previously, any attempts to access an exposed variable would have displayed "%varname has no value" in the debugger session. This feature is enabled in V7.7 with the application of zap 77z363.
 
−
 
−
===Subroutine or method display===
 
−
When execution pauses for a break point or runtime error, the subroutine or method being executed is indicated in the status area.  In addition, the source code line information available by right-clicking on a source line now also indicates the subroutine or method.
 
  
 
==Performance enhancements==
 
==Performance enhancements==
−
 
−
===MP/204 offload improvements===
 
−
Application code issuing the following SOUL statements will be fully offloadable:
 
−
<ul>
 
−
<li><var>File Records In/On</var></li>
 
−
<li><var>Remember</var></li>
 
−
<li><var>Position</var></li>
 
−
<li><var>Sort Values</var></li>                                           
 
−
<li><var>Reset Header/Trailer</var></li>
 
−
<li><var>Find and Print Count</var></li>
 
−
<li><var>Find All Values</var></li>
 
−
<li><var>For Each Value</var></li>
 
−
</ul>
 
−
The above improvements are enabled in V7.7 with the application of zaps 77z419 and 77z420.
 
−
 
−
Also, [[JANUS WEB|Janus Web rules]] scanning will be offloadable. In addition, the scan for persistent web sessions ([[$Web_Form_Done]] and [[Janus Web Legacy Support]]) will be offloadable. While the rendezvous with the persistent thread will still be maintask-only, stateless requests will not need to go back to the maintask to be processed and, even for persistent requests, the persistent session lookup will be offloadable. These changes should provide better scalability for MP/204 sites with heavy Janus Web activity.
 
−
 
−
===X3270OUT exit offloadable===
 
−
When running MP/204 (AMPSUBS>0) and using the [[Coding_SNA_Communications_Server_conversion_exit_routines#X3270OUT_.28convert_output_from_3270_format.29|X3270OUT]] exit to convert a 3270 output data stream to the appropriate device protocol, the exit can now run in parallel mode to improve performance. This change is enabled in V7.7 with the application of zap 77z313.
 
−
 
−
The X3270OUT exit must be written to be re-entrant.
 
−
 
−
===Internal performance improvements===
 
−
A number of internal performance and optimisation improvements have been made in this release. these include
 
−
 
−
<ul>
 
−
<li>Sampling buffer pool pages rather than carrying out a full scan of large buffer pools ( NUMBUFG > 200000 ) when calculating BUFFnnn stats for SirMon</li>
 
−
<li>Optimising group and file closure, in particular providing relief on exit from APSYs where a lerga number of groups may be in use, and where the groups may comprise a large number of file members</li>
 
−
<li>Improved handling of timer queues, particularly in an MP/204 environment</li>
 
−
<li>More aggressive prioritisation of journal and checkpoint I/O, in order to reduce user waits for such I/), and to reduce related waits on critical file resources
 
−
</ul>
 
−
 
−
==New and changed commands==
 
−
===MONITOR===
 
−
The MONITOR command output now contains a new column, headed LOG, that shows the logon status of each user in the system, for example
 
−
<p class="code">
 
−
USER SVR        FLS  PCPU SMPLS  RUNG    REDY    BLKI    WTSV    BLKO  SWPG
 
−
                  7 0.330                                                   
 
−
                                                                             
 
−
USER SVR USERID    P CUR  SLICE LOG FUNC  CNCT        CPU  SEQIO QUE  WT FLGS
 
−
  0  1 SUPERKLUGE S  56  0.031 CCA EVAL    5      0.012    221 OFFI 12  65
 
−
  4  2 ADMIN      S  51  0.031 CCA          1      0.000    22 RUNG       
 
−
  20    VT75DIED          0.000              0      0.000      0      2  20
 
−
  21    VT75READ          0.000            37      0.000      0      3  00
 
−
  22    VT75ERRS          0.000              0      0.000      0      2  20
 
−
  23    CHKPTIMO          0.000              0      0.000      0      12  20
 
−
  24    CHKPTIMR          0.000              0      0.000      0      12  20
 
−
  25    CHKPPST            0.000              0      0.000      0      12  20
 
−
  26    CHKPAWW            0.000              0      0.000      0      12  20
 
−
  27    TC62RAPS          0.000              0      0.000      0      27  04
 
−
  28    TC62SRVC          0.000              0      0.000      0      27  20
 
−
>                                                                             
 
−
</p>
 
−
The LOG column replaces the AGE column in the MONITOR output, as this information was considered more relevant for this command output. Possible values that are shown in the LOG column are as follows
 
−
<ul>
 
−
<li> CCA - CCASTAT userid</li>
 
−
<li> ESM - userid validated by an External Security Manager - ACF2, RACF, or TopSecret/li>
 
−
<li> SUB - Subsystem controlled logon</li>
 
−
<li> GST - Guest - neither logged on via CCASTAT nor by an ESM</li>
 
−
<li> PDG - Logon pending due to errors (e.g. invalid password)</li>
 
−
</ul>
 
−
 
−
This change is also available with V7.7 with the application of zap 77z478.
 
−
 
−
===MONITOR IODEV===
 
−
This new command displays the total number, the current usage and the maximum number of each IODEV type. <p> If the Model 204 parameters include telnet threads (TNDEV parameter), the specified IODEV will actually execute as a daemon thread (SDAEMDEV parameter). For that reason, both the telnet and daemon IODEVs will be incremented and the telnet IODEV will appear with an appended '*'. </p>
 
−
<p class="code">M IODEV </p>                     
 
−
Iodev  Total  Active ( % )  Maximum ( % )                               
 
−
    1      1      1  100%        1  100%                               
 
−
    7    300    100  33%      150  50%                               
 
−
    11      4      0    0%        1  25%                               
 
−
    15    500      50  10%      80  16%                               
 
−
    25      1      0    0%        0    0%                               
 
−
    27    10      0    0%        0    0%                               
 
−
    29    10      1    10%      1    10%                               
 
−
    51      5      0    0%        0    0%
 
−
    21*            1              1
 
−
 
−
===DISPLAY ECF===
 
−
<p class="code">DISPLAY ECF {{ M | N | U } like ?} </p>
 
−
 
−
This new command displays details from ECF tables, or the current status of users accessing ECF modules.
 
−
 
−
<code>D ECF M</code> displays the contents of the module table. For example:<p class="code">    D ECF M
 
−
    Module  Loadlib  Address:Length    Loaded@      Lastused@  #Calls  Flags
 
−
    QATUM13C PROGLIB 2FB91FB8:00000028 19023:121506 19023:121506 00000001
 
−
    QATUM13B PROGLIB 2FE65000:00009C18 19023:121506 19023:121506 00000001
 
−
    QATUM13A PROGLIB 2FE6EC18:00001CD8 19023:121506 19023:121506 00000001 
 
−
</p>
 
−
(flags may be D=deleted; S=shared; H=halted; I=Idle)
 
−
 
−
<code>D ECF N</code> displays contents of the name table. For example: <p class="code">    D ECF N
 
−
    Module  Logical-call-name
 
−
    QATUM13C MOD_QATUM13C
 
−
    QATUM13B MOD_QATUM13B
 
−
    QATUM13A MOD_QATUM13A </p>
 
−
 
−
<code>D ECF U</code> displays details of users currently accessing ECF modules. This is also the default option, and so <code>D ECF</code> will display the same output as <code>D ECF U</code>. For example:
 
−
<p class="code">    D ECF U                         
 
−
    User# Userid    Module  Parmlen
 
−
    00002 ADMIN      --none--       
 
−
    00003 ADMIN      COBSAMP1 00000002
 
−
    00004 ADMIN      COBSAMP1 00000002 </p>
 
−
 
−
<code>D ECF <var class="term">function</var> LIKE <var class="term">?</var> </code> (where <var class="term">?</var> is a valid pattern) displays details for entities that match the specified pattern. The function is either M (modules), N (names), or U (users), and it defaults to U. So for example:
 
−
 
−
<p class="code">D ECF U L A</p>
 
−
or
 
−
<p class="code">D ECF U L A*</p>
 
−
 
−
displays details of ECF users whose names begin with A.
 
−
 
−
===REGENERATE===
 
−
The <var>[[REGENERATE command|REGENERATE]]</var> command can now be run in a multi-user environment by multiple users with system manager privileges. A new option USING is provided to specify the ddname of the input journal, so that the full syntax is now as follows:
 
−
<p class="code">  REGENERATE [USING ddname] FILE filename [FROM dumpname | IGNORE]
 
−
  [TO {LAST UPDATE [BEFORE yy.ddd hh:mm:ss.th] | LAST CHECKPOINT [BEFORE yy.dd hh:mm:ss.th]
 
−
  | UPDATE number OF yy.ddd hh:mm:ss.th | CHECKPOINT yy.ddd hh:mm:ss.th} ]</p>
 
−
 
−
The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 
−
<p class="code">  ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
 
−
  REGENERATE USING REGEN1 FILE TEST</p>
 
−
 
−
It is the user's responsibility to ensure that the file being regenerated is not in use, and so prior to usage, <var>BUMP FILE</var> and <var>STOP FILE</var> should be used to isolate usage against the file. If the file is in use, the REGEN will fail with these messages:
 
−
<p class="code">  M204.1430: Failed to open file TEST
 
−
  M204.1436: Stopped processing file TEST  </p>
 
−
 
−
$STATUS will now be set for <var>REGENERATE</var> with the following values:
 
−
<blockquote>   
 
−
    0 - Success <br/>
 
−
    1 - No files were processed <br/>
 
−
    2 - At least one file stopped processing <br/>
 
−
    4 - A serious error occurred, REGEN failed
 
−
</blockquote>
 
−
 
−
Similarly, <var>[[SETGRC command|SETGRC]]</var> may be used to get the return code and error message.
 
−
 
−
==New and changed parameters==
 
−
 
−
===COMMITX===
 
−
The commit exit runs within the APSY defined by the <var>COMMITX</var> parameter and uses normal APSY processing.
 
−
 
−
The new parameter <var>COMMITX</var> is settable from User 0's parameter line or by the system manager. It can be reset at any time by the system manager.
 
−
 
−
Setting/Resetting the parameter sends a DYRWT message to the issuer and requires a Yes or No response (unless set/reset by user0).
 
−
 
−
If <var>COMMITX</var> is specified, all APSY subsystems participate by default but any can be exempted.
 
−
 
−
===ECMSUBS===
 
−
This maximum value may now be reset dynamically by a system manager. If the value is raised, new tasks will be added as needed up to the value specified. If the value is lowered, idle subtasks will be detached before they are activated until the new maximum is established.
 
−
 
−
===ECMODS===
 
−
The new minimum value for ECMODS, the allowable number of ECF modules, is 1. Prior to V7.8 the minimum value was 0. This change is enabled in V7.7 with the application of zap 77z306.
 
−
 
−
===ECNAMES===
 
−
The new minimum value for ECNAMES, the allowable number of ECF module names, is 1. Prior to V7.8 the minimum value was 0. This change is enabled in V7.7 with the application of zap 77z306.
 
−
 
−
===ECPSIZE===
 
−
The new minimum value for ECPSIZE, the initial storage allocation for ECF parameters, is 1024. Prior to V7.8 the minimum value was 0. This change is enabled in V7.7 with the application of zap 77z306.
 
−
 
−
===ENQTIME===
 
−
Millisecond duration of automatic record locking retry wait.
 
−
 
−
Prior to this change, if record locking conflicts occur frequently in a busy online, any user with a non-zero value for <var>[[ENQRETRY parameter|ENQRETRY]]</var> will wait at least 3 seconds before the conflict is dealt with. This can degrade overall system performance.     
 
−
                                                       
 
−
The <var>[[ENQTIME parameter|ENQTIME]]</var> parameter specifies the number of milliseconds waited for each record locking retry wait. <var>ENQTIME</var> can be between 1 and 60000, corresponding to a minimum of 1 millisecond and a maximum of 1 minute. The default value of <var>ENQTIME</var> is 3000 (3 seconds).           
 
−
                                                       
 
−
For example, with <code>ENQTIME = 100</code> and <code>ENQRETRY = 7</code>, after a record locking conflict occurs the thread will retry 7 times with wait intervals of .1 seconds, and so within at most .7 seconds either the lock becomes available or the conflict triggers an On unit or cancels the request.   
 
−
                                                       
 
−
The <var>ENQTIME</var> parameter may also be reset with $ResetN.
 
−
 
−
This new parameter is enabled in V7.7 with the application of zap 77z299.
 
−
 
−
===EVALOPT===
 
−
The new <var>EVALOPT</var> parameter controls the cancellation of a request on truncation of string data. The default value is 0, and currently there is just one setting, 1, which means "cancel a request if truncation of string data occurs."
 
−
 
−
For example, with the default of 0 in place, the following code <p class="code">    %x is string len 1 
 
−
    %y is string len 2 
 
−
    %y = 'ab'           
 
−
    %x = %y             
 
−
    printtext {~} = {%x} </p>
 
−
 
−
would cause silent truncation, and give the result
 
−
    <p class="code">%x = a </p>
 
−
 
−
If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
 
−
    <p class="code">M204.0552: Variable too small for result </p>
 
−
 
−
and the request is cancelled.
 
−
 
−
===LFSCB===
 
−
<var>LFSCB</var>, the length of the full screen buffer, now has a new minimum value of 8 (the previous minimum was 0). This change is enabled in v7.7 with the application of zap 77z042, and within V7.6 with the application of zap 76z393.
 
−
 
−
 
−
===MAXPRE, MAXBOUT, MAXSUBT===
 
−
<p>Introduced in zap 77z257.</p>
 
−
The new <var>MAXPRE</var>, <var>MAXBOUT</var>, and <var>MAXSUBT</var> parameters can be used to cancel a runaway transaction and prevent it from filling the checkpoint data set.
 
−
<ul>
 
−
<li><var>MAXPRE</var>:  Maximum number of pre-images per transaction.  </li>
 
−
<li><var>MAXBOUT</var>: Maximum number of backout pages per transaction. </li>
 
−
<li><var>MAXSUBT</var>: Maximum number of subtransaction checkpoints that a transaction can span.</li></ul>
 
−
 
−
<p>Each new parameter defaults to unlimited. </p>
 
−
<p>If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:</p>
 
−
<p class="code">M204.0524: Maximum number (<i>num</i>) of <i>parameter</i> exceeded.</p>
 
−
where <i>num</i> is the value set for <i>parameter</i> (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).
 
−
 
−
===MODENAME in a Transfer Control PROCESSGROUP===
 
−
Previously the MODENAME parameter has been ignored in VTAM TRANSFER PROCESSGROUP processing. 
 
−
 
−
As of V78 with 78Z029 applied, Users will be able to control the characteristics of a session (for example, Display Model, Ru size, EDS support et al.) bound at the VTAM Transfer Control Target
 
−
by means of the VTAM Transfer PROCESSGROUP's MODENAME.
 
−
 
 
−
A null or unspecified MODENAME in a VTAM Transfer PROCESSGROUP definition will result in the Target LU's 
 
−
Default LOGMODE being used to Bind the Target Session (This is how all VTAM Transfers worked previously). 
 
−
   
 
−
Specifying MODENAME=LOGON or MODENAME=LOGIN in a VTAM TRANSFER PROCESSGROUP definition results in the LOGMODE used   
 
−
to Logon to the Source Online also being used to Bind the Session at the Transfer Target.               
 
−
 
 
−
Otherwise, anything specified in a VTAM TRANSFER PROCESSGROUP MODENAME parameter will be assumed to be a
 
−
valid VTAM LOGMODE and will be used to Bind the Transferred session at the Target. There is a potential
 
−
for upward incompatibility in the case where a VTAM TRANSFER PROCESSGROUP definition specifies an invalid value for MODENAME:
 
−
 
 
−
Since the MODENAME is no longer ignored, an invalid value will now fail the Transfer.
 
−
   
 
−
A failed Transfer consequent to an invalid LOGMODE or a LOGMODE unknown at the Target is flagged with:
 
−
M204.2483 'unknown-modename  is not a valid LOGMODE name'.
 
−
 
−
===MQMXTASK===
 
−
This maximum value may now be reset dynamically by a system manager. If the value is raised, new tasks will be added as needed up to the value specified. If the value is lowered, idle subtasks will be detached before they are activated until the new maximum is established.
 
−
 
−
===NLDAPBUF===
 
−
This new parameter allows the number of LDAP buffers allocated during startup to be set in CCAIN. The default value is 2, and the settable value can range from 0 to 65535.
 
−
 
−
===PUPDTH (new minimum value)===
 
−
If a user sets the <var>[[PUPDTH parameter|PUPDTH]]</var> parameter to 0, it will now automatically be increased to 1, its minimum value.
 
−
 
−
===SERV4G===
 
−
This parameter allows testing of server tables that span a 4-gigabyte boundary. For example, if <var>SERV4G</var> is <code>X'FFFFF000'</code>, each ATB server will begin at <code>XX_FFFFF000</code>. If <var>SERV4G</var> is <code>X'FFFF0000'</code>, each ATB server will begin at <code>XX_FFFF0000</code>. <code>XX</code> is determined by the storage available on the system. The parameter is set in CCAIN.
 
−
 
−
The contents of the ATB server are specified by using the <var>[[SERVGA parameter|SERVGA]]</var> parameter.
 
−
 
−
For example, if you want VTBL to span the 4G boundary, you can use these settings: <code>SERV4G=X'FFFFF000'</code>, <code>SERVGA=X'00040000'</code>, and <code>LVTBL=200 (6400 bytes, X'1900')</code>. This will force each server's VTBL to begin at <code>XX_FFFFF000</code> and end at <code>XX+1_00000900</code>.
 
−
===SIRTERM===
 
−
The <var>[[SIRTERM parameter|SIRTERM]]</var> (Sirius terminal options) parameter settings have changed.
 
−
The changes to <var>SIRTERM</var> allow a user to preclude a reset to a Model that is not supported by the terminal emulator in use.
 
−
 
−
The X'01' setting (MODEL 6 support) is no longer used.
 
−
 
−
The X'02' setting (Write Structured Field Query Support) now supports MODEL 6 terminals by default.
 
−
 
−
The new X'08' setting always issues a Write Structured Field Query for Terminal Model Resets for terminals connected to Model 204 through VTAM or TELNET, provided that X'02' has been set. This precludes Terminal Model RESETs to Models that are not supported by the terminal emulator in use.
 
−
 
−
===WEBDFLT===
 
−
At V7.7, the default access rule for non-SSL ports was changed from ALLOW * to DISALLOW *, meaning that unless any ALLOW rules were in place resulting in a login/password prompt, the port couldn't be accessed. The new <var>[[WEBDFLT_parameter|WEBDFLT]]</var> parameter may be set to 1 for reversion to the old default of ALLOW *. This new parameter is enabled in V7.7 with the application of zap 77z090.
 
−
 
−
<var>RESET WEBDFLT</var> requires system administrator privileges. It is recommended to reset the 1 bit of <var>WEBDFLT</var> to zero after issuing a series of <var>JANUS DEFINE</var> commands which need <var>WEBDFLT=1</var>, as in the CCAIN input stream.
 
−
 
−
===WEBOPT===
 
−
The new x'10' setting of <var>[[WEBOPT_parameter|WEBOPT]]</var> allows transaction daemon threads to access web data owned by the ancestor ( usually the parent ) thread.
 
−
 
−
==New and changed statistics==
 
−
===MPR, MBO, MCP, and RCV===
 
−
Introduced in zap 77z257.
 
−
<p>These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)</p>
 
−
<p>They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. </p>
 
−
 
−
User/system statistics:
 
−
<ul>
 
−
<li>MPR: High water mark of transaction pre-images. </li>
 
−
<li>MBO: High water mark of transaction backout pages. </li>
 
−
<li>MCP: High water mark of transaction chkpoint spans. </li>
 
−
</ul>
 
−
System statistics:
 
−
<ul>
 
−
<li>RCV: Number of blocks needed for subtransaction recovery </li>
 
−
</ul>
 
−
<p class="note"><b>Notes:</b> M204.0843 now displays the RCV statistic for subtransaction checkpoints.
 
−
The size of recovery checkpoint must be greater than the sum of the last RCV value plus the number of records in [[System_and_media_recovery#RESTART_recovery_considerations_for_sub-transaction_checkpoints|RESTART and RESTARTS]].
 
−
</p>
 
−
 
−
===DKWTS and DKWTMICS===
 
−
Introduced in zap 77z7289.
 
−
<p>The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.</p>
 
−
 
−
DKWTS shows the number of disk I/O waits. DKWTMICS shows the total wait time for those waits in microseconds. Dividing the difference in DKWTMICS by the difference in DKWTS over an interval provides the average disk I/O wait time in microseconds.             
 
−
 
−
<p class="note"><b>Notes:</b>
 
−
<ul>
 
−
<li>The wait time does include internal Model 204 scheduler delays, so on a CPU bound Model 204 system, the service times calculated from DKWTS and DKWTMICS are likely to be an overestimate of actual service times.</li> 
 
−
                                                                   
 
−
<li>DKWTS and DKWTMICS are not available in SirMon; use <var>[[MONITOR_command|MONITOR]] SYSTEM STATISTICS</var> to view these statistics.</li></ul>  </p>
 
−
 
−
==Compatibility issues==
 
−
===<b id="listNewInit"></b>$ListNew cannot be used in Initial clause===
 
−
It is now a compilation error if <var>$ListNew</var> is attempted to 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 is propagated by zap maintenance to versions 7.5 (zap 75Z487), 7.6 (zap 76Z514), and 7.7 (zap 77z281) of Model 204.</p>
 
−
 
−
<blockquote class="note"><b>Note:</b> Strictly speaking, this would not be considered a compilation error, because previously although <code>..&nbsp;Initial($ListNew)</code> did not produce a compilation error, in almost all circumstances it would produce a snap if the initialized %variable were used with some other <var>$List<i>xxx</i></var> invocation.</blockquote>
 
−
 
−
===Restricting the use of the CUSTOM=38 setting===
 
−
The <var>[[CUSTOM parameter|CUSTOM=38]]</var> parameter setting, introduced at V7.5, inadvertently provided System Manager privileges to all users via the <var>RESET</var> command. This <var>CUSTOM</var> setting is now restricted to the <var>RESET</var> of the <var>LAUDIT</var> parameter.
 
−
 
−
===Disabling of Closure support===
 
−
Due to a non-trivial backward incompatibility issue related to Closure support, introduced in V7.7, this feature, which can best be described as exposed methods assigned to method variables, has been disabled in this release. This change was also made to V7.7 with application of zap 77z119.
 
−
 
−
===Password delimiter enforced===
 
−
When using <var>IFSTRTN</var> to log on to a Model 204 online from an IFAM2 application, both the logonid and password must be followed by a semicolon, which is the delimiter. For example:     
 
−
                                     
 
−
<p class="code">CALL IFSTRTN(RC,'logonid;password;'...)</p>
 
−
               
 
−
If a semicolon does not follow the password string, the following message will now be issued:
 
−
 
−
<p class="code">M204.2964: Password missing or too long </p>               
 
−
                                                       
 
−
Previously, a semicolon following the password was not required and the first blank served as a password delimiter.  However, as of V7.7, embedded blanks are valid password characters and a semicolon is now required to delimit the password.
 
−
 
−
This change is enabled in V7.7 with the application of zap 77z231.
 
−
 
−
===PAGESZ parameter validated===
 
−
Previously it was possible to set the <var>PAGESZ</var> parameter to any value, although Model 204 internally supports one page size of 6184, and any deviation from this value would have led to problems during file creation. The value of this parameter is now controlled, such that setting it to any value other than 6184 will generate an M204.1149 message with the parameter being reset to 6184.
 
−
 
−
===ECPRIV and the IDCAMS facility===
 
−
At V7.7 a security loophole was closed, whereby all ECF modules were run under external-authorizer profile of the calling user. Previously any ECF tasks were run under the owning job's external-authorizer profile, and in order for certain sites to retain that ability, a new setting of <var>ECPRIV</var>, value 4, was introduced to retain the ability to run ECF tasks using the job's security profile.
 
−
 
−
The <var>ECPRIV</var> 4 setting potentially introduced a security loophole when calling the IDCAMS interface, based upon what the IDCAMS utility is able to do at a system level. Consequently as of this release, the <var>ECPRIV</var> 4 setting will be ignored when calling the IDCAMS facility via ECF, and such IDCAMS processes will always use the calling user's security profile. Any existing jobs that use ECF to call the IDCAMS utility with the <var>ECFPRIV</var> 4 bit set should be checked to ensure that the calling user's security profile still satisfies the job's requirements.
 
−
 
−
===TCPOPTS is view-only===
 
−
In previous versions the <var>TCPOPTS</var> parameter, which identifies the type of IP addressing in use (v4 or v6), was resettable, although it was always documented as a view-only parameter. The parameter is now handled as a view-only parameter, and any attempts to reset the parameter will result in the following message:
 
−
 
−
<p class="code>  M204.1123: Parameter TCPOPTS not reset</p>
 
−
 
−
===ZHPF command can only be issued by a system manager===
 
−
In previous versions it was possible to issue the <var>ZHPF</var> command without being logged on. From this release onwards, a user must be logged on with system manager privileges in order to issue this command.
 
−
 
−
Additionally, the command output will now only  display results for currently open files.
 
−
 
−
This change is enabled in v7.7 with the application of zap 77z264.
 
−
 
−
===Terminal MODEL reset failure===
 
−
If a reset of the terminal <var>MODEL</var> parameter fails due to an undersized output page buffer, then in addition to the existing messages that inform the user of this failure:
 
−
<p class="code>    M204.1875 UNABLE TO RESET MODEL TO %C
 
−
    M204.1123: Parameter MODEL not reset</p> 
 
−
 
−
the following message will now be issued:
 
−
 
−
<p class="code>    M204.1008: LOUTPB must be increased to at least <number> </p>
 
−
                                                       
 
−
where <number> is the minimum value of <var>LOUTPB</var> necessary to support the terminal model.
 
−
 
−
This change is enabled in V7.7 with the application of zap 77z309.
 
−
 
−
===BUF and FBMX stats removed===
 
−
Unnecessary scans of the buffer pool have been eliminated from most forms of the MONITOR command ( other than MONITOR DISKBUFF itself ), and this provides performance gain when running these commands. However, as a result of this the BUF stat on the MONITOR command output, and the FBMX stat reported in the system final stats block have been removed. These stats were of extremely limited value, and their elimination should not cause any problems for system management. This change is implemented in V7.8 via zap 78z077, and in V7.7 by zap 77z463.
 
−
 
−
==Notes for system manager and installer==
 
−
===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]].
 
−
===Authorization and maintenance zaps===
 
−
When you download Rocket M204 product object files, all relevant authorization keys and all current maintenance zaps are pre-applied to the object files as part of the download process.
 
  
 
==New products==
 
==New products==
−
===Janus Two-Phase Commit===
 
−
[[Janus Two-Phase Commit]] support makes it possible to create global transactions where updates on multiple Model 204 Onlines or <var>Imagine</var> can be atomically committed or backed out.
 
−
 
−
===Commit Exit===
 
−
The [[Application_Subsystem_development#Commit_exits|Commit exit]] product allows for the invocation of specified APSY code when an an APSY TBO transaction executes its first explicit or implicit COMMIT. The feature is controlled by the new COMMITX parameter.
 
  
 
==New and changed messages==
 
==New and changed messages==

Revision as of 04:11, 21 December 2021

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

Overview

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

New in this release

Operating system and hardware requirements

Operating system requirements

System Enhancements

Debugger enhancements

These enhancements apply to the Janus and TN3270 debuggers.


Performance enhancements

New products

New and changed messages

See New and updated messages in Model 204 version 7.9 for details.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.9_(Beta)&oldid=118316"