m204wiki - User contributions [en]

Number (FloatNamedArraylist function)

2020-09-23T15:22:34Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==

b

%y is collection floatNamedArraylist of string len 32
%i is float

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

%i = 38
print %y:number(%y:nameByNumber(%i)) and %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:


2 38 thirty-eight


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:21:50Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==

b

%y is collection floatNamedArraylist of string len 32
%i is float

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

%i = 38
print %y:number(%y:nameByNumber(%i)) and %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:


1 7 seven
2 38 thirty-eight
3 110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:17:32Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==
The following request demonstrates the numerically ordered
result produced by a <var>[[Number (FloatNamedArraylist function)|Number]]</var> loop over a <var>FloatNamedArraylist</var> :
b

%y is collection floatNamedArraylist of string len 32
%i is float

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

for %i from 1 to %y:count
print %y:number(%y:nameByNumber(%i)) and %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:


1 7 seven
2 38 thirty-eight
3 110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:16:56Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==
The following request demonstrates the numerically ordered
result produced by a <var>[[Number (FloatNamedArraylist function)|Number]]</var> loop over a <var>FloatNamedArraylist</var> :
b

%y is collection floatNamedArraylist of string len 32
%i is float

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

for %i from 1 to %y:count
print %y:number(%y:nameByNumber(%i)) and %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:

110 one-hundred-ten
38 thirty-eight
7 seven
-----
7 seven
38 thirty-eight
110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:16:01Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==
The following request demonstrates the numerically ordered
result produced by a <var>[[Number (FloatNamedArraylist function)|Number]]</var> loop over a <var>FloatNamedArraylist</var> :
b

%y is collection floatNamedArraylist of string len 32
%i is float

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

for %i from 1 to %x:count
print %x:nameByNumber(%i) and %x:itemByNumber(%i)
end for

for %i from 1 to %y:count
print %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:

110 one-hundred-ten
38 thirty-eight
7 seven
-----
7 seven
38 thirty-eight
110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:15:27Z

DCameron: /* Examples */

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==
The following request demonstrates the numerically ordered
result produced by a <var>[[Number (FloatNamedArraylist function)|Number]]</var> loop over a <var>FloatNamedArraylist</var> versus the alphabetically ordered result using a <var>NamedArraylist</var>:
b

%x is collection namedArraylist of string len 32
%y is collection floatNamedArraylist of string len 32
%i is float

%x = new
%x(7) = 'seven'
%x(38) = 'thirty-eight'
%x(110) = 'one-hundred-ten'

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

for %i from 1 to %x:count
print %x:nameByNumber(%i) and %x:itemByNumber(%i)
end for

for %i from 1 to %y:count
print %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:

110 one-hundred-ten
38 thirty-eight
7 seven
-----
7 seven
38 thirty-eight
110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Number (FloatNamedArraylist function)

2020-09-23T15:14:56Z

DCameron:

{{Template:FloatNamedArraylist:Number subtitle}}

<var>Number</var> returns the item number (ordinal) of the item that has the specified subscript in the <var>FloatNamedArraylist</var>.

==Syntax==
{{Template:FloatNamedArraylist:Number syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%number</th>
<td>A numeric variable to contain the item number of the <var class="term">fltNal</var> item selected by <var class="term">subscript</var>.</td></tr>
<tr><th>fltNal</th>
<td>A <var>FloatNamedArraylist</var> object. </td></tr>
<tr><th>subscript</th>
<td>A numeric value that serves as a subscript to identify a <var class="term">fltNal</var> item.</td></tr>
</table>

==Usage notes==
<ul>
<li>If <var>Number</var> is called and there is no item on the <var>FloatNamedArraylist</var> that has the indicated <var class="term">subscript</var>, a <code>0</code> is returned, regardless of the setting of <var>[[UseDefault (FloatNamedArraylist property)|UseDefault]]</var>.
</ul>

==Examples==
The following request demonstrates the numerically ordered
result produced by a <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> loop over a <var>FloatNamedArraylist</var> versus the alphabetically ordered result using a <var>NamedArraylist</var>:
b

%x is collection namedArraylist of string len 32
%y is collection floatNamedArraylist of string len 32
%i is float

%x = new
%x(7) = 'seven'
%x(38) = 'thirty-eight'
%x(110) = 'one-hundred-ten'

%y = new
%y(7) = 'seven'
%y(38) = 'thirty-eight'
%y(110) = 'one-hundred-ten'

for %i from 1 to %x:count
print %x:nameByNumber(%i) and %x:itemByNumber(%i)
end for

for %i from 1 to %y:count
print %y:nameByNumber(%i) and %y:itemByNumber(%i)
end for

end


The request prints:

110 one-hundred-ten
38 thirty-eight
7 seven
-----
7 seven
38 thirty-eight
110 one-hundred-ten


==See also==
<ul>
<li>The <var>[[ItemByNumber_(GenericNamedArraylist_property)|ItemByNumber]]</var> property lets you retrieve or set an item using the item's ordinal number.
<li>The <var>[[NameByNumber (FloatNamedArraylist function)|NameByNumber]]</var> function lets you retrieve an item's name using the item's ordinal number.
</ul>

{{Template:FloatNamedArraylist:Number footer}}

Run (Daemon function)

2020-09-16T10:08:52Z

DCameron: /* Examples */

{{Template:Daemon:Run subtitle}}
<var>Run</var> runs on the daemon thread the command, or set of commands, specified by its first argument, and it returns the terminal output from the command(s).

==Syntax==
{{Template:Daemon:Run syntax}}

===Syntax terms===
<table class="syntaxTable">
<tr><th>%sl</th>
<td>If specified, a <var>[[Stringlist class|Stringlist]]</var> object to contain the terminal output from the command, or commands, run on the daemon thread. </td></tr>

<tr><th>daemon</th>
<td>A <var>Daemon</var> object expression. </td></tr>

<tr><th>commands</th>
<td>A string or <var>Stringlist</var> that is the command, or the set of commands, to be executed by the daemon. </td></tr>

<tr><th><var>Input</var></th>
<td>The input object passed to the daemon method object. This optional, [[Methods#Named parameters|name allowed]], argument is passed by deep copy and not by reference, so <var class="term">object</var> must be deep copyable, as described in: [[Copying objects]]. The passed object can be retrieved by the daemon thread using <var>[[GetInputObject (Daemon subroutine)|GetInputObject]]</var>.</td></tr>

<tr><th><var>Output</var></th>
<td>The output object returned from the daemon method object. This optional, name allowed, argument is passed by deep copy and not by reference, so <var class="term">object</var> must be deep copyable. The object set to <var class="term">object</var> is the object passed by the daemon thread using <var>[[ReturnObject (Daemon subroutine)|ReturnObject]]</var>.
Because <var class="term">object</var> is an output variable, it cannot itself be contained inside an object: that is, it must be a local or a common %variable. </td></tr>

<tr><th><var>Info</var></th>
<td>An optional, [[Methods#Named parameters|name required]], parameter that indicates a second output object returned from the daemon method object. This optional argument is passed by deep copy and not by reference, so <var>Info</var> must be deep copyable. The object set to <var>Info</var> is the object passed by the daemon thread using <var>[[ReturnInfoObject (Daemon subroutine)|ReturnInfoObject]]</var>.
Because <var>Info</var> is an output variable, it cannot itself be contained inside an object: that is, it must be a local or a common %variable. 
For an example of how to use this parameter, see the bottom of [[Run (Daemon function)#Usage notes|Usage Notes]], below.</td></tr>
</table>

==Exceptions==
This function can throw the following exception:
<table class="syntaxTable">
<tr><th><var>[[DaemonLost class|DaemonLost]]</var></th>
<td>If the daemon object is lost (probably restarted), a <var>DaemonLost</var> exception is thrown. </td></tr>
</table>

==Usage notes==
<ul>
<li><var>Run</var> sets the output object to Null if the daemon command contains no <var>[[ReturnObject (Daemon subroutine)|ReturnObject]]</var> invocation. Any subsequent master thread references to that object, for example to print it, will cancel the request.

<li>As any Run method input-object argument, an input "parameter object" is passed by deep copy: the parameter object, all objects contained in that object, all objects contained in those objects, and so on are copied and passed to the sdaemon thread.
An example of a category of object that may not be passed to a daemon is a <var class="product">[[Janus Sockets]]</var> <var>[[Socket class|Socket]]</var> object.

<li>If a file you want to open on the daemon is already open on the master thread, the <var>[[Open (Daemon subroutine)|Open]]</var> method lets you open the file with the same privileges it had on the master thread.

<li>As described in [[Daemon class#Working with Daemonobjects|Working with Daemon objects]], <var>Run's</var> <var class="term">commands</var> argument can pass multiple commands to the daemon.
For example, to pass objects of three different classes, as well as float and longstring values to a daemon request, you can create a user class that contains such objects and the appropriate float and longstring values, then pass a "parameter object" of that class, as follows:
class Multivar
public
variable a is object a
variable b is object b
variable c is object c
variable y is float
variable z is longstring
end public
end class
...
%multi is object Multivar
%daem is object daemon
...
%multi = new
%multi:a = %objectA
%multi:b = %objectB
%multi:c = %objectC
%multi:y = 3.1415929
%multi:z = %lstrZ
...
%daem:run('I MYPROC', %Multi)

To make use of the variables passed in the <code>%multi</code> input parameter above:
<ul>

<li>The file containing <code>MYPROC</code> must be open on the daemon from an invocation of <var>Run</var> with a <var class="product">Model 204</var> <var>OPEN</var> command argument or from an invocation of <var>[[Open (Daemon subroutine)|Open]]</var>.
<li>The <code>MYPROC</code> procedure must contain an invocation of <var>[[GetInputObject_(Daemon_subroutine)|GetInputObject]]</var>.
</ul>
To return updated values to the master thread above, <code>MYPROC</code> must contain an invocation of <var>[[ReturnObject (Daemon subroutine)|ReturnObject]]</var>, and the <var>Run</var> invocation requires an additional argument (represented in the <var>Run</var> method syntax by the <var>Output</var> argument), compatible with the <var>ReturnObject</var> argument. [[Daemon_class#A_Daemon_example|A Daemon example]] shows the passing of input and output objects between a master and daemon.
</ul>

==Examples==
<ol><li>These are simple examples of <var>Run</var> calls:
%strlist = %daem:run('V UTABLE')

%strlist = %daem:run(%list2, %x, %x)

<li>In the following example, a daemon sorts found records, then returns in an object the sorted set of records:
begin
%findCriteria is string len 255
%pazuzu is object daemon
%sSorted is object sortedRecordset in file MYFILE
%subList is object stringList
%findCriteria = 'NICKNAME IS LIKE ''SI*'' '

%subList = new
text to %subList
begin
%basicSet is object recordSet in file MYFILE
%sorted is object sortedRecordSet in file MYFILE
%basicSet = New
find records to %basicSet
{%FindCriteria}
end find
sort records in %basicSet to %sorted by NICKNAME
%(daemon):returnObject(%Sorted)
end
end text

%pazuzu = New
%pazuzu:run('*LOWER')
%pazuzu:open('MYFILE')
%pazuzu:run(%subList,,%sSorted)

for each record in %sSorted
print '*'
pai
end for
end

<li>While the optional <var>Info</var> object can be used for any kind of output object, its intent is to separate the "true" output of a daemon request from informational output (return codes, error messages, diagnostics, etc.). In the following example, a <var>Stringlist</var> object (presumably containing error messages) is used as the <var>Info</var> output:
%errors is object stringList
%result is object myClass
%daem is object daemon
...
%daem:run('MYSUBSYS', , %result, info=%errors)

The daemon thread running the request returns the <var>Info</var> object using <var>[[ReturnInfoObject (Daemon subroutine)|ReturnInfoObject]]</var>:
%errors is object stringList
...
%(daemon):returnInfoObject(%errors)
</ol>

==See also==
{{Template:Daemon:Run footer}}

USERPDL command

2020-09-01T14:35:16Z

DCameron: /* Syntax */

The <var>USERPDL</var> command displays a requested user's call stack. This information isn't really useful without access to Model 204 source code so is only likely to be used when communicating with Model 204 support.

==Summary==
<dl>
<dt>Privileges
<dd>System administrator
<dt>Function
<dd>Displays a user's push-down-list (call stack)
</dl>

==Syntax==
USERPDL <var class="term">usernumber</var>

Where:
<table>
<tr>
<tr>
<th>usernumber</th>
<td>The number associated with a particular user. The user must be swapped in for <var>USERPDL</var> to be able to display the user's push-down-list. Swapped out users details can also be accessed from V7.7 with zap 77z509 applied, and from V7.8 with zap 78z073 applied.</td>
</tr>
</table>

[[Category:System administrator commands]]
[[Category:Commands]]

NUMBUFG parameter

2020-08-26T14:49:25Z

DCameron: /* Setting NUMBUFG */

{{Template:NUMBUFG parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>Not resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V7.1</var>
</dl>

==Description==

Allocate this number of buffer pool buffers above the bar (ATB).
<ul>
<li>Prior to version 7.7 of Model 204:

<var>NUMBUFG</var> specifies the number of buffer pool buffers built ATB, while the number of buffer pool buffers built BTB is based on the setting of <var>[[MINBUF parameter|MINBUF]]</var>, <var>[[MAXBUF parameter|MAXBUF]]</var>, and <var>[[SPCORE parameter|SPCORE]]</var>.</li>

<li>As of version 7.7:

If <var>NUMBUFG</var> is specified, no buffer pool buffers are built BTB; all buffers are ATB. Model 204 obtains exactly the <var>NUMBUFG</var> number of buffers. 

In this case, <var>NUMBUFG</var> essentially replaces the BTB parameters: <var>NUMBUF</var> and <var>MINBUF</var> are automatically reset to 0, and <var>MAXBUF</var> and <var>SPCORE</var> are ignored. 
</li>
</ul>

===Setting NUMBUFG===

The maximum number of buffers is <code>2**31/3</code>, or <code>715,827,882</code>, which limits buffer pools to 4.2 terabytes or less.

The minimum number of ATB buffers is: 
[[NLRUQG parameter|NLRUQG]] * (([[NSERVS parameter|NSERVS]] + [[NSUBTKS parameter|NSUBTKS]]) * [[MAXOBUF parameter|MAXOBUF]] + 15)


If you set <var>NUMBUFG</var> to a value lower than the minimum, the value is reset to the calculated value and you receive messages like the following: 
*** M204.2756: NUMBUFG reset to NLRUQG * ((NSERVS + NSUBTKS) * MAXOBUF + 15)
= 1 * ((2+9) * 4 + 15) = 59
*** M204.0075: Initialization completed. Buffers = 0+59

<blockquote class="note">Note:
If you set <var>NUMBUFG</var> greater than 0: 
<ul>
<li>The X'02' bit of the <var>[[XMEMOPT parameter|XMEMOPT]]</var> parameter (the default), must also be set. </li>

<li>The [[File Load utility: FLOD and FILELOAD commands|FLOD and FILELOAD commands]] and [[Fast/Reload]] are not available due to 64-bit addressing conflicts. This particular restriction is removed in V7.7 and later releases.
</ul>
</blockquote>

==See also==
For more information about setting <var>NUMBUFG</var>, see [[Defining the runtime environment (CCAIN)#Using 64-bit addressing and Above the Bar (ATB) storage|Using 64-bit addressing and Above the Bar (ATB) storage]].

[[Category:System parameters]]
[[Category:Parameters]]

BUMPSNAP command

2020-07-29T08:49:40Z

DCameron:

Note: This is a <var class="product">[[Sirius Mods]]</var>-only command prior to Version 7.5 of <var class="product">[[Model 204]]</var>.

The <var>BUMPSNAP</var> command is identical to the <var class="product">Model 204</var> <var>[[BUMP command]]</var>
with the exception that a [[Storing_diagnostic_information_(CCASNAP)|CCASNAP]] is taken for the user or users being BUMPed, if the user is in a BUMPable wait.
When the <var>BUMPSNAP</var> command is issued, the following message is written to [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)|CCAAUDIT/CCAJLOG]] and is printed at the top of each page of CCASNAP:
MSIR.0661: Snap taken, user bumped by BUMPSNAP command
This can be useful in diagnosing a hung user situation where the
error is believed to be a <var class="product">Model 204</var> internals problem.
Whether or not a CCASNAP or SYSMDUMP/VMDUMP is actually taken
depends on many factors, including the settings of the <var>[[SNAPCTL_parameter|SNAPCTL]]</var>
system parameter, the presence of DD cards or FILEDEFs for
CCASNAP or dump datasets, and the setting of <var>[[SNAPLIM_parameter|SNAPLIM]]</var> and the current
number of CCASNAPs already taken.

The syntax of the <var>BUMPSNAP</var> command is identical to that of the BUMP
command.

The <var>BUMPSNAP</var> command, like the <var>BUMP</var> command, allows BUMPing and SNAPping
of more than one user with a single command.
Generally, this is not what is desired with a <var>BUMPSNAP</var> command, so use caution
when issuing a <var>BUMPSNAP</var> command that doesn't specify a user number
(but instead specifies something more generic like a userid or a subsystem name
or file), since this could result in a large number of snap dumps being taken.
For most purposes, the <var>BUMPSNAP</var> command should simply be followed by the
user number of the user for which a snap is desired.

The <var>BUMPSNAP</var> command can be issued as either of these:
<ul>
<li>An operator command,
that is, as a reply to the <var>[[HALT_command|HALT]]</var> message under z/OS
<li>A command typed on the Online virtual console under CMS
</ul>


[[Category:System administrator commands]]
[[Category:Operator commands]]
[[Category:Commands]]

Release notes for Model 204 version 7.8

2020-07-28T14:34:07Z

DCameron: /* WEBOPT */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<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.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-07-28T14:33:14Z

DCameron: /* New and changed parameters */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<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 WEBOPT 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.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

CPTYPE parameter

2020-07-07T13:47:17Z

DCameron: /* Description */

{{Template:CPTYPE parameter subtitle}}

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>Resettable by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var>
</dl>

==Description==
CPTYPE = {0 | 1}


Where: 
<table class="thJustBold">
<tr>
<th>0</th>
<td>Enables transaction checkpoints only.</td>
</tr>
<tr>
<th>1</th>
<td>Enables the use of transaction and sub-transaction checkpoints.</td>
</tr>
</table>


In a <code>CPTYPE=1</code> run, two other significant checkpoint parameters are <var>[[CPTIME parameter|CPTIME]]</var> and <var>[[CPTS parameter|CPTS]]</var>. 

As long as all data sets and parameters are appropriately defined and requirements met within your job, you can reset back and forth between <code>CPTYPE=0</code> and <code>CPTYPE=1</code>. In recovery-only job steps, only set <code>CPTYPE=0</code>, or allow <var>CPTYPE</var> to default. 

The <var>CPTYPE</var> parameter applies to timed checkpoints, meaning those initialized by <var>CPTIME</var>. This parameter is not referenced during <var>[[CHECKPOINT command|CHECKPOINT]]</var> command processing.

If CPTYPE is set to 1, then <var>[[DKUPDTWT_parameter|DKUPDTWT]]</var> must be set to 0.

[[Category:System parameters]]
[[Category:Parameters]]

DKUPDTWT parameter

2020-07-07T13:45:13Z

DCameron: /* Description */

{{Template:DKUPDTWT parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On User 0's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V3.2</var>
</dl>

==Description==
How long disk buffers, containing a file's modified pages, must have aged (in seconds) before they can be written to disk. Even after the write, the pages remain in the buffer pool for future reference until the file is closed by the last user. 
If DKUPDTWT is zero, <var class="product">Model 204</var> writes all of a file's modified pages to disk at the end of the last in-flight update of the file. The user who completed the last in-flight update waits for this disk update process to complete and for the message stating that the disk update is complete.
If DKUPDTWT is nonzero, <var class="product">Model 204</var> delays the start of the disk update process for at least DKUPDTWT seconds, after which it can be the checkpoint pseudo subtask (CHKPST) that performs the disk update. The user who completed the last in-flight update does not have to wait for the disk update process to complete. 
If DKUPDTWT is nonzero, the CHKPST and CHKPTIMR pseudo subtasks are started automatically at <var class="product">Model 204</var> initialization. An error message informs you if the <var>[[NSUBTKS_parameter|NSUBTKS]]</var> parameter is set too low to start these pseudo subtasks.
DKUPDTWT has a maximum of 60, and it also depends on the <var>[[CPTIME_parameter|CPTIME]]</var> parameter setting. If CPTIME is nonzero, DKUPDTWT must be less than or equal to CPTIME*30. 
The system manager can reset DKUPDTWT to zero while the online is running, and to a nonzero value as long as the CHKPST and CHKPTIMR pseudo subtasks were started during <var class="product">Model 204</var> initialization.

If [[Checkpoints:_Storing_before-images_of_changed_pages#Overview_of_sub-transaction_checkpoints|sub-transaction checkpointing]] is activated by setting <var>[[CPTYPE_parameter|CPTYPE]]</var> to 1, then DKUPDTWT must be set to 0
[[Category:System parameters]]
[[Category:Parameters]]

DKUPDTWT parameter

2020-07-07T13:43:10Z

DCameron: /* Description */

{{Template:DKUPDTWT parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>On User 0's parameter line or reset by system manager
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V3.2</var>
</dl>

==Description==
How long disk buffers, containing a file's modified pages, must have aged (in seconds) before they can be written to disk. Even after the write, the pages remain in the buffer pool for future reference until the file is closed by the last user. 
If DKUPDTWT is zero, <var class="product">Model 204</var> writes all of a file's modified pages to disk at the end of the last in-flight update of the file. The user who completed the last in-flight update waits for this disk update process to complete and for the message stating that the disk update is complete.
If DKUPDTWT is nonzero, <var class="product">Model 204</var> delays the start of the disk update process for at least DKUPDTWT seconds, after which it can be the checkpoint pseudo subtask (CHKPST) that performs the disk update. The user who completed the last in-flight update does not have to wait for the disk update process to complete. 
If DKUPDTWT is nonzero, the CHKPST and CHKPTIMR pseudo subtasks are started automatically at <var class="product">Model 204</var> initialization. An error message informs you if the <var>[[NSUBTKS_parameter|NSUBTKS]]</var> parameter is set too low to start these pseudo subtasks.
DKUPDTWT has a maximum of 60, and it also depends on the <var>[[CPTIME_parameter|CPTIME]]</var> parameter setting. If CPTIME is nonzero, DKUPDTWT must be less than or equal to CPTIME*30. 
The system manager can reset DKUPDTWT to zero while the online is running, and to a nonzero value as long as the CHKPST and CHKPTIMR pseudo subtasks were started during <var class="product">Model 204</var> initialization.

If sub-transaction checkpointing is activated by setting <var>[[CPTYPE_parameter|CPTYPE]]</var> to 1, then DKUPDTWT must be set to 0
[[Category:System parameters]]
[[Category:Parameters]]

Release notes for Model 204 version 7.8

2020-07-07T13:23:26Z

DCameron: /* MERGEJ now supports up to 99 input journals */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

ONLINE monitoring

2020-05-20T15:53:21Z

DCameron: /* V7.8 layout change */

You can monitor the status and performance of an ONLINE system, including SNA Communications Server interfaces, with the MONITOR command. See [[MONITOR command]] for complete command syntax.


MONITOR provides a series of formatted or unformatted displays of system and user statistics about all or a selected set of active users. You can update the displays on a periodic basis, but do not update them more frequently than every five seconds. 

==Unformatted displays==

Unformatted displays show all the nonzero cumulative system or user statistics in a format similar to that provided in the journal: 

<ul>
<li> Series of terms appears in name=value format.</li>

<li> Journal header is not displayed.</li>

<li> Each user is identified by user number.</li>

<li> Account name appears at the beginning of the user's display.
</li>
</ul>

==Formatted displays==

Formatted displays show basic system information, followed by specified user information in labelled columns. 


Basic system information includes the number of:

<ul>
<li> Active users (USR)</li>

<li> Active servers (SVR)</li>

<li> Open buffers (BUF)</li>

<li> Open files (FLS) </li>

<li> A file open as part of one or more permanent groups is followed by an asterisk (*).</li>

<li> Two pound signs (##) indicate that the user has more files open than can fit into the internal buffer used to hold open file names.</li>

<li> System percentage of CPU time (PCPU).</li>

<li> Statistics from the last system performance line written to the journal. If performance monitoring is active and performance lines are being written to the journal, all statistics are shown. Otherwise, only open buffers, open files, and system PCPU are shown.
</li>
</ul>


Specified user information is described in the next section.

==User information in formatted displays==

User information is viewable in the following types of formatted displays:

<ul>
<li> Basic display (default)</li>

<li> User since-last statistics</li>

<li> User performance data</li>

<li> Open files
</li>
</ul>


The following sections describe these types of formatted displays.

===Basic display===

USER SVR USERID P CUR SLICE AGE FUNC CNCT CPU SEQIO QUE WT FLGS
0 SAM S 48 0.075 0 0.041 3 BLKO 04 40
1 1 MARY S 49 0.075 EVAL 266 0.152 36 REDY


Where:

<ul>
<li>USER is the user number.</li>
<li>SVR is the server number.</li>
<li>USERID is the user ID.</li>
<li>P is user priority (P).</li>
<li>CUR is current priority.</li>
<li>SLICE is current CPU time slice.</li>
<li>AGE is user pre-aged priority.</li>
<li>FUNC is the last function to set the since-last parameter.</li>
<li>CNCT is connect time.</li>
<li>CPU is CPU time.</li>
<li>SEQIO is the sequential I/O operations performed.</li>
<li>QUE is the [[#QUE values|current scheduler queue]].</li>
<li>WT is the [[#Wait state values|user wait state]].</li>
<li>FLGS is the sum of the [[#Status flag values|status flag values]].</li>
</ul>

====QUE values====
<table>
<tr class="head">
<th>

QUE value 
</th>
<th>

Means user is...
</th>
</tr>

<tr>
<td>

RUNG 
</td>
<td>

Running.
</td>
</tr>

<tr>
<td>

BLKI 
</td>
<td>

Blocked in server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFI 
</td>
<td>

Blocked in server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

BLKO 
</td>
<td>

Blocked out of server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFO 
</td>
<td>

Blocked out of server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

WTSV 
</td>
<td>

Waiting for a server.
</td>
</tr>

<tr>
<td>

REDY 
</td>
<td>

Ready or running.
</td>
</tr>

<tr>
<td>

SWPG 
</td>
<td>

Being swapped in or out.
</td>
</tr>

<tr>
<td>

WTUS 
</td>
<td>

Server waiting for user.
</td>
</tr>

<tr>
<td>

MOVE
</td>
<td>

Moving between queues.
</td>
</tr>
</table>

Tip: As of version 7.7, by summing RUNG, BLKI, BLKO, WTSV, REDY, and SWPG, you can approximate USRS (average active users).

Note: Prior to version 7.7, OFFQ was used instead of OFFI and OFFO.

====Wait type values====
<table>
<tr class="head">
<th>

Wait
</th>
<th>

Description
</th>
</tr>

<tr>
<td>

00
</td>
<td>

Unspecified.
</td>
</tr>

<tr>
<td>

01
</td>
<td>

Disk I/O.
</td>
</tr>

<tr>
<td>
02
</td>
<td>

Sequential user I/O — output.
</td></tr>

<tr>
<td>
03
</td>
<td>

Sequential user I/O — input.
</td></tr>

<tr>
<td>
04
</td>
<td>

Operator's console input (WTOR).
</td></tr>

<tr>
<td>
05
</td>
<td>
Restore reads (BSAM).
</td></tr>

<tr>
<td>

06
</td>
<td>

Dump writes (BSAM). 
</td></tr>

<tr>
<td>
07
</td>
<td>
Enqueue waits (record or noncritical resource).
</td></tr>

<tr>
<td>
08
</td>
<td>

Buffer waits.
</td></tr>

<tr>
<td>
09
</td>
<td>
Wait almost forever (deactivated user).
</td></tr>

<tr>
<td>
10
</td>
<td>
Waits for a pseudo subtask, or waits for reactivation (hung terminal).
</td></tr>

<tr>
<td>
11
</td>
<td>
Waits for an IFAM2 or IFAM4 call.
</td></tr>

<tr>
<td>
12
</td>
<td>
Waits for a wakeup.
</td></tr>

<tr>
<td>
13
</td>
<td>
Server I/O.
</td></tr>

<tr>
<td>
15
</td>
<td>
Writes to the journal data set, CCAJRNL.
</td></tr>

<tr>
<td>
16
</td>
<td>
Checkpoint writes to CHKPOINT data set.
</td></tr>

<tr>
<td>
17
</td>
<td>
Waits for check on previous write.
</td></tr>

<tr>
<td>
18
</td>
<td>
Waits for a checkpoint DECB to free up or waiting for multiuser output arbitration.
</td></tr>

<tr>
<td>
19
</td>
<td>
Waits for a checkpoint request.
</td></tr>

<tr>
<td>
20
</td>
<td>
Waits for a checkpoint completion.
</td></tr>

<tr>
<td>
21
</td>
<td>
Wait forever (dead user).
</td></tr>

<tr>
<td>
22
</td>
<td>
VSAM or sequential file input.
</td></tr>

<tr>
<td>
23
</td>
<td>
User waiting due to excessive login failures.
</td></tr>

<tr>
<td>
24
</td>
<td>
Waits for exclusive control of critical file resource.
</td></tr>

<tr>
<td>
25
</td>
<td>
Waits for share control of critical file resource.
</td></tr>

<tr>
<td>
26
</td>
<td>
Waits for SNA Communications Server buffer, input or output.
</td></tr>

<tr>
<td>
27
</td>
<td>
Waits for interprocess input.
</td></tr>

<tr>
<td>
28
</td>
<td>
Waits for interprocess output.
</td></tr>

<tr>
<td>
29
</td>
<td>
User waiting for the security interface.
</td></tr>

<tr>
<td>
30
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'SWAP')</code>, for a user-defined ECB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
31
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'NOSWAP')</code>, for a user-defined EDB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
32
</td>
<td>
User waiting for DB2 subtask.
</td>
</tr>

<tr>
<td>
33-36
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>
37
</td>
<td>
User waiting for recovery to complete.
</td>
</tr>

<tr>
<td>
38
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

39
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

40
</td>
<td>
Waiting for an MQSeries subtask to become available.
</td>
</tr>

<tr>
<td>

41
</td>
<td>
Waiting for a MQ subtask to run.
</td>
</tr>

<tr>
<td>

42
</td>
<td>
MQSeries MQGET operations with wait time specified.
</td>
</tr>

<tr>
<td>

43
</td>
<td>
ECF to load or delete a module. 
</td>
</tr>

<tr>
<td>
44
</td>
<td>
External module to become free. 
</td>
</tr>

<tr>
<td>
45
</td>
<td>
ECF subtask to become free.
</td>
</tr>

<tr>
<td>
46
</td>
<td>
External module to run.
</td>
</tr>

<tr>
<td>
47
</td>
<td>
User(s) waiting, with <code>$Wait('CPQZ')</code>, for the extended quiesce ECB to be posted by the successful completion of a <var class="product">Model 204</var>, system-wide checkpoint.
</td>
</tr>

<tr>
<td>
48
</td>
<td>
User(s) waiting, with <code>$Wait('QZSIG')</code>, for the end of extended quiesce.
</td></tr>

<tr>
<td>
49
</td>
<td>
User(s) waiting, at end of extended quiesce, for count of <code>$Wait('CPQZ')</code> and <code>$Wait('QZSIG')</code> users to go to zero.
</td></tr>

<tr>
<td>
50
</td>
<td>
User is waiting for HSM to recall an archived data set.
</td></tr>

<tr>
<td>
51
</td>
<td>
User is waiting for a share lock on the internal constraints database. 
The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
52
</td>
<td>

User is waiting for an exclusive lock on the internal constraints database. 

The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
53
</td>
<td>
User is waiting for a subtransaction checkpoint to complete.
</td></tr>

<tr>
<td>
54
</td>
<td>
Checkpoint PST waiting on a blocking file update to complete to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
55
</td>
<td>
Checkpoint PST doing a timed wait to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
56
</td>
<td>
Checkpoint PST waiting on users to complete subtransactions.
</td></tr>

<tr>
<td>
80-89
</td>
<td>
Customer (site-specific) wait types.
</td></tr>

<tr>
<td>
97
</td>
<td>
Waiting for a Fast/Unload request running in a real subtask.
</td></tr>

<tr>
<td>
98
</td>
<td>
In a <var>[[MAXAUSER parameter|MAXAUSER]]</var> wait.
</td></tr>

<tr>
<td>
99
</td>
<td>
Waiting for a <var>[[SIRFACT command|SIRFACT QUIESCE]]</var> to be completed (with a <var>SIRFACT RESUME</var>).
</td></tr>
</table>

====Status flag values====
<table>
<tr class="head">
<th>

Flag
</th>
<th>

Description of wait...
</th>
</tr>

<tr>
<td>

40
</td>
<td>

User's wait is swappable. If another user needs this user's server area, the waiter may be written out.</td>
</tr>

<tr>
<td>20</td>
<td>User is waiting for an internal ECB (that is, the ECB is posted only by <var class="product">Model 204</var>, not by the operating system). This can happen, for example, if the waiting user is waiting to access a record to which someone else is preventing access. </td>
</tr>

<tr>
<td>10</td>
<td>ECB to be posted is of the short form (1 byte in length) and is an internal ECB (posted by M204). </td>
</tr>

<tr>
<td>8</td>
<td>More than one user is allowed to wait for the ECB that this user is waiting for. </td>
</tr>

<tr>
<td>4</td>
<td>User can be bumped.</td>
</tr>

<tr>
<td>2</td>
<td>User can be interrupted with an urgent message.</td>
</tr>

<tr>
<td>1</td>
<td>A time limit was specified for the user's wait. For example, if a waiting user is in a record locking conflict situation, it is a timed wait until the request ends and a record locking conflict message is issued, or an <var>ON</var> unit in the code takes control.</td>
</tr>
</table>

====V7.8 layout change====
From V.8 onwards the AGE column in the basic display output has been replaced with a column, headed log, which shows the logon status of each user, as in the following example


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
>

Possible values that are shown in the LOG column are as follows
<table>
<tr class="head">
<th>Value</th>
<th>Meaning</th>
</tr>
<tr><td>CCA</td><td>CCASTAT userid</td></tr>
<tr><td>ESM</td><td>userid validated by an External Security Manager - ACF2, RACF, or TopSecret</td></tr>
<tr><td>SUB</td><td>Subsystem controlled logon</td></tr>
<tr><td>GST</td><td>Guest - neither logged on via CCASTAT nor by an ESM</td></tr>
<tr><td>PDG</td><td>Logon pending due to errors (e.g. invalid password)</td></tr>
</table>

===User since-last statistics===

User since-last statistics (SL option) show current activity.


If the user is between activities or performing an activity that does not initialize since-last statistics, the display is cumulative.


Statistics displayed are CPU, DKRD, DKWR, UDD, OUT, SLIC, FINDS, RECDS, PCPU, RQTM, SUBSYSTEM, PROC-FILE, PROC, and the pseudo subtask's user ID, account name, and user number. (Refer to the [[#Description of statistics|Statistics with descriptions]] table for statistic definitions, and to [[#Pseudo subtasks|Pseudo subtasks]].) 

===User performance data===

The PERFORMANCE option shows data last written to the journal. The following information is included:

<ul>
<li> Number of samples used to compute percentages</li>

<li> percentage of time the user is in each of the scheduler queues</li>
</ul>


See [[#Priority scheduling|Priority scheduling]].

===Open files===

This display is a list of files a user has open.

==MONITOR examples==

These examples show several variations of the MONITOR command.


The following command specifies a single nonrepeating formatted display of basic information for the system and all active users:

MONITOR


The following command, MONITOR ACTIVE, specifies a single nonrepeating formatted display of basic information for the system and active users, excepting OFFO and OFFI users. (OFFO and OFFI are state-of-queue statuses meaning that the Scheduler does not have to evaluate those users not in the queue. Prior to version 7.7, OFFQ was used instead of OFFO and OFFI.)
The MONITOR ACTIVE command is used to reduce the amount of terminal output.

MONITOR ACTIVE


The following commands specify a display of the cumulative system statistics, which is updated every minute:

MONITOR STATISTICS 60
MONITOR STAT EVERY 60
MONITOR SYSTEM STATISTICS 60


The following command specifies a single display of the cumulative user statistics for users 1, 3, and 5, if they are active:

MONITOR (1,3,5) STATISTICS


The following commands specify a single formatted display of basic system information and basic, since-last, performance, and file information for each active user. Pseudo subtask's user ID, account name, and user number are displayed for SL (since-last) statistics:

MONITOR ALL
MONITOR USERS ALL
MONITOR BASIC SL PERFORMANCE FILE
MONITOR SL FILE PERF


The following commands specify a display of basic formatted information for the system and users 1, 2, 5, and 7, if they are active. The display is repeated continually 75 seconds after it completes. The user must press Enter to display the refreshed version, or enter *CANCEL to terminate the display:

MONITOR (1,2,5,7) 75
MONITOR (1,2,5,7) BASIC EVERY 75


The following command specifies an unformatted display of the following information:

<ul>
<li> Number of active users</li>

<li> Number of compactions of the record locking table</li>

<li> Current number of bytes used in the record locking table</li>

<li> Current high-water mark for the number of bytes used in the record locking table</li>

<li> Current number of headers used in the record locking table</li>

<li> Current high-water mark for the number of headers used in the record locking table</li>

<li> Required LRETBL setting (high-water mark) for the current system load</li>
</ul>

MONITOR ENQ


The following command specifies a formatted display of the number of pages from tables of each file that are currently located in the disk buffers: 

MONITOR DISKBUFF


The following command specifies information about SNA Communications Server's use of output buffers and waits for threads:

MONITOR VTAM


==MONITOR LINK example==


The following command specifies information about a network entity:

MONITOR LINK HEADQTRS


For more information about the MONITOR command for network monitoring, see <var class="product">Model 204</var> Horizon: Intersystem Processing.


In this example, HEADQTRS is the specified network entity for which the Online system operation is being monitored. The following statistics are provided:

 LOCAL ID MAXSES BNDSES IBWTS OBWTS CONVS FLGS TRAN/PROTO
-------- ------ ------ ----- ----- ----- ---- ----------
BOSTACB 4 2 0 0 2 A VTAM/LU62

USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
3 PROCESS1 5 4 BI DENVER OBSOLETE
4 PROCESS1 5 4 BI DENVER


Where:

<ul>
<li> LOCAL ID is the SNA Communications Server ACB name (BOSTACB).</li>

<li> MAXSES is the maximum number of sessions allowed on this link (4).


The limit is established by the SESSIONS parameter of the DEFINE LINK command.

<li> BNDSES indicates the number of currently bound sessions (2).</li>

<li> IBWTS indicates the number of input buffer waits (0) by inbound conversations.


The input buffer availability is controlled by the actual number of input buffers established by the INBUFNO parameter of the DEFINE LINK command. An input buffer is used on the inbound side when a conversation is being established. If IBWTS is high, and you observe delays while opening inbound processes, then increase INBUFNO.</li>

<li> OBWTS indicates the number of output buffer waits (0).


Note: OBWTS is always zero when the communication protocol is
LU 6.2 (output buffers are not used).</li>

<li> CONVS indicates the number of active conversations (2).</li>

<li> FLGS indicates the status of the link status (A). Possible values for FLGS are:

<table class="thJustBold">
<tr><th>A</th> <td>Active</td></tr>

<tr><th>S</th> <td>Stopped</td></tr>

<tr><th>C</th> <td>Closed</td></tr>
</table></li>

<li> TRAN indicates the transport mechanism: SNA Communications Server or terminal (TERM). In this case TRAN is SNA Communications Server. </li>

<li> PROTO indicates the communication protocol (LU 6.2). Possible values for PROTO are:

<table class="thJustBold">
<tr><th>MSTR</th> <td>Master (for TPROCESS)</td></tr>

<tr><th>XFER</th> <td>Transfer (for TPROCESS)</td></tr>

<tr><th>IMS61</th> <td>IMS LU 6.1</td></tr>

<tr><th>LU 6.2</th> <td>LU 6.2 </td></tr>
</table>


The second line of statistics is a detail line for each bound session.

<ul>
<li> USER provides the external user number (3, 4). A blank occurs if a conversation is not active.</li>

<li> PROCESS indicates the process name (PROCESS1). If a conversation is not active, a blank appears.</li>

<li> SENDS indicates the number of physical sends for each conversation
(5, 5).</li>

<li> RECVS indicates the number of physical receives for each conversation
(4, 4).</li>

<li> FLGS indicates the status of the session (BI, BI). The session status flags are:
<table class="thJustBold">
<tr><th>B </th>
<td>bound </td>
</tr>

<tr>
<th>F </th>
<td>first speaker </td>
</tr>

<tr>
<th>I </th>
<td>inbound </td>
</tr>

<tr>
<th>O </th>
<td>outbound </td>
</tr>

<tr>
<th>L </th>
<td>local bid in progress </td>
</tr>

<tr>
<th>R </th>
<td>remote bid accepted </td></tr>
</table></li></ul>

<li> PROCESSGRP provides the process group name (DENVER). In this example, user 3 is running with an OBSOLETE process group: the process group was stopped and a DEFINE PROCESSGROUP command was issued to change the process group definition for subsequent usage. User 4 is running with the most recent version of the process group definition. </li>
</ul>

==MONITOR PROCESSGROUP example==

The following command specifies reports concerning a specific process group:

MONITOR PROCESSGROUP 


In this example, two PROCESSGROUP reports are produced. The first report is for an active conversation. The second report reflects the stopping and redefinition of the active conversation, which is allocated to another conversation (OBSOLETE with the same process name). Until the conversation with the obsolete process group ends, separate reports are produced for each process group to reflect the more current set of attributes.

 MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 A

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 5 4 BI

MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 AX

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI


Where:

<ul>
<li><var>LINKNAME</var> names the associated link (<code>HEADQTRS</code>).</li>

<li><var>REMOTEID</var> provides the Remote LU name (<code>DENVACB</code>).</li>

<li><var>BNDSES</var> indicates the number of bound sessions (2).</li>

<li><var>INCONVS</var> indicates the number of active inbound conversations (1).</li>

<li><var>OTCONVS</var> indicates the number of active outbound conversations (0).</li>

<li><var>FLGS</var> indicates the status of the processgroup (<code>A</code>). The processgroup status flags are:
<table class="thJustBold">
<tr>
<th>A </th>
<td>Active </td>
</tr>

<tr>
<th>S </th>
<td>Stopped </td>
</tr>

<tr>
<th>X </th>
<td>Obsolete </td>
</tr>
</table></li>
</ul>


The second line of statistics is a detail line for each active conversation.

<ul>
<li><var>USER</var> indicates the external user number (4).</li>

<li><var>PROCESS</var> provides the name of the program as it is known to network users (<code>PROCESS1</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (5).</li>

<li><var>RECVS</var> indicates the number of physical receives (4).</li>

<li><var>FLGS</var> indicates the status of the session status (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>
</ul>

==MONITOR PROCESS example==

The following command specifies information about a particular process:

MONITOR PROCESS PROCESS1


In this example, two inbound conversations invoked from PROCESSGROUP DENVER (users 3 and 4) are in progress with the process named <code>PROCESS1</code>. The conversation ID (CID) that was assigned in the SOUL <var>OPEN PROCESS</var> statement is <code>PROGRAM1</code>.

MONITOR PROCESS PROCESS1

USER CID PROCESSGRP STARTED SENDS RECVS FLGS STATE
----- -------- ---------- ----------- ----- ----- ---- ------
3 PROGRAM1 DENVER 88349135723 5 4 BI RECV
4 PROGRAM1 DENVER 88349135803 5 4 BI RECV

<ul>
<li><var>USER</var> indicates the external user number (<code>3</code>, <code>4</code>).</li>

<li><var>CID</var> provides the conversation ID (<code>PROGRAM1</code>).</li>

<li><var>PROCESSGRP</var> indicates the name of the processgroup (<code>DENVER</code>).</li>

<li><var>STARTED</var> provides the Julian date and time the conversation began (<code>88349</code> and <code>13:57:23</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (<code>5</code>, <code>5</code>).</li>

<li><var>RECVS</var> indicates the number of physical receives (<code>4</code>, <code>4</code>).</li>

<li><var>FLGS</var> indicates the status of the session (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>

<li><var>STATE</var> indicates the state of the conversation (<code>RECV</code>). Conversation states can be:

:ACCEPT
:CLOSE
:CONFCLS
:CONFIRM
:CONFSND
:INITIAL
:RECV
:SEND
</li>
</ul>

==MONITOR DISKBUFF example==

You can use the <var>[[MONITOR command: Disk buffers|MONITOR DISKBUFF]]</var> commands to analyze the buffer pool utilizations:

<ul>
<li><var>MONITOR DISKBUFF</var> output shows buffer usage combining above and below the bar buffers.</li>

<li><var>MONITOR DISKBUFFG</var> output shows buffer pool usage for only above the bar buffers.</li>

<li><var>MONITOR DISKBUFFL</var> output shows buffer pool usage for only below the bar buffer usage.</li>
</ul>


Use these commands throughout the day across varied types of daily and event processing to evaluate your buffer allocations.

===Using MONITOR DISKBUFF commands===

You can see the types of pages that are in your buffer pools at any point in time using the <var>MONITOR DISKBUFF</var> command. The output of this command displays the types of pages that are in buffers and how many of each type.

MONITOR DISKBUFF

FILENAME FCT TBLA TBLB TBLC TBLD TBLE TBLX *TOTAL*
-------- --- ------ ------ ------ ------ ------ ------ -------
CCATEMP 0 40 0 0 0 0 0 40
PROC1 1 0 0 0 11 0 0 12
FILETBLX 1 1 10 0 2 0 2 16
TESTZ 1 1 11 0 3 185 0 201
*TOTAL* 3 42 21 0 16 185 2 269


[[Category:System management]]
[[Category:Model 204 operational issues]]

ONLINE monitoring

2020-05-20T15:32:12Z

DCameron: /* V7.8 layout change */

You can monitor the status and performance of an ONLINE system, including SNA Communications Server interfaces, with the MONITOR command. See [[MONITOR command]] for complete command syntax.


MONITOR provides a series of formatted or unformatted displays of system and user statistics about all or a selected set of active users. You can update the displays on a periodic basis, but do not update them more frequently than every five seconds. 

==Unformatted displays==

Unformatted displays show all the nonzero cumulative system or user statistics in a format similar to that provided in the journal: 

<ul>
<li> Series of terms appears in name=value format.</li>

<li> Journal header is not displayed.</li>

<li> Each user is identified by user number.</li>

<li> Account name appears at the beginning of the user's display.
</li>
</ul>

==Formatted displays==

Formatted displays show basic system information, followed by specified user information in labelled columns. 


Basic system information includes the number of:

<ul>
<li> Active users (USR)</li>

<li> Active servers (SVR)</li>

<li> Open buffers (BUF)</li>

<li> Open files (FLS) </li>

<li> A file open as part of one or more permanent groups is followed by an asterisk (*).</li>

<li> Two pound signs (##) indicate that the user has more files open than can fit into the internal buffer used to hold open file names.</li>

<li> System percentage of CPU time (PCPU).</li>

<li> Statistics from the last system performance line written to the journal. If performance monitoring is active and performance lines are being written to the journal, all statistics are shown. Otherwise, only open buffers, open files, and system PCPU are shown.
</li>
</ul>


Specified user information is described in the next section.

==User information in formatted displays==

User information is viewable in the following types of formatted displays:

<ul>
<li> Basic display (default)</li>

<li> User since-last statistics</li>

<li> User performance data</li>

<li> Open files
</li>
</ul>


The following sections describe these types of formatted displays.

===Basic display===

USER SVR USERID P CUR SLICE AGE FUNC CNCT CPU SEQIO QUE WT FLGS
0 SAM S 48 0.075 0 0.041 3 BLKO 04 40
1 1 MARY S 49 0.075 EVAL 266 0.152 36 REDY


Where:

<ul>
<li>USER is the user number.</li>
<li>SVR is the server number.</li>
<li>USERID is the user ID.</li>
<li>P is user priority (P).</li>
<li>CUR is current priority.</li>
<li>SLICE is current CPU time slice.</li>
<li>AGE is user pre-aged priority.</li>
<li>FUNC is the last function to set the since-last parameter.</li>
<li>CNCT is connect time.</li>
<li>CPU is CPU time.</li>
<li>SEQIO is the sequential I/O operations performed.</li>
<li>QUE is the [[#QUE values|current scheduler queue]].</li>
<li>WT is the [[#Wait state values|user wait state]].</li>
<li>FLGS is the sum of the [[#Status flag values|status flag values]].</li>
</ul>

====QUE values====
<table>
<tr class="head">
<th>

QUE value 
</th>
<th>

Means user is...
</th>
</tr>

<tr>
<td>

RUNG 
</td>
<td>

Running.
</td>
</tr>

<tr>
<td>

BLKI 
</td>
<td>

Blocked in server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFI 
</td>
<td>

Blocked in server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

BLKO 
</td>
<td>

Blocked out of server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFO 
</td>
<td>

Blocked out of server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

WTSV 
</td>
<td>

Waiting for a server.
</td>
</tr>

<tr>
<td>

REDY 
</td>
<td>

Ready or running.
</td>
</tr>

<tr>
<td>

SWPG 
</td>
<td>

Being swapped in or out.
</td>
</tr>

<tr>
<td>

WTUS 
</td>
<td>

Server waiting for user.
</td>
</tr>

<tr>
<td>

MOVE
</td>
<td>

Moving between queues.
</td>
</tr>
</table>

Tip: As of version 7.7, by summing RUNG, BLKI, BLKO, WTSV, REDY, and SWPG, you can approximate USRS (average active users).

Note: Prior to version 7.7, OFFQ was used instead of OFFI and OFFO.

====Wait type values====
<table>
<tr class="head">
<th>

Wait
</th>
<th>

Description
</th>
</tr>

<tr>
<td>

00
</td>
<td>

Unspecified.
</td>
</tr>

<tr>
<td>

01
</td>
<td>

Disk I/O.
</td>
</tr>

<tr>
<td>
02
</td>
<td>

Sequential user I/O — output.
</td></tr>

<tr>
<td>
03
</td>
<td>

Sequential user I/O — input.
</td></tr>

<tr>
<td>
04
</td>
<td>

Operator's console input (WTOR).
</td></tr>

<tr>
<td>
05
</td>
<td>
Restore reads (BSAM).
</td></tr>

<tr>
<td>

06
</td>
<td>

Dump writes (BSAM). 
</td></tr>

<tr>
<td>
07
</td>
<td>
Enqueue waits (record or noncritical resource).
</td></tr>

<tr>
<td>
08
</td>
<td>

Buffer waits.
</td></tr>

<tr>
<td>
09
</td>
<td>
Wait almost forever (deactivated user).
</td></tr>

<tr>
<td>
10
</td>
<td>
Waits for a pseudo subtask, or waits for reactivation (hung terminal).
</td></tr>

<tr>
<td>
11
</td>
<td>
Waits for an IFAM2 or IFAM4 call.
</td></tr>

<tr>
<td>
12
</td>
<td>
Waits for a wakeup.
</td></tr>

<tr>
<td>
13
</td>
<td>
Server I/O.
</td></tr>

<tr>
<td>
15
</td>
<td>
Writes to the journal data set, CCAJRNL.
</td></tr>

<tr>
<td>
16
</td>
<td>
Checkpoint writes to CHKPOINT data set.
</td></tr>

<tr>
<td>
17
</td>
<td>
Waits for check on previous write.
</td></tr>

<tr>
<td>
18
</td>
<td>
Waits for a checkpoint DECB to free up or waiting for multiuser output arbitration.
</td></tr>

<tr>
<td>
19
</td>
<td>
Waits for a checkpoint request.
</td></tr>

<tr>
<td>
20
</td>
<td>
Waits for a checkpoint completion.
</td></tr>

<tr>
<td>
21
</td>
<td>
Wait forever (dead user).
</td></tr>

<tr>
<td>
22
</td>
<td>
VSAM or sequential file input.
</td></tr>

<tr>
<td>
23
</td>
<td>
User waiting due to excessive login failures.
</td></tr>

<tr>
<td>
24
</td>
<td>
Waits for exclusive control of critical file resource.
</td></tr>

<tr>
<td>
25
</td>
<td>
Waits for share control of critical file resource.
</td></tr>

<tr>
<td>
26
</td>
<td>
Waits for SNA Communications Server buffer, input or output.
</td></tr>

<tr>
<td>
27
</td>
<td>
Waits for interprocess input.
</td></tr>

<tr>
<td>
28
</td>
<td>
Waits for interprocess output.
</td></tr>

<tr>
<td>
29
</td>
<td>
User waiting for the security interface.
</td></tr>

<tr>
<td>
30
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'SWAP')</code>, for a user-defined ECB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
31
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'NOSWAP')</code>, for a user-defined EDB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
32
</td>
<td>
User waiting for DB2 subtask.
</td>
</tr>

<tr>
<td>
33-36
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>
37
</td>
<td>
User waiting for recovery to complete.
</td>
</tr>

<tr>
<td>
38
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

39
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

40
</td>
<td>
Waiting for an MQSeries subtask to become available.
</td>
</tr>

<tr>
<td>

41
</td>
<td>
Waiting for a MQ subtask to run.
</td>
</tr>

<tr>
<td>

42
</td>
<td>
MQSeries MQGET operations with wait time specified.
</td>
</tr>

<tr>
<td>

43
</td>
<td>
ECF to load or delete a module. 
</td>
</tr>

<tr>
<td>
44
</td>
<td>
External module to become free. 
</td>
</tr>

<tr>
<td>
45
</td>
<td>
ECF subtask to become free.
</td>
</tr>

<tr>
<td>
46
</td>
<td>
External module to run.
</td>
</tr>

<tr>
<td>
47
</td>
<td>
User(s) waiting, with <code>$Wait('CPQZ')</code>, for the extended quiesce ECB to be posted by the successful completion of a <var class="product">Model 204</var>, system-wide checkpoint.
</td>
</tr>

<tr>
<td>
48
</td>
<td>
User(s) waiting, with <code>$Wait('QZSIG')</code>, for the end of extended quiesce.
</td></tr>

<tr>
<td>
49
</td>
<td>
User(s) waiting, at end of extended quiesce, for count of <code>$Wait('CPQZ')</code> and <code>$Wait('QZSIG')</code> users to go to zero.
</td></tr>

<tr>
<td>
50
</td>
<td>
User is waiting for HSM to recall an archived data set.
</td></tr>

<tr>
<td>
51
</td>
<td>
User is waiting for a share lock on the internal constraints database. 
The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
52
</td>
<td>

User is waiting for an exclusive lock on the internal constraints database. 

The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
53
</td>
<td>
User is waiting for a subtransaction checkpoint to complete.
</td></tr>

<tr>
<td>
54
</td>
<td>
Checkpoint PST waiting on a blocking file update to complete to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
55
</td>
<td>
Checkpoint PST doing a timed wait to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
56
</td>
<td>
Checkpoint PST waiting on users to complete subtransactions.
</td></tr>

<tr>
<td>
80-89
</td>
<td>
Customer (site-specific) wait types.
</td></tr>

<tr>
<td>
97
</td>
<td>
Waiting for a Fast/Unload request running in a real subtask.
</td></tr>

<tr>
<td>
98
</td>
<td>
In a <var>[[MAXAUSER parameter|MAXAUSER]]</var> wait.
</td></tr>

<tr>
<td>
99
</td>
<td>
Waiting for a <var>[[SIRFACT command|SIRFACT QUIESCE]]</var> to be completed (with a <var>SIRFACT RESUME</var>).
</td></tr>
</table>

====Status flag values====
<table>
<tr class="head">
<th>

Flag
</th>
<th>

Description of wait...
</th>
</tr>

<tr>
<td>

40
</td>
<td>

User's wait is swappable. If another user needs this user's server area, the waiter may be written out.</td>
</tr>

<tr>
<td>20</td>
<td>User is waiting for an internal ECB (that is, the ECB is posted only by <var class="product">Model 204</var>, not by the operating system). This can happen, for example, if the waiting user is waiting to access a record to which someone else is preventing access. </td>
</tr>

<tr>
<td>10</td>
<td>ECB to be posted is of the short form (1 byte in length) and is an internal ECB (posted by M204). </td>
</tr>

<tr>
<td>8</td>
<td>More than one user is allowed to wait for the ECB that this user is waiting for. </td>
</tr>

<tr>
<td>4</td>
<td>User can be bumped.</td>
</tr>

<tr>
<td>2</td>
<td>User can be interrupted with an urgent message.</td>
</tr>

<tr>
<td>1</td>
<td>A time limit was specified for the user's wait. For example, if a waiting user is in a record locking conflict situation, it is a timed wait until the request ends and a record locking conflict message is issued, or an <var>ON</var> unit in the code takes control.</td>
</tr>
</table>

====V7.8 layout change====
From V.8 onwards the AGE column in the basic display output has been replaced with a column, headed log, which shows the logon status of each user, as in the following example


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
>

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>

===User since-last statistics===

User since-last statistics (SL option) show current activity.


If the user is between activities or performing an activity that does not initialize since-last statistics, the display is cumulative.


Statistics displayed are CPU, DKRD, DKWR, UDD, OUT, SLIC, FINDS, RECDS, PCPU, RQTM, SUBSYSTEM, PROC-FILE, PROC, and the pseudo subtask's user ID, account name, and user number. (Refer to the [[#Description of statistics|Statistics with descriptions]] table for statistic definitions, and to [[#Pseudo subtasks|Pseudo subtasks]].) 

===User performance data===

The PERFORMANCE option shows data last written to the journal. The following information is included:

<ul>
<li> Number of samples used to compute percentages</li>

<li> percentage of time the user is in each of the scheduler queues</li>
</ul>


See [[#Priority scheduling|Priority scheduling]].

===Open files===

This display is a list of files a user has open.

==MONITOR examples==

These examples show several variations of the MONITOR command.


The following command specifies a single nonrepeating formatted display of basic information for the system and all active users:

MONITOR


The following command, MONITOR ACTIVE, specifies a single nonrepeating formatted display of basic information for the system and active users, excepting OFFO and OFFI users. (OFFO and OFFI are state-of-queue statuses meaning that the Scheduler does not have to evaluate those users not in the queue. Prior to version 7.7, OFFQ was used instead of OFFO and OFFI.)
The MONITOR ACTIVE command is used to reduce the amount of terminal output.

MONITOR ACTIVE


The following commands specify a display of the cumulative system statistics, which is updated every minute:

MONITOR STATISTICS 60
MONITOR STAT EVERY 60
MONITOR SYSTEM STATISTICS 60


The following command specifies a single display of the cumulative user statistics for users 1, 3, and 5, if they are active:

MONITOR (1,3,5) STATISTICS


The following commands specify a single formatted display of basic system information and basic, since-last, performance, and file information for each active user. Pseudo subtask's user ID, account name, and user number are displayed for SL (since-last) statistics:

MONITOR ALL
MONITOR USERS ALL
MONITOR BASIC SL PERFORMANCE FILE
MONITOR SL FILE PERF


The following commands specify a display of basic formatted information for the system and users 1, 2, 5, and 7, if they are active. The display is repeated continually 75 seconds after it completes. The user must press Enter to display the refreshed version, or enter *CANCEL to terminate the display:

MONITOR (1,2,5,7) 75
MONITOR (1,2,5,7) BASIC EVERY 75


The following command specifies an unformatted display of the following information:

<ul>
<li> Number of active users</li>

<li> Number of compactions of the record locking table</li>

<li> Current number of bytes used in the record locking table</li>

<li> Current high-water mark for the number of bytes used in the record locking table</li>

<li> Current number of headers used in the record locking table</li>

<li> Current high-water mark for the number of headers used in the record locking table</li>

<li> Required LRETBL setting (high-water mark) for the current system load</li>
</ul>

MONITOR ENQ


The following command specifies a formatted display of the number of pages from tables of each file that are currently located in the disk buffers: 

MONITOR DISKBUFF


The following command specifies information about SNA Communications Server's use of output buffers and waits for threads:

MONITOR VTAM


==MONITOR LINK example==


The following command specifies information about a network entity:

MONITOR LINK HEADQTRS


For more information about the MONITOR command for network monitoring, see <var class="product">Model 204</var> Horizon: Intersystem Processing.


In this example, HEADQTRS is the specified network entity for which the Online system operation is being monitored. The following statistics are provided:

 LOCAL ID MAXSES BNDSES IBWTS OBWTS CONVS FLGS TRAN/PROTO
-------- ------ ------ ----- ----- ----- ---- ----------
BOSTACB 4 2 0 0 2 A VTAM/LU62

USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
3 PROCESS1 5 4 BI DENVER OBSOLETE
4 PROCESS1 5 4 BI DENVER


Where:

<ul>
<li> LOCAL ID is the SNA Communications Server ACB name (BOSTACB).</li>

<li> MAXSES is the maximum number of sessions allowed on this link (4).


The limit is established by the SESSIONS parameter of the DEFINE LINK command.

<li> BNDSES indicates the number of currently bound sessions (2).</li>

<li> IBWTS indicates the number of input buffer waits (0) by inbound conversations.


The input buffer availability is controlled by the actual number of input buffers established by the INBUFNO parameter of the DEFINE LINK command. An input buffer is used on the inbound side when a conversation is being established. If IBWTS is high, and you observe delays while opening inbound processes, then increase INBUFNO.</li>

<li> OBWTS indicates the number of output buffer waits (0).


Note: OBWTS is always zero when the communication protocol is
LU 6.2 (output buffers are not used).</li>

<li> CONVS indicates the number of active conversations (2).</li>

<li> FLGS indicates the status of the link status (A). Possible values for FLGS are:

<table class="thJustBold">
<tr><th>A</th> <td>Active</td></tr>

<tr><th>S</th> <td>Stopped</td></tr>

<tr><th>C</th> <td>Closed</td></tr>
</table></li>

<li> TRAN indicates the transport mechanism: SNA Communications Server or terminal (TERM). In this case TRAN is SNA Communications Server. </li>

<li> PROTO indicates the communication protocol (LU 6.2). Possible values for PROTO are:

<table class="thJustBold">
<tr><th>MSTR</th> <td>Master (for TPROCESS)</td></tr>

<tr><th>XFER</th> <td>Transfer (for TPROCESS)</td></tr>

<tr><th>IMS61</th> <td>IMS LU 6.1</td></tr>

<tr><th>LU 6.2</th> <td>LU 6.2 </td></tr>
</table>


The second line of statistics is a detail line for each bound session.

<ul>
<li> USER provides the external user number (3, 4). A blank occurs if a conversation is not active.</li>

<li> PROCESS indicates the process name (PROCESS1). If a conversation is not active, a blank appears.</li>

<li> SENDS indicates the number of physical sends for each conversation
(5, 5).</li>

<li> RECVS indicates the number of physical receives for each conversation
(4, 4).</li>

<li> FLGS indicates the status of the session (BI, BI). The session status flags are:
<table class="thJustBold">
<tr><th>B </th>
<td>bound </td>
</tr>

<tr>
<th>F </th>
<td>first speaker </td>
</tr>

<tr>
<th>I </th>
<td>inbound </td>
</tr>

<tr>
<th>O </th>
<td>outbound </td>
</tr>

<tr>
<th>L </th>
<td>local bid in progress </td>
</tr>

<tr>
<th>R </th>
<td>remote bid accepted </td></tr>
</table></li></ul>

<li> PROCESSGRP provides the process group name (DENVER). In this example, user 3 is running with an OBSOLETE process group: the process group was stopped and a DEFINE PROCESSGROUP command was issued to change the process group definition for subsequent usage. User 4 is running with the most recent version of the process group definition. </li>
</ul>

==MONITOR PROCESSGROUP example==

The following command specifies reports concerning a specific process group:

MONITOR PROCESSGROUP 


In this example, two PROCESSGROUP reports are produced. The first report is for an active conversation. The second report reflects the stopping and redefinition of the active conversation, which is allocated to another conversation (OBSOLETE with the same process name). Until the conversation with the obsolete process group ends, separate reports are produced for each process group to reflect the more current set of attributes.

 MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 A

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 5 4 BI

MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 AX

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI


Where:

<ul>
<li><var>LINKNAME</var> names the associated link (<code>HEADQTRS</code>).</li>

<li><var>REMOTEID</var> provides the Remote LU name (<code>DENVACB</code>).</li>

<li><var>BNDSES</var> indicates the number of bound sessions (2).</li>

<li><var>INCONVS</var> indicates the number of active inbound conversations (1).</li>

<li><var>OTCONVS</var> indicates the number of active outbound conversations (0).</li>

<li><var>FLGS</var> indicates the status of the processgroup (<code>A</code>). The processgroup status flags are:
<table class="thJustBold">
<tr>
<th>A </th>
<td>Active </td>
</tr>

<tr>
<th>S </th>
<td>Stopped </td>
</tr>

<tr>
<th>X </th>
<td>Obsolete </td>
</tr>
</table></li>
</ul>


The second line of statistics is a detail line for each active conversation.

<ul>
<li><var>USER</var> indicates the external user number (4).</li>

<li><var>PROCESS</var> provides the name of the program as it is known to network users (<code>PROCESS1</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (5).</li>

<li><var>RECVS</var> indicates the number of physical receives (4).</li>

<li><var>FLGS</var> indicates the status of the session status (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>
</ul>

==MONITOR PROCESS example==

The following command specifies information about a particular process:

MONITOR PROCESS PROCESS1


In this example, two inbound conversations invoked from PROCESSGROUP DENVER (users 3 and 4) are in progress with the process named <code>PROCESS1</code>. The conversation ID (CID) that was assigned in the SOUL <var>OPEN PROCESS</var> statement is <code>PROGRAM1</code>.

MONITOR PROCESS PROCESS1

USER CID PROCESSGRP STARTED SENDS RECVS FLGS STATE
----- -------- ---------- ----------- ----- ----- ---- ------
3 PROGRAM1 DENVER 88349135723 5 4 BI RECV
4 PROGRAM1 DENVER 88349135803 5 4 BI RECV

<ul>
<li><var>USER</var> indicates the external user number (<code>3</code>, <code>4</code>).</li>

<li><var>CID</var> provides the conversation ID (<code>PROGRAM1</code>).</li>

<li><var>PROCESSGRP</var> indicates the name of the processgroup (<code>DENVER</code>).</li>

<li><var>STARTED</var> provides the Julian date and time the conversation began (<code>88349</code> and <code>13:57:23</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (<code>5</code>, <code>5</code>).</li>

<li><var>RECVS</var> indicates the number of physical receives (<code>4</code>, <code>4</code>).</li>

<li><var>FLGS</var> indicates the status of the session (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>

<li><var>STATE</var> indicates the state of the conversation (<code>RECV</code>). Conversation states can be:

:ACCEPT
:CLOSE
:CONFCLS
:CONFIRM
:CONFSND
:INITIAL
:RECV
:SEND
</li>
</ul>

==MONITOR DISKBUFF example==

You can use the <var>[[MONITOR command: Disk buffers|MONITOR DISKBUFF]]</var> commands to analyze the buffer pool utilizations:

<ul>
<li><var>MONITOR DISKBUFF</var> output shows buffer usage combining above and below the bar buffers.</li>

<li><var>MONITOR DISKBUFFG</var> output shows buffer pool usage for only above the bar buffers.</li>

<li><var>MONITOR DISKBUFFL</var> output shows buffer pool usage for only below the bar buffer usage.</li>
</ul>


Use these commands throughout the day across varied types of daily and event processing to evaluate your buffer allocations.

===Using MONITOR DISKBUFF commands===

You can see the types of pages that are in your buffer pools at any point in time using the <var>MONITOR DISKBUFF</var> command. The output of this command displays the types of pages that are in buffers and how many of each type.

MONITOR DISKBUFF

FILENAME FCT TBLA TBLB TBLC TBLD TBLE TBLX *TOTAL*
-------- --- ------ ------ ------ ------ ------ ------ -------
CCATEMP 0 40 0 0 0 0 0 40
PROC1 1 0 0 0 11 0 0 12
FILETBLX 1 1 10 0 2 0 2 16
TESTZ 1 1 11 0 3 185 0 201
*TOTAL* 3 42 21 0 16 185 2 269


[[Category:System management]]
[[Category:Model 204 operational issues]]

ONLINE monitoring

2020-05-20T15:31:34Z

DCameron: /* V7.8 layout change */

You can monitor the status and performance of an ONLINE system, including SNA Communications Server interfaces, with the MONITOR command. See [[MONITOR command]] for complete command syntax.


MONITOR provides a series of formatted or unformatted displays of system and user statistics about all or a selected set of active users. You can update the displays on a periodic basis, but do not update them more frequently than every five seconds. 

==Unformatted displays==

Unformatted displays show all the nonzero cumulative system or user statistics in a format similar to that provided in the journal: 

<ul>
<li> Series of terms appears in name=value format.</li>

<li> Journal header is not displayed.</li>

<li> Each user is identified by user number.</li>

<li> Account name appears at the beginning of the user's display.
</li>
</ul>

==Formatted displays==

Formatted displays show basic system information, followed by specified user information in labelled columns. 


Basic system information includes the number of:

<ul>
<li> Active users (USR)</li>

<li> Active servers (SVR)</li>

<li> Open buffers (BUF)</li>

<li> Open files (FLS) </li>

<li> A file open as part of one or more permanent groups is followed by an asterisk (*).</li>

<li> Two pound signs (##) indicate that the user has more files open than can fit into the internal buffer used to hold open file names.</li>

<li> System percentage of CPU time (PCPU).</li>

<li> Statistics from the last system performance line written to the journal. If performance monitoring is active and performance lines are being written to the journal, all statistics are shown. Otherwise, only open buffers, open files, and system PCPU are shown.
</li>
</ul>


Specified user information is described in the next section.

==User information in formatted displays==

User information is viewable in the following types of formatted displays:

<ul>
<li> Basic display (default)</li>

<li> User since-last statistics</li>

<li> User performance data</li>

<li> Open files
</li>
</ul>


The following sections describe these types of formatted displays.

===Basic display===

USER SVR USERID P CUR SLICE AGE FUNC CNCT CPU SEQIO QUE WT FLGS
0 SAM S 48 0.075 0 0.041 3 BLKO 04 40
1 1 MARY S 49 0.075 EVAL 266 0.152 36 REDY


Where:

<ul>
<li>USER is the user number.</li>
<li>SVR is the server number.</li>
<li>USERID is the user ID.</li>
<li>P is user priority (P).</li>
<li>CUR is current priority.</li>
<li>SLICE is current CPU time slice.</li>
<li>AGE is user pre-aged priority.</li>
<li>FUNC is the last function to set the since-last parameter.</li>
<li>CNCT is connect time.</li>
<li>CPU is CPU time.</li>
<li>SEQIO is the sequential I/O operations performed.</li>
<li>QUE is the [[#QUE values|current scheduler queue]].</li>
<li>WT is the [[#Wait state values|user wait state]].</li>
<li>FLGS is the sum of the [[#Status flag values|status flag values]].</li>
</ul>

====QUE values====
<table>
<tr class="head">
<th>

QUE value 
</th>
<th>

Means user is...
</th>
</tr>

<tr>
<td>

RUNG 
</td>
<td>

Running.
</td>
</tr>

<tr>
<td>

BLKI 
</td>
<td>

Blocked in server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFI 
</td>
<td>

Blocked in server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

BLKO 
</td>
<td>

Blocked out of server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFO 
</td>
<td>

Blocked out of server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

WTSV 
</td>
<td>

Waiting for a server.
</td>
</tr>

<tr>
<td>

REDY 
</td>
<td>

Ready or running.
</td>
</tr>

<tr>
<td>

SWPG 
</td>
<td>

Being swapped in or out.
</td>
</tr>

<tr>
<td>

WTUS 
</td>
<td>

Server waiting for user.
</td>
</tr>

<tr>
<td>

MOVE
</td>
<td>

Moving between queues.
</td>
</tr>
</table>

Tip: As of version 7.7, by summing RUNG, BLKI, BLKO, WTSV, REDY, and SWPG, you can approximate USRS (average active users).

Note: Prior to version 7.7, OFFQ was used instead of OFFI and OFFO.

====Wait type values====
<table>
<tr class="head">
<th>

Wait
</th>
<th>

Description
</th>
</tr>

<tr>
<td>

00
</td>
<td>

Unspecified.
</td>
</tr>

<tr>
<td>

01
</td>
<td>

Disk I/O.
</td>
</tr>

<tr>
<td>
02
</td>
<td>

Sequential user I/O — output.
</td></tr>

<tr>
<td>
03
</td>
<td>

Sequential user I/O — input.
</td></tr>

<tr>
<td>
04
</td>
<td>

Operator's console input (WTOR).
</td></tr>

<tr>
<td>
05
</td>
<td>
Restore reads (BSAM).
</td></tr>

<tr>
<td>

06
</td>
<td>

Dump writes (BSAM). 
</td></tr>

<tr>
<td>
07
</td>
<td>
Enqueue waits (record or noncritical resource).
</td></tr>

<tr>
<td>
08
</td>
<td>

Buffer waits.
</td></tr>

<tr>
<td>
09
</td>
<td>
Wait almost forever (deactivated user).
</td></tr>

<tr>
<td>
10
</td>
<td>
Waits for a pseudo subtask, or waits for reactivation (hung terminal).
</td></tr>

<tr>
<td>
11
</td>
<td>
Waits for an IFAM2 or IFAM4 call.
</td></tr>

<tr>
<td>
12
</td>
<td>
Waits for a wakeup.
</td></tr>

<tr>
<td>
13
</td>
<td>
Server I/O.
</td></tr>

<tr>
<td>
15
</td>
<td>
Writes to the journal data set, CCAJRNL.
</td></tr>

<tr>
<td>
16
</td>
<td>
Checkpoint writes to CHKPOINT data set.
</td></tr>

<tr>
<td>
17
</td>
<td>
Waits for check on previous write.
</td></tr>

<tr>
<td>
18
</td>
<td>
Waits for a checkpoint DECB to free up or waiting for multiuser output arbitration.
</td></tr>

<tr>
<td>
19
</td>
<td>
Waits for a checkpoint request.
</td></tr>

<tr>
<td>
20
</td>
<td>
Waits for a checkpoint completion.
</td></tr>

<tr>
<td>
21
</td>
<td>
Wait forever (dead user).
</td></tr>

<tr>
<td>
22
</td>
<td>
VSAM or sequential file input.
</td></tr>

<tr>
<td>
23
</td>
<td>
User waiting due to excessive login failures.
</td></tr>

<tr>
<td>
24
</td>
<td>
Waits for exclusive control of critical file resource.
</td></tr>

<tr>
<td>
25
</td>
<td>
Waits for share control of critical file resource.
</td></tr>

<tr>
<td>
26
</td>
<td>
Waits for SNA Communications Server buffer, input or output.
</td></tr>

<tr>
<td>
27
</td>
<td>
Waits for interprocess input.
</td></tr>

<tr>
<td>
28
</td>
<td>
Waits for interprocess output.
</td></tr>

<tr>
<td>
29
</td>
<td>
User waiting for the security interface.
</td></tr>

<tr>
<td>
30
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'SWAP')</code>, for a user-defined ECB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
31
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'NOSWAP')</code>, for a user-defined EDB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
32
</td>
<td>
User waiting for DB2 subtask.
</td>
</tr>

<tr>
<td>
33-36
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>
37
</td>
<td>
User waiting for recovery to complete.
</td>
</tr>

<tr>
<td>
38
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

39
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

40
</td>
<td>
Waiting for an MQSeries subtask to become available.
</td>
</tr>

<tr>
<td>

41
</td>
<td>
Waiting for a MQ subtask to run.
</td>
</tr>

<tr>
<td>

42
</td>
<td>
MQSeries MQGET operations with wait time specified.
</td>
</tr>

<tr>
<td>

43
</td>
<td>
ECF to load or delete a module. 
</td>
</tr>

<tr>
<td>
44
</td>
<td>
External module to become free. 
</td>
</tr>

<tr>
<td>
45
</td>
<td>
ECF subtask to become free.
</td>
</tr>

<tr>
<td>
46
</td>
<td>
External module to run.
</td>
</tr>

<tr>
<td>
47
</td>
<td>
User(s) waiting, with <code>$Wait('CPQZ')</code>, for the extended quiesce ECB to be posted by the successful completion of a <var class="product">Model 204</var>, system-wide checkpoint.
</td>
</tr>

<tr>
<td>
48
</td>
<td>
User(s) waiting, with <code>$Wait('QZSIG')</code>, for the end of extended quiesce.
</td></tr>

<tr>
<td>
49
</td>
<td>
User(s) waiting, at end of extended quiesce, for count of <code>$Wait('CPQZ')</code> and <code>$Wait('QZSIG')</code> users to go to zero.
</td></tr>

<tr>
<td>
50
</td>
<td>
User is waiting for HSM to recall an archived data set.
</td></tr>

<tr>
<td>
51
</td>
<td>
User is waiting for a share lock on the internal constraints database. 
The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
52
</td>
<td>

User is waiting for an exclusive lock on the internal constraints database. 

The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
53
</td>
<td>
User is waiting for a subtransaction checkpoint to complete.
</td></tr>

<tr>
<td>
54
</td>
<td>
Checkpoint PST waiting on a blocking file update to complete to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
55
</td>
<td>
Checkpoint PST doing a timed wait to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
56
</td>
<td>
Checkpoint PST waiting on users to complete subtransactions.
</td></tr>

<tr>
<td>
80-89
</td>
<td>
Customer (site-specific) wait types.
</td></tr>

<tr>
<td>
97
</td>
<td>
Waiting for a Fast/Unload request running in a real subtask.
</td></tr>

<tr>
<td>
98
</td>
<td>
In a <var>[[MAXAUSER parameter|MAXAUSER]]</var> wait.
</td></tr>

<tr>
<td>
99
</td>
<td>
Waiting for a <var>[[SIRFACT command|SIRFACT QUIESCE]]</var> to be completed (with a <var>SIRFACT RESUME</var>).
</td></tr>
</table>

====Status flag values====
<table>
<tr class="head">
<th>

Flag
</th>
<th>

Description of wait...
</th>
</tr>

<tr>
<td>

40
</td>
<td>

User's wait is swappable. If another user needs this user's server area, the waiter may be written out.</td>
</tr>

<tr>
<td>20</td>
<td>User is waiting for an internal ECB (that is, the ECB is posted only by <var class="product">Model 204</var>, not by the operating system). This can happen, for example, if the waiting user is waiting to access a record to which someone else is preventing access. </td>
</tr>

<tr>
<td>10</td>
<td>ECB to be posted is of the short form (1 byte in length) and is an internal ECB (posted by M204). </td>
</tr>

<tr>
<td>8</td>
<td>More than one user is allowed to wait for the ECB that this user is waiting for. </td>
</tr>

<tr>
<td>4</td>
<td>User can be bumped.</td>
</tr>

<tr>
<td>2</td>
<td>User can be interrupted with an urgent message.</td>
</tr>

<tr>
<td>1</td>
<td>A time limit was specified for the user's wait. For example, if a waiting user is in a record locking conflict situation, it is a timed wait until the request ends and a record locking conflict message is issued, or an <var>ON</var> unit in the code takes control.</td>
</tr>
</table>

====V7.8 layout change====
From V.8 onwards the AGE column in the basic display output has been replaced with a column, headed log, which shows the logon status of each user, as in the following example


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
>

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>

===User since-last statistics===

User since-last statistics (SL option) show current activity.


If the user is between activities or performing an activity that does not initialize since-last statistics, the display is cumulative.


Statistics displayed are CPU, DKRD, DKWR, UDD, OUT, SLIC, FINDS, RECDS, PCPU, RQTM, SUBSYSTEM, PROC-FILE, PROC, and the pseudo subtask's user ID, account name, and user number. (Refer to the [[#Description of statistics|Statistics with descriptions]] table for statistic definitions, and to [[#Pseudo subtasks|Pseudo subtasks]].) 

===User performance data===

The PERFORMANCE option shows data last written to the journal. The following information is included:

<ul>
<li> Number of samples used to compute percentages</li>

<li> percentage of time the user is in each of the scheduler queues</li>
</ul>


See [[#Priority scheduling|Priority scheduling]].

===Open files===

This display is a list of files a user has open.

==MONITOR examples==

These examples show several variations of the MONITOR command.


The following command specifies a single nonrepeating formatted display of basic information for the system and all active users:

MONITOR


The following command, MONITOR ACTIVE, specifies a single nonrepeating formatted display of basic information for the system and active users, excepting OFFO and OFFI users. (OFFO and OFFI are state-of-queue statuses meaning that the Scheduler does not have to evaluate those users not in the queue. Prior to version 7.7, OFFQ was used instead of OFFO and OFFI.)
The MONITOR ACTIVE command is used to reduce the amount of terminal output.

MONITOR ACTIVE


The following commands specify a display of the cumulative system statistics, which is updated every minute:

MONITOR STATISTICS 60
MONITOR STAT EVERY 60
MONITOR SYSTEM STATISTICS 60


The following command specifies a single display of the cumulative user statistics for users 1, 3, and 5, if they are active:

MONITOR (1,3,5) STATISTICS


The following commands specify a single formatted display of basic system information and basic, since-last, performance, and file information for each active user. Pseudo subtask's user ID, account name, and user number are displayed for SL (since-last) statistics:

MONITOR ALL
MONITOR USERS ALL
MONITOR BASIC SL PERFORMANCE FILE
MONITOR SL FILE PERF


The following commands specify a display of basic formatted information for the system and users 1, 2, 5, and 7, if they are active. The display is repeated continually 75 seconds after it completes. The user must press Enter to display the refreshed version, or enter *CANCEL to terminate the display:

MONITOR (1,2,5,7) 75
MONITOR (1,2,5,7) BASIC EVERY 75


The following command specifies an unformatted display of the following information:

<ul>
<li> Number of active users</li>

<li> Number of compactions of the record locking table</li>

<li> Current number of bytes used in the record locking table</li>

<li> Current high-water mark for the number of bytes used in the record locking table</li>

<li> Current number of headers used in the record locking table</li>

<li> Current high-water mark for the number of headers used in the record locking table</li>

<li> Required LRETBL setting (high-water mark) for the current system load</li>
</ul>

MONITOR ENQ


The following command specifies a formatted display of the number of pages from tables of each file that are currently located in the disk buffers: 

MONITOR DISKBUFF


The following command specifies information about SNA Communications Server's use of output buffers and waits for threads:

MONITOR VTAM


==MONITOR LINK example==


The following command specifies information about a network entity:

MONITOR LINK HEADQTRS


For more information about the MONITOR command for network monitoring, see <var class="product">Model 204</var> Horizon: Intersystem Processing.


In this example, HEADQTRS is the specified network entity for which the Online system operation is being monitored. The following statistics are provided:

 LOCAL ID MAXSES BNDSES IBWTS OBWTS CONVS FLGS TRAN/PROTO
-------- ------ ------ ----- ----- ----- ---- ----------
BOSTACB 4 2 0 0 2 A VTAM/LU62

USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
3 PROCESS1 5 4 BI DENVER OBSOLETE
4 PROCESS1 5 4 BI DENVER


Where:

<ul>
<li> LOCAL ID is the SNA Communications Server ACB name (BOSTACB).</li>

<li> MAXSES is the maximum number of sessions allowed on this link (4).


The limit is established by the SESSIONS parameter of the DEFINE LINK command.

<li> BNDSES indicates the number of currently bound sessions (2).</li>

<li> IBWTS indicates the number of input buffer waits (0) by inbound conversations.


The input buffer availability is controlled by the actual number of input buffers established by the INBUFNO parameter of the DEFINE LINK command. An input buffer is used on the inbound side when a conversation is being established. If IBWTS is high, and you observe delays while opening inbound processes, then increase INBUFNO.</li>

<li> OBWTS indicates the number of output buffer waits (0).


Note: OBWTS is always zero when the communication protocol is
LU 6.2 (output buffers are not used).</li>

<li> CONVS indicates the number of active conversations (2).</li>

<li> FLGS indicates the status of the link status (A). Possible values for FLGS are:

<table class="thJustBold">
<tr><th>A</th> <td>Active</td></tr>

<tr><th>S</th> <td>Stopped</td></tr>

<tr><th>C</th> <td>Closed</td></tr>
</table></li>

<li> TRAN indicates the transport mechanism: SNA Communications Server or terminal (TERM). In this case TRAN is SNA Communications Server. </li>

<li> PROTO indicates the communication protocol (LU 6.2). Possible values for PROTO are:

<table class="thJustBold">
<tr><th>MSTR</th> <td>Master (for TPROCESS)</td></tr>

<tr><th>XFER</th> <td>Transfer (for TPROCESS)</td></tr>

<tr><th>IMS61</th> <td>IMS LU 6.1</td></tr>

<tr><th>LU 6.2</th> <td>LU 6.2 </td></tr>
</table>


The second line of statistics is a detail line for each bound session.

<ul>
<li> USER provides the external user number (3, 4). A blank occurs if a conversation is not active.</li>

<li> PROCESS indicates the process name (PROCESS1). If a conversation is not active, a blank appears.</li>

<li> SENDS indicates the number of physical sends for each conversation
(5, 5).</li>

<li> RECVS indicates the number of physical receives for each conversation
(4, 4).</li>

<li> FLGS indicates the status of the session (BI, BI). The session status flags are:
<table class="thJustBold">
<tr><th>B </th>
<td>bound </td>
</tr>

<tr>
<th>F </th>
<td>first speaker </td>
</tr>

<tr>
<th>I </th>
<td>inbound </td>
</tr>

<tr>
<th>O </th>
<td>outbound </td>
</tr>

<tr>
<th>L </th>
<td>local bid in progress </td>
</tr>

<tr>
<th>R </th>
<td>remote bid accepted </td></tr>
</table></li></ul>

<li> PROCESSGRP provides the process group name (DENVER). In this example, user 3 is running with an OBSOLETE process group: the process group was stopped and a DEFINE PROCESSGROUP command was issued to change the process group definition for subsequent usage. User 4 is running with the most recent version of the process group definition. </li>
</ul>

==MONITOR PROCESSGROUP example==

The following command specifies reports concerning a specific process group:

MONITOR PROCESSGROUP 


In this example, two PROCESSGROUP reports are produced. The first report is for an active conversation. The second report reflects the stopping and redefinition of the active conversation, which is allocated to another conversation (OBSOLETE with the same process name). Until the conversation with the obsolete process group ends, separate reports are produced for each process group to reflect the more current set of attributes.

 MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 A

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 5 4 BI

MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 AX

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI


Where:

<ul>
<li><var>LINKNAME</var> names the associated link (<code>HEADQTRS</code>).</li>

<li><var>REMOTEID</var> provides the Remote LU name (<code>DENVACB</code>).</li>

<li><var>BNDSES</var> indicates the number of bound sessions (2).</li>

<li><var>INCONVS</var> indicates the number of active inbound conversations (1).</li>

<li><var>OTCONVS</var> indicates the number of active outbound conversations (0).</li>

<li><var>FLGS</var> indicates the status of the processgroup (<code>A</code>). The processgroup status flags are:
<table class="thJustBold">
<tr>
<th>A </th>
<td>Active </td>
</tr>

<tr>
<th>S </th>
<td>Stopped </td>
</tr>

<tr>
<th>X </th>
<td>Obsolete </td>
</tr>
</table></li>
</ul>


The second line of statistics is a detail line for each active conversation.

<ul>
<li><var>USER</var> indicates the external user number (4).</li>

<li><var>PROCESS</var> provides the name of the program as it is known to network users (<code>PROCESS1</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (5).</li>

<li><var>RECVS</var> indicates the number of physical receives (4).</li>

<li><var>FLGS</var> indicates the status of the session status (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>
</ul>

==MONITOR PROCESS example==

The following command specifies information about a particular process:

MONITOR PROCESS PROCESS1


In this example, two inbound conversations invoked from PROCESSGROUP DENVER (users 3 and 4) are in progress with the process named <code>PROCESS1</code>. The conversation ID (CID) that was assigned in the SOUL <var>OPEN PROCESS</var> statement is <code>PROGRAM1</code>.

MONITOR PROCESS PROCESS1

USER CID PROCESSGRP STARTED SENDS RECVS FLGS STATE
----- -------- ---------- ----------- ----- ----- ---- ------
3 PROGRAM1 DENVER 88349135723 5 4 BI RECV
4 PROGRAM1 DENVER 88349135803 5 4 BI RECV

<ul>
<li><var>USER</var> indicates the external user number (<code>3</code>, <code>4</code>).</li>

<li><var>CID</var> provides the conversation ID (<code>PROGRAM1</code>).</li>

<li><var>PROCESSGRP</var> indicates the name of the processgroup (<code>DENVER</code>).</li>

<li><var>STARTED</var> provides the Julian date and time the conversation began (<code>88349</code> and <code>13:57:23</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (<code>5</code>, <code>5</code>).</li>

<li><var>RECVS</var> indicates the number of physical receives (<code>4</code>, <code>4</code>).</li>

<li><var>FLGS</var> indicates the status of the session (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>

<li><var>STATE</var> indicates the state of the conversation (<code>RECV</code>). Conversation states can be:

:ACCEPT
:CLOSE
:CONFCLS
:CONFIRM
:CONFSND
:INITIAL
:RECV
:SEND
</li>
</ul>

==MONITOR DISKBUFF example==

You can use the <var>[[MONITOR command: Disk buffers|MONITOR DISKBUFF]]</var> commands to analyze the buffer pool utilizations:

<ul>
<li><var>MONITOR DISKBUFF</var> output shows buffer usage combining above and below the bar buffers.</li>

<li><var>MONITOR DISKBUFFG</var> output shows buffer pool usage for only above the bar buffers.</li>

<li><var>MONITOR DISKBUFFL</var> output shows buffer pool usage for only below the bar buffer usage.</li>
</ul>


Use these commands throughout the day across varied types of daily and event processing to evaluate your buffer allocations.

===Using MONITOR DISKBUFF commands===

You can see the types of pages that are in your buffer pools at any point in time using the <var>MONITOR DISKBUFF</var> command. The output of this command displays the types of pages that are in buffers and how many of each type.

MONITOR DISKBUFF

FILENAME FCT TBLA TBLB TBLC TBLD TBLE TBLX *TOTAL*
-------- --- ------ ------ ------ ------ ------ ------ -------
CCATEMP 0 40 0 0 0 0 0 40
PROC1 1 0 0 0 11 0 0 12
FILETBLX 1 1 10 0 2 0 2 16
TESTZ 1 1 11 0 3 185 0 201
*TOTAL* 3 42 21 0 16 185 2 269


[[Category:System management]]
[[Category:Model 204 operational issues]]

ONLINE monitoring

2020-05-20T15:28:32Z

DCameron: /* V7.8 layout change */

You can monitor the status and performance of an ONLINE system, including SNA Communications Server interfaces, with the MONITOR command. See [[MONITOR command]] for complete command syntax.


MONITOR provides a series of formatted or unformatted displays of system and user statistics about all or a selected set of active users. You can update the displays on a periodic basis, but do not update them more frequently than every five seconds. 

==Unformatted displays==

Unformatted displays show all the nonzero cumulative system or user statistics in a format similar to that provided in the journal: 

<ul>
<li> Series of terms appears in name=value format.</li>

<li> Journal header is not displayed.</li>

<li> Each user is identified by user number.</li>

<li> Account name appears at the beginning of the user's display.
</li>
</ul>

==Formatted displays==

Formatted displays show basic system information, followed by specified user information in labelled columns. 


Basic system information includes the number of:

<ul>
<li> Active users (USR)</li>

<li> Active servers (SVR)</li>

<li> Open buffers (BUF)</li>

<li> Open files (FLS) </li>

<li> A file open as part of one or more permanent groups is followed by an asterisk (*).</li>

<li> Two pound signs (##) indicate that the user has more files open than can fit into the internal buffer used to hold open file names.</li>

<li> System percentage of CPU time (PCPU).</li>

<li> Statistics from the last system performance line written to the journal. If performance monitoring is active and performance lines are being written to the journal, all statistics are shown. Otherwise, only open buffers, open files, and system PCPU are shown.
</li>
</ul>


Specified user information is described in the next section.

==User information in formatted displays==

User information is viewable in the following types of formatted displays:

<ul>
<li> Basic display (default)</li>

<li> User since-last statistics</li>

<li> User performance data</li>

<li> Open files
</li>
</ul>


The following sections describe these types of formatted displays.

===Basic display===

USER SVR USERID P CUR SLICE AGE FUNC CNCT CPU SEQIO QUE WT FLGS
0 SAM S 48 0.075 0 0.041 3 BLKO 04 40
1 1 MARY S 49 0.075 EVAL 266 0.152 36 REDY


Where:

<ul>
<li>USER is the user number.</li>
<li>SVR is the server number.</li>
<li>USERID is the user ID.</li>
<li>P is user priority (P).</li>
<li>CUR is current priority.</li>
<li>SLICE is current CPU time slice.</li>
<li>AGE is user pre-aged priority.</li>
<li>FUNC is the last function to set the since-last parameter.</li>
<li>CNCT is connect time.</li>
<li>CPU is CPU time.</li>
<li>SEQIO is the sequential I/O operations performed.</li>
<li>QUE is the [[#QUE values|current scheduler queue]].</li>
<li>WT is the [[#Wait state values|user wait state]].</li>
<li>FLGS is the sum of the [[#Status flag values|status flag values]].</li>
</ul>

====QUE values====
<table>
<tr class="head">
<th>

QUE value 
</th>
<th>

Means user is...
</th>
</tr>

<tr>
<td>

RUNG 
</td>
<td>

Running.
</td>
</tr>

<tr>
<td>

BLKI 
</td>
<td>

Blocked in server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFI 
</td>
<td>

Blocked in server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

BLKO 
</td>
<td>

Blocked out of server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFO 
</td>
<td>

Blocked out of server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

WTSV 
</td>
<td>

Waiting for a server.
</td>
</tr>

<tr>
<td>

REDY 
</td>
<td>

Ready or running.
</td>
</tr>

<tr>
<td>

SWPG 
</td>
<td>

Being swapped in or out.
</td>
</tr>

<tr>
<td>

WTUS 
</td>
<td>

Server waiting for user.
</td>
</tr>

<tr>
<td>

MOVE
</td>
<td>

Moving between queues.
</td>
</tr>
</table>

Tip: As of version 7.7, by summing RUNG, BLKI, BLKO, WTSV, REDY, and SWPG, you can approximate USRS (average active users).

Note: Prior to version 7.7, OFFQ was used instead of OFFI and OFFO.

====Wait type values====
<table>
<tr class="head">
<th>

Wait
</th>
<th>

Description
</th>
</tr>

<tr>
<td>

00
</td>
<td>

Unspecified.
</td>
</tr>

<tr>
<td>

01
</td>
<td>

Disk I/O.
</td>
</tr>

<tr>
<td>
02
</td>
<td>

Sequential user I/O — output.
</td></tr>

<tr>
<td>
03
</td>
<td>

Sequential user I/O — input.
</td></tr>

<tr>
<td>
04
</td>
<td>

Operator's console input (WTOR).
</td></tr>

<tr>
<td>
05
</td>
<td>
Restore reads (BSAM).
</td></tr>

<tr>
<td>

06
</td>
<td>

Dump writes (BSAM). 
</td></tr>

<tr>
<td>
07
</td>
<td>
Enqueue waits (record or noncritical resource).
</td></tr>

<tr>
<td>
08
</td>
<td>

Buffer waits.
</td></tr>

<tr>
<td>
09
</td>
<td>
Wait almost forever (deactivated user).
</td></tr>

<tr>
<td>
10
</td>
<td>
Waits for a pseudo subtask, or waits for reactivation (hung terminal).
</td></tr>

<tr>
<td>
11
</td>
<td>
Waits for an IFAM2 or IFAM4 call.
</td></tr>

<tr>
<td>
12
</td>
<td>
Waits for a wakeup.
</td></tr>

<tr>
<td>
13
</td>
<td>
Server I/O.
</td></tr>

<tr>
<td>
15
</td>
<td>
Writes to the journal data set, CCAJRNL.
</td></tr>

<tr>
<td>
16
</td>
<td>
Checkpoint writes to CHKPOINT data set.
</td></tr>

<tr>
<td>
17
</td>
<td>
Waits for check on previous write.
</td></tr>

<tr>
<td>
18
</td>
<td>
Waits for a checkpoint DECB to free up or waiting for multiuser output arbitration.
</td></tr>

<tr>
<td>
19
</td>
<td>
Waits for a checkpoint request.
</td></tr>

<tr>
<td>
20
</td>
<td>
Waits for a checkpoint completion.
</td></tr>

<tr>
<td>
21
</td>
<td>
Wait forever (dead user).
</td></tr>

<tr>
<td>
22
</td>
<td>
VSAM or sequential file input.
</td></tr>

<tr>
<td>
23
</td>
<td>
User waiting due to excessive login failures.
</td></tr>

<tr>
<td>
24
</td>
<td>
Waits for exclusive control of critical file resource.
</td></tr>

<tr>
<td>
25
</td>
<td>
Waits for share control of critical file resource.
</td></tr>

<tr>
<td>
26
</td>
<td>
Waits for SNA Communications Server buffer, input or output.
</td></tr>

<tr>
<td>
27
</td>
<td>
Waits for interprocess input.
</td></tr>

<tr>
<td>
28
</td>
<td>
Waits for interprocess output.
</td></tr>

<tr>
<td>
29
</td>
<td>
User waiting for the security interface.
</td></tr>

<tr>
<td>
30
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'SWAP')</code>, for a user-defined ECB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
31
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'NOSWAP')</code>, for a user-defined EDB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
32
</td>
<td>
User waiting for DB2 subtask.
</td>
</tr>

<tr>
<td>
33-36
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>
37
</td>
<td>
User waiting for recovery to complete.
</td>
</tr>

<tr>
<td>
38
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

39
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

40
</td>
<td>
Waiting for an MQSeries subtask to become available.
</td>
</tr>

<tr>
<td>

41
</td>
<td>
Waiting for a MQ subtask to run.
</td>
</tr>

<tr>
<td>

42
</td>
<td>
MQSeries MQGET operations with wait time specified.
</td>
</tr>

<tr>
<td>

43
</td>
<td>
ECF to load or delete a module. 
</td>
</tr>

<tr>
<td>
44
</td>
<td>
External module to become free. 
</td>
</tr>

<tr>
<td>
45
</td>
<td>
ECF subtask to become free.
</td>
</tr>

<tr>
<td>
46
</td>
<td>
External module to run.
</td>
</tr>

<tr>
<td>
47
</td>
<td>
User(s) waiting, with <code>$Wait('CPQZ')</code>, for the extended quiesce ECB to be posted by the successful completion of a <var class="product">Model 204</var>, system-wide checkpoint.
</td>
</tr>

<tr>
<td>
48
</td>
<td>
User(s) waiting, with <code>$Wait('QZSIG')</code>, for the end of extended quiesce.
</td></tr>

<tr>
<td>
49
</td>
<td>
User(s) waiting, at end of extended quiesce, for count of <code>$Wait('CPQZ')</code> and <code>$Wait('QZSIG')</code> users to go to zero.
</td></tr>

<tr>
<td>
50
</td>
<td>
User is waiting for HSM to recall an archived data set.
</td></tr>

<tr>
<td>
51
</td>
<td>
User is waiting for a share lock on the internal constraints database. 
The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
52
</td>
<td>

User is waiting for an exclusive lock on the internal constraints database. 

The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
53
</td>
<td>
User is waiting for a subtransaction checkpoint to complete.
</td></tr>

<tr>
<td>
54
</td>
<td>
Checkpoint PST waiting on a blocking file update to complete to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
55
</td>
<td>
Checkpoint PST doing a timed wait to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
56
</td>
<td>
Checkpoint PST waiting on users to complete subtransactions.
</td></tr>

<tr>
<td>
80-89
</td>
<td>
Customer (site-specific) wait types.
</td></tr>

<tr>
<td>
97
</td>
<td>
Waiting for a Fast/Unload request running in a real subtask.
</td></tr>

<tr>
<td>
98
</td>
<td>
In a <var>[[MAXAUSER parameter|MAXAUSER]]</var> wait.
</td></tr>

<tr>
<td>
99
</td>
<td>
Waiting for a <var>[[SIRFACT command|SIRFACT QUIESCE]]</var> to be completed (with a <var>SIRFACT RESUME</var>).
</td></tr>
</table>

====Status flag values====
<table>
<tr class="head">
<th>

Flag
</th>
<th>

Description of wait...
</th>
</tr>

<tr>
<td>

40
</td>
<td>

User's wait is swappable. If another user needs this user's server area, the waiter may be written out.</td>
</tr>

<tr>
<td>20</td>
<td>User is waiting for an internal ECB (that is, the ECB is posted only by <var class="product">Model 204</var>, not by the operating system). This can happen, for example, if the waiting user is waiting to access a record to which someone else is preventing access. </td>
</tr>

<tr>
<td>10</td>
<td>ECB to be posted is of the short form (1 byte in length) and is an internal ECB (posted by M204). </td>
</tr>

<tr>
<td>8</td>
<td>More than one user is allowed to wait for the ECB that this user is waiting for. </td>
</tr>

<tr>
<td>4</td>
<td>User can be bumped.</td>
</tr>

<tr>
<td>2</td>
<td>User can be interrupted with an urgent message.</td>
</tr>

<tr>
<td>1</td>
<td>A time limit was specified for the user's wait. For example, if a waiting user is in a record locking conflict situation, it is a timed wait until the request ends and a record locking conflict message is issued, or an <var>ON</var> unit in the code takes control.</td>
</tr>
</table>

====V7.8 layout change====
From V

===User since-last statistics===

User since-last statistics (SL option) show current activity.


If the user is between activities or performing an activity that does not initialize since-last statistics, the display is cumulative.


Statistics displayed are CPU, DKRD, DKWR, UDD, OUT, SLIC, FINDS, RECDS, PCPU, RQTM, SUBSYSTEM, PROC-FILE, PROC, and the pseudo subtask's user ID, account name, and user number. (Refer to the [[#Description of statistics|Statistics with descriptions]] table for statistic definitions, and to [[#Pseudo subtasks|Pseudo subtasks]].) 

===User performance data===

The PERFORMANCE option shows data last written to the journal. The following information is included:

<ul>
<li> Number of samples used to compute percentages</li>

<li> percentage of time the user is in each of the scheduler queues</li>
</ul>


See [[#Priority scheduling|Priority scheduling]].

===Open files===

This display is a list of files a user has open.

==MONITOR examples==

These examples show several variations of the MONITOR command.


The following command specifies a single nonrepeating formatted display of basic information for the system and all active users:

MONITOR


The following command, MONITOR ACTIVE, specifies a single nonrepeating formatted display of basic information for the system and active users, excepting OFFO and OFFI users. (OFFO and OFFI are state-of-queue statuses meaning that the Scheduler does not have to evaluate those users not in the queue. Prior to version 7.7, OFFQ was used instead of OFFO and OFFI.)
The MONITOR ACTIVE command is used to reduce the amount of terminal output.

MONITOR ACTIVE


The following commands specify a display of the cumulative system statistics, which is updated every minute:

MONITOR STATISTICS 60
MONITOR STAT EVERY 60
MONITOR SYSTEM STATISTICS 60


The following command specifies a single display of the cumulative user statistics for users 1, 3, and 5, if they are active:

MONITOR (1,3,5) STATISTICS


The following commands specify a single formatted display of basic system information and basic, since-last, performance, and file information for each active user. Pseudo subtask's user ID, account name, and user number are displayed for SL (since-last) statistics:

MONITOR ALL
MONITOR USERS ALL
MONITOR BASIC SL PERFORMANCE FILE
MONITOR SL FILE PERF


The following commands specify a display of basic formatted information for the system and users 1, 2, 5, and 7, if they are active. The display is repeated continually 75 seconds after it completes. The user must press Enter to display the refreshed version, or enter *CANCEL to terminate the display:

MONITOR (1,2,5,7) 75
MONITOR (1,2,5,7) BASIC EVERY 75


The following command specifies an unformatted display of the following information:

<ul>
<li> Number of active users</li>

<li> Number of compactions of the record locking table</li>

<li> Current number of bytes used in the record locking table</li>

<li> Current high-water mark for the number of bytes used in the record locking table</li>

<li> Current number of headers used in the record locking table</li>

<li> Current high-water mark for the number of headers used in the record locking table</li>

<li> Required LRETBL setting (high-water mark) for the current system load</li>
</ul>

MONITOR ENQ


The following command specifies a formatted display of the number of pages from tables of each file that are currently located in the disk buffers: 

MONITOR DISKBUFF


The following command specifies information about SNA Communications Server's use of output buffers and waits for threads:

MONITOR VTAM


==MONITOR LINK example==


The following command specifies information about a network entity:

MONITOR LINK HEADQTRS


For more information about the MONITOR command for network monitoring, see <var class="product">Model 204</var> Horizon: Intersystem Processing.


In this example, HEADQTRS is the specified network entity for which the Online system operation is being monitored. The following statistics are provided:

 LOCAL ID MAXSES BNDSES IBWTS OBWTS CONVS FLGS TRAN/PROTO
-------- ------ ------ ----- ----- ----- ---- ----------
BOSTACB 4 2 0 0 2 A VTAM/LU62

USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
3 PROCESS1 5 4 BI DENVER OBSOLETE
4 PROCESS1 5 4 BI DENVER


Where:

<ul>
<li> LOCAL ID is the SNA Communications Server ACB name (BOSTACB).</li>

<li> MAXSES is the maximum number of sessions allowed on this link (4).


The limit is established by the SESSIONS parameter of the DEFINE LINK command.

<li> BNDSES indicates the number of currently bound sessions (2).</li>

<li> IBWTS indicates the number of input buffer waits (0) by inbound conversations.


The input buffer availability is controlled by the actual number of input buffers established by the INBUFNO parameter of the DEFINE LINK command. An input buffer is used on the inbound side when a conversation is being established. If IBWTS is high, and you observe delays while opening inbound processes, then increase INBUFNO.</li>

<li> OBWTS indicates the number of output buffer waits (0).


Note: OBWTS is always zero when the communication protocol is
LU 6.2 (output buffers are not used).</li>

<li> CONVS indicates the number of active conversations (2).</li>

<li> FLGS indicates the status of the link status (A). Possible values for FLGS are:

<table class="thJustBold">
<tr><th>A</th> <td>Active</td></tr>

<tr><th>S</th> <td>Stopped</td></tr>

<tr><th>C</th> <td>Closed</td></tr>
</table></li>

<li> TRAN indicates the transport mechanism: SNA Communications Server or terminal (TERM). In this case TRAN is SNA Communications Server. </li>

<li> PROTO indicates the communication protocol (LU 6.2). Possible values for PROTO are:

<table class="thJustBold">
<tr><th>MSTR</th> <td>Master (for TPROCESS)</td></tr>

<tr><th>XFER</th> <td>Transfer (for TPROCESS)</td></tr>

<tr><th>IMS61</th> <td>IMS LU 6.1</td></tr>

<tr><th>LU 6.2</th> <td>LU 6.2 </td></tr>
</table>


The second line of statistics is a detail line for each bound session.

<ul>
<li> USER provides the external user number (3, 4). A blank occurs if a conversation is not active.</li>

<li> PROCESS indicates the process name (PROCESS1). If a conversation is not active, a blank appears.</li>

<li> SENDS indicates the number of physical sends for each conversation
(5, 5).</li>

<li> RECVS indicates the number of physical receives for each conversation
(4, 4).</li>

<li> FLGS indicates the status of the session (BI, BI). The session status flags are:
<table class="thJustBold">
<tr><th>B </th>
<td>bound </td>
</tr>

<tr>
<th>F </th>
<td>first speaker </td>
</tr>

<tr>
<th>I </th>
<td>inbound </td>
</tr>

<tr>
<th>O </th>
<td>outbound </td>
</tr>

<tr>
<th>L </th>
<td>local bid in progress </td>
</tr>

<tr>
<th>R </th>
<td>remote bid accepted </td></tr>
</table></li></ul>

<li> PROCESSGRP provides the process group name (DENVER). In this example, user 3 is running with an OBSOLETE process group: the process group was stopped and a DEFINE PROCESSGROUP command was issued to change the process group definition for subsequent usage. User 4 is running with the most recent version of the process group definition. </li>
</ul>

==MONITOR PROCESSGROUP example==

The following command specifies reports concerning a specific process group:

MONITOR PROCESSGROUP 


In this example, two PROCESSGROUP reports are produced. The first report is for an active conversation. The second report reflects the stopping and redefinition of the active conversation, which is allocated to another conversation (OBSOLETE with the same process name). Until the conversation with the obsolete process group ends, separate reports are produced for each process group to reflect the more current set of attributes.

 MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 A

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 5 4 BI

MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 AX

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI


Where:

<ul>
<li><var>LINKNAME</var> names the associated link (<code>HEADQTRS</code>).</li>

<li><var>REMOTEID</var> provides the Remote LU name (<code>DENVACB</code>).</li>

<li><var>BNDSES</var> indicates the number of bound sessions (2).</li>

<li><var>INCONVS</var> indicates the number of active inbound conversations (1).</li>

<li><var>OTCONVS</var> indicates the number of active outbound conversations (0).</li>

<li><var>FLGS</var> indicates the status of the processgroup (<code>A</code>). The processgroup status flags are:
<table class="thJustBold">
<tr>
<th>A </th>
<td>Active </td>
</tr>

<tr>
<th>S </th>
<td>Stopped </td>
</tr>

<tr>
<th>X </th>
<td>Obsolete </td>
</tr>
</table></li>
</ul>


The second line of statistics is a detail line for each active conversation.

<ul>
<li><var>USER</var> indicates the external user number (4).</li>

<li><var>PROCESS</var> provides the name of the program as it is known to network users (<code>PROCESS1</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (5).</li>

<li><var>RECVS</var> indicates the number of physical receives (4).</li>

<li><var>FLGS</var> indicates the status of the session status (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>
</ul>

==MONITOR PROCESS example==

The following command specifies information about a particular process:

MONITOR PROCESS PROCESS1


In this example, two inbound conversations invoked from PROCESSGROUP DENVER (users 3 and 4) are in progress with the process named <code>PROCESS1</code>. The conversation ID (CID) that was assigned in the SOUL <var>OPEN PROCESS</var> statement is <code>PROGRAM1</code>.

MONITOR PROCESS PROCESS1

USER CID PROCESSGRP STARTED SENDS RECVS FLGS STATE
----- -------- ---------- ----------- ----- ----- ---- ------
3 PROGRAM1 DENVER 88349135723 5 4 BI RECV
4 PROGRAM1 DENVER 88349135803 5 4 BI RECV

<ul>
<li><var>USER</var> indicates the external user number (<code>3</code>, <code>4</code>).</li>

<li><var>CID</var> provides the conversation ID (<code>PROGRAM1</code>).</li>

<li><var>PROCESSGRP</var> indicates the name of the processgroup (<code>DENVER</code>).</li>

<li><var>STARTED</var> provides the Julian date and time the conversation began (<code>88349</code> and <code>13:57:23</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (<code>5</code>, <code>5</code>).</li>

<li><var>RECVS</var> indicates the number of physical receives (<code>4</code>, <code>4</code>).</li>

<li><var>FLGS</var> indicates the status of the session (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>

<li><var>STATE</var> indicates the state of the conversation (<code>RECV</code>). Conversation states can be:

:ACCEPT
:CLOSE
:CONFCLS
:CONFIRM
:CONFSND
:INITIAL
:RECV
:SEND
</li>
</ul>

==MONITOR DISKBUFF example==

You can use the <var>[[MONITOR command: Disk buffers|MONITOR DISKBUFF]]</var> commands to analyze the buffer pool utilizations:

<ul>
<li><var>MONITOR DISKBUFF</var> output shows buffer usage combining above and below the bar buffers.</li>

<li><var>MONITOR DISKBUFFG</var> output shows buffer pool usage for only above the bar buffers.</li>

<li><var>MONITOR DISKBUFFL</var> output shows buffer pool usage for only below the bar buffer usage.</li>
</ul>


Use these commands throughout the day across varied types of daily and event processing to evaluate your buffer allocations.

===Using MONITOR DISKBUFF commands===

You can see the types of pages that are in your buffer pools at any point in time using the <var>MONITOR DISKBUFF</var> command. The output of this command displays the types of pages that are in buffers and how many of each type.

MONITOR DISKBUFF

FILENAME FCT TBLA TBLB TBLC TBLD TBLE TBLX *TOTAL*
-------- --- ------ ------ ------ ------ ------ ------ -------
CCATEMP 0 40 0 0 0 0 0 40
PROC1 1 0 0 0 11 0 0 12
FILETBLX 1 1 10 0 2 0 2 16
TESTZ 1 1 11 0 3 185 0 201
*TOTAL* 3 42 21 0 16 185 2 269


[[Category:System management]]
[[Category:Model 204 operational issues]]

ONLINE monitoring

2020-05-20T15:27:41Z

DCameron: /* Basic display */

You can monitor the status and performance of an ONLINE system, including SNA Communications Server interfaces, with the MONITOR command. See [[MONITOR command]] for complete command syntax.


MONITOR provides a series of formatted or unformatted displays of system and user statistics about all or a selected set of active users. You can update the displays on a periodic basis, but do not update them more frequently than every five seconds. 

==Unformatted displays==

Unformatted displays show all the nonzero cumulative system or user statistics in a format similar to that provided in the journal: 

<ul>
<li> Series of terms appears in name=value format.</li>

<li> Journal header is not displayed.</li>

<li> Each user is identified by user number.</li>

<li> Account name appears at the beginning of the user's display.
</li>
</ul>

==Formatted displays==

Formatted displays show basic system information, followed by specified user information in labelled columns. 


Basic system information includes the number of:

<ul>
<li> Active users (USR)</li>

<li> Active servers (SVR)</li>

<li> Open buffers (BUF)</li>

<li> Open files (FLS) </li>

<li> A file open as part of one or more permanent groups is followed by an asterisk (*).</li>

<li> Two pound signs (##) indicate that the user has more files open than can fit into the internal buffer used to hold open file names.</li>

<li> System percentage of CPU time (PCPU).</li>

<li> Statistics from the last system performance line written to the journal. If performance monitoring is active and performance lines are being written to the journal, all statistics are shown. Otherwise, only open buffers, open files, and system PCPU are shown.
</li>
</ul>


Specified user information is described in the next section.

==User information in formatted displays==

User information is viewable in the following types of formatted displays:

<ul>
<li> Basic display (default)</li>

<li> User since-last statistics</li>

<li> User performance data</li>

<li> Open files
</li>
</ul>


The following sections describe these types of formatted displays.

===Basic display===

USER SVR USERID P CUR SLICE AGE FUNC CNCT CPU SEQIO QUE WT FLGS
0 SAM S 48 0.075 0 0.041 3 BLKO 04 40
1 1 MARY S 49 0.075 EVAL 266 0.152 36 REDY


Where:

<ul>
<li>USER is the user number.</li>
<li>SVR is the server number.</li>
<li>USERID is the user ID.</li>
<li>P is user priority (P).</li>
<li>CUR is current priority.</li>
<li>SLICE is current CPU time slice.</li>
<li>AGE is user pre-aged priority.</li>
<li>FUNC is the last function to set the since-last parameter.</li>
<li>CNCT is connect time.</li>
<li>CPU is CPU time.</li>
<li>SEQIO is the sequential I/O operations performed.</li>
<li>QUE is the [[#QUE values|current scheduler queue]].</li>
<li>WT is the [[#Wait state values|user wait state]].</li>
<li>FLGS is the sum of the [[#Status flag values|status flag values]].</li>
</ul>

====QUE values====
<table>
<tr class="head">
<th>

QUE value 
</th>
<th>

Means user is...
</th>
</tr>

<tr>
<td>

RUNG 
</td>
<td>

Running.
</td>
</tr>

<tr>
<td>

BLKI 
</td>
<td>

Blocked in server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFI 
</td>
<td>

Blocked in server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

BLKO 
</td>
<td>

Blocked out of server, visible to the scheduler.
</td>
</tr>

<tr>
<td>

OFFO 
</td>
<td>

Blocked out of server, invisible to the scheduler.
</td>
</tr>

<tr>
<td>

WTSV 
</td>
<td>

Waiting for a server.
</td>
</tr>

<tr>
<td>

REDY 
</td>
<td>

Ready or running.
</td>
</tr>

<tr>
<td>

SWPG 
</td>
<td>

Being swapped in or out.
</td>
</tr>

<tr>
<td>

WTUS 
</td>
<td>

Server waiting for user.
</td>
</tr>

<tr>
<td>

MOVE
</td>
<td>

Moving between queues.
</td>
</tr>
</table>

Tip: As of version 7.7, by summing RUNG, BLKI, BLKO, WTSV, REDY, and SWPG, you can approximate USRS (average active users).

Note: Prior to version 7.7, OFFQ was used instead of OFFI and OFFO.

====Wait type values====
<table>
<tr class="head">
<th>

Wait
</th>
<th>

Description
</th>
</tr>

<tr>
<td>

00
</td>
<td>

Unspecified.
</td>
</tr>

<tr>
<td>

01
</td>
<td>

Disk I/O.
</td>
</tr>

<tr>
<td>
02
</td>
<td>

Sequential user I/O — output.
</td></tr>

<tr>
<td>
03
</td>
<td>

Sequential user I/O — input.
</td></tr>

<tr>
<td>
04
</td>
<td>

Operator's console input (WTOR).
</td></tr>

<tr>
<td>
05
</td>
<td>
Restore reads (BSAM).
</td></tr>

<tr>
<td>

06
</td>
<td>

Dump writes (BSAM). 
</td></tr>

<tr>
<td>
07
</td>
<td>
Enqueue waits (record or noncritical resource).
</td></tr>

<tr>
<td>
08
</td>
<td>

Buffer waits.
</td></tr>

<tr>
<td>
09
</td>
<td>
Wait almost forever (deactivated user).
</td></tr>

<tr>
<td>
10
</td>
<td>
Waits for a pseudo subtask, or waits for reactivation (hung terminal).
</td></tr>

<tr>
<td>
11
</td>
<td>
Waits for an IFAM2 or IFAM4 call.
</td></tr>

<tr>
<td>
12
</td>
<td>
Waits for a wakeup.
</td></tr>

<tr>
<td>
13
</td>
<td>
Server I/O.
</td></tr>

<tr>
<td>
15
</td>
<td>
Writes to the journal data set, CCAJRNL.
</td></tr>

<tr>
<td>
16
</td>
<td>
Checkpoint writes to CHKPOINT data set.
</td></tr>

<tr>
<td>
17
</td>
<td>
Waits for check on previous write.
</td></tr>

<tr>
<td>
18
</td>
<td>
Waits for a checkpoint DECB to free up or waiting for multiuser output arbitration.
</td></tr>

<tr>
<td>
19
</td>
<td>
Waits for a checkpoint request.
</td></tr>

<tr>
<td>
20
</td>
<td>
Waits for a checkpoint completion.
</td></tr>

<tr>
<td>
21
</td>
<td>
Wait forever (dead user).
</td></tr>

<tr>
<td>
22
</td>
<td>
VSAM or sequential file input.
</td></tr>

<tr>
<td>
23
</td>
<td>
User waiting due to excessive login failures.
</td></tr>

<tr>
<td>
24
</td>
<td>
Waits for exclusive control of critical file resource.
</td></tr>

<tr>
<td>
25
</td>
<td>
Waits for share control of critical file resource.
</td></tr>

<tr>
<td>
26
</td>
<td>
Waits for SNA Communications Server buffer, input or output.
</td></tr>

<tr>
<td>
27
</td>
<td>
Waits for interprocess input.
</td></tr>

<tr>
<td>
28
</td>
<td>
Waits for interprocess output.
</td></tr>

<tr>
<td>
29
</td>
<td>
User waiting for the security interface.
</td></tr>

<tr>
<td>
30
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'SWAP')</code>, for a user-defined ECB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
31
</td>
<td>
User(s) waiting, with <code>$Wait(nn,'NOSWAP')</code>, for a user-defined EDB to be posted by a <var>$Post</var> function from a different user.
</td></tr>

<tr>
<td>
32
</td>
<td>
User waiting for DB2 subtask.
</td>
</tr>

<tr>
<td>
33-36
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>
37
</td>
<td>
User waiting for recovery to complete.
</td>
</tr>

<tr>
<td>
38
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

39
</td>
<td>
Reserved for future development.
</td>
</tr>

<tr>
<td>

40
</td>
<td>
Waiting for an MQSeries subtask to become available.
</td>
</tr>

<tr>
<td>

41
</td>
<td>
Waiting for a MQ subtask to run.
</td>
</tr>

<tr>
<td>

42
</td>
<td>
MQSeries MQGET operations with wait time specified.
</td>
</tr>

<tr>
<td>

43
</td>
<td>
ECF to load or delete a module. 
</td>
</tr>

<tr>
<td>
44
</td>
<td>
External module to become free. 
</td>
</tr>

<tr>
<td>
45
</td>
<td>
ECF subtask to become free.
</td>
</tr>

<tr>
<td>
46
</td>
<td>
External module to run.
</td>
</tr>

<tr>
<td>
47
</td>
<td>
User(s) waiting, with <code>$Wait('CPQZ')</code>, for the extended quiesce ECB to be posted by the successful completion of a <var class="product">Model 204</var>, system-wide checkpoint.
</td>
</tr>

<tr>
<td>
48
</td>
<td>
User(s) waiting, with <code>$Wait('QZSIG')</code>, for the end of extended quiesce.
</td></tr>

<tr>
<td>
49
</td>
<td>
User(s) waiting, at end of extended quiesce, for count of <code>$Wait('CPQZ')</code> and <code>$Wait('QZSIG')</code> users to go to zero.
</td></tr>

<tr>
<td>
50
</td>
<td>
User is waiting for HSM to recall an archived data set.
</td></tr>

<tr>
<td>
51
</td>
<td>
User is waiting for a share lock on the internal constraints database. 
The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
52
</td>
<td>

User is waiting for an exclusive lock on the internal constraints database. 

The constraints database is used to ensure that there is sufficient space on table B pages and in table D to be able to back out active transactions as needed.
</td></tr>

<tr>
<td>
53
</td>
<td>
User is waiting for a subtransaction checkpoint to complete.
</td></tr>

<tr>
<td>
54
</td>
<td>
Checkpoint PST waiting on a blocking file update to complete to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
55
</td>
<td>
Checkpoint PST doing a timed wait to try to do a transaction checkpoint.
</td></tr>

<tr>
<td>
56
</td>
<td>
Checkpoint PST waiting on users to complete subtransactions.
</td></tr>

<tr>
<td>
80-89
</td>
<td>
Customer (site-specific) wait types.
</td></tr>

<tr>
<td>
97
</td>
<td>
Waiting for a Fast/Unload request running in a real subtask.
</td></tr>

<tr>
<td>
98
</td>
<td>
In a <var>[[MAXAUSER parameter|MAXAUSER]]</var> wait.
</td></tr>

<tr>
<td>
99
</td>
<td>
Waiting for a <var>[[SIRFACT command|SIRFACT QUIESCE]]</var> to be completed (with a <var>SIRFACT RESUME</var>).
</td></tr>
</table>

====Status flag values====
<table>
<tr class="head">
<th>

Flag
</th>
<th>

Description of wait...
</th>
</tr>

<tr>
<td>

40
</td>
<td>

User's wait is swappable. If another user needs this user's server area, the waiter may be written out.</td>
</tr>

<tr>
<td>20</td>
<td>User is waiting for an internal ECB (that is, the ECB is posted only by <var class="product">Model 204</var>, not by the operating system). This can happen, for example, if the waiting user is waiting to access a record to which someone else is preventing access. </td>
</tr>

<tr>
<td>10</td>
<td>ECB to be posted is of the short form (1 byte in length) and is an internal ECB (posted by M204). </td>
</tr>

<tr>
<td>8</td>
<td>More than one user is allowed to wait for the ECB that this user is waiting for. </td>
</tr>

<tr>
<td>4</td>
<td>User can be bumped.</td>
</tr>

<tr>
<td>2</td>
<td>User can be interrupted with an urgent message.</td>
</tr>

<tr>
<td>1</td>
<td>A time limit was specified for the user's wait. For example, if a waiting user is in a record locking conflict situation, it is a timed wait until the request ends and a record locking conflict message is issued, or an <var>ON</var> unit in the code takes control.</td>
</tr>
</table>

====V7.8 layout change====

===User since-last statistics===

User since-last statistics (SL option) show current activity.


If the user is between activities or performing an activity that does not initialize since-last statistics, the display is cumulative.


Statistics displayed are CPU, DKRD, DKWR, UDD, OUT, SLIC, FINDS, RECDS, PCPU, RQTM, SUBSYSTEM, PROC-FILE, PROC, and the pseudo subtask's user ID, account name, and user number. (Refer to the [[#Description of statistics|Statistics with descriptions]] table for statistic definitions, and to [[#Pseudo subtasks|Pseudo subtasks]].) 

===User performance data===

The PERFORMANCE option shows data last written to the journal. The following information is included:

<ul>
<li> Number of samples used to compute percentages</li>

<li> percentage of time the user is in each of the scheduler queues</li>
</ul>


See [[#Priority scheduling|Priority scheduling]].

===Open files===

This display is a list of files a user has open.

==MONITOR examples==

These examples show several variations of the MONITOR command.


The following command specifies a single nonrepeating formatted display of basic information for the system and all active users:

MONITOR


The following command, MONITOR ACTIVE, specifies a single nonrepeating formatted display of basic information for the system and active users, excepting OFFO and OFFI users. (OFFO and OFFI are state-of-queue statuses meaning that the Scheduler does not have to evaluate those users not in the queue. Prior to version 7.7, OFFQ was used instead of OFFO and OFFI.)
The MONITOR ACTIVE command is used to reduce the amount of terminal output.

MONITOR ACTIVE


The following commands specify a display of the cumulative system statistics, which is updated every minute:

MONITOR STATISTICS 60
MONITOR STAT EVERY 60
MONITOR SYSTEM STATISTICS 60


The following command specifies a single display of the cumulative user statistics for users 1, 3, and 5, if they are active:

MONITOR (1,3,5) STATISTICS


The following commands specify a single formatted display of basic system information and basic, since-last, performance, and file information for each active user. Pseudo subtask's user ID, account name, and user number are displayed for SL (since-last) statistics:

MONITOR ALL
MONITOR USERS ALL
MONITOR BASIC SL PERFORMANCE FILE
MONITOR SL FILE PERF


The following commands specify a display of basic formatted information for the system and users 1, 2, 5, and 7, if they are active. The display is repeated continually 75 seconds after it completes. The user must press Enter to display the refreshed version, or enter *CANCEL to terminate the display:

MONITOR (1,2,5,7) 75
MONITOR (1,2,5,7) BASIC EVERY 75


The following command specifies an unformatted display of the following information:

<ul>
<li> Number of active users</li>

<li> Number of compactions of the record locking table</li>

<li> Current number of bytes used in the record locking table</li>

<li> Current high-water mark for the number of bytes used in the record locking table</li>

<li> Current number of headers used in the record locking table</li>

<li> Current high-water mark for the number of headers used in the record locking table</li>

<li> Required LRETBL setting (high-water mark) for the current system load</li>
</ul>

MONITOR ENQ


The following command specifies a formatted display of the number of pages from tables of each file that are currently located in the disk buffers: 

MONITOR DISKBUFF


The following command specifies information about SNA Communications Server's use of output buffers and waits for threads:

MONITOR VTAM


==MONITOR LINK example==


The following command specifies information about a network entity:

MONITOR LINK HEADQTRS


For more information about the MONITOR command for network monitoring, see <var class="product">Model 204</var> Horizon: Intersystem Processing.


In this example, HEADQTRS is the specified network entity for which the Online system operation is being monitored. The following statistics are provided:

 LOCAL ID MAXSES BNDSES IBWTS OBWTS CONVS FLGS TRAN/PROTO
-------- ------ ------ ----- ----- ----- ---- ----------
BOSTACB 4 2 0 0 2 A VTAM/LU62

USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
3 PROCESS1 5 4 BI DENVER OBSOLETE
4 PROCESS1 5 4 BI DENVER


Where:

<ul>
<li> LOCAL ID is the SNA Communications Server ACB name (BOSTACB).</li>

<li> MAXSES is the maximum number of sessions allowed on this link (4).


The limit is established by the SESSIONS parameter of the DEFINE LINK command.

<li> BNDSES indicates the number of currently bound sessions (2).</li>

<li> IBWTS indicates the number of input buffer waits (0) by inbound conversations.


The input buffer availability is controlled by the actual number of input buffers established by the INBUFNO parameter of the DEFINE LINK command. An input buffer is used on the inbound side when a conversation is being established. If IBWTS is high, and you observe delays while opening inbound processes, then increase INBUFNO.</li>

<li> OBWTS indicates the number of output buffer waits (0).


Note: OBWTS is always zero when the communication protocol is
LU 6.2 (output buffers are not used).</li>

<li> CONVS indicates the number of active conversations (2).</li>

<li> FLGS indicates the status of the link status (A). Possible values for FLGS are:

<table class="thJustBold">
<tr><th>A</th> <td>Active</td></tr>

<tr><th>S</th> <td>Stopped</td></tr>

<tr><th>C</th> <td>Closed</td></tr>
</table></li>

<li> TRAN indicates the transport mechanism: SNA Communications Server or terminal (TERM). In this case TRAN is SNA Communications Server. </li>

<li> PROTO indicates the communication protocol (LU 6.2). Possible values for PROTO are:

<table class="thJustBold">
<tr><th>MSTR</th> <td>Master (for TPROCESS)</td></tr>

<tr><th>XFER</th> <td>Transfer (for TPROCESS)</td></tr>

<tr><th>IMS61</th> <td>IMS LU 6.1</td></tr>

<tr><th>LU 6.2</th> <td>LU 6.2 </td></tr>
</table>


The second line of statistics is a detail line for each bound session.

<ul>
<li> USER provides the external user number (3, 4). A blank occurs if a conversation is not active.</li>

<li> PROCESS indicates the process name (PROCESS1). If a conversation is not active, a blank appears.</li>

<li> SENDS indicates the number of physical sends for each conversation
(5, 5).</li>

<li> RECVS indicates the number of physical receives for each conversation
(4, 4).</li>

<li> FLGS indicates the status of the session (BI, BI). The session status flags are:
<table class="thJustBold">
<tr><th>B </th>
<td>bound </td>
</tr>

<tr>
<th>F </th>
<td>first speaker </td>
</tr>

<tr>
<th>I </th>
<td>inbound </td>
</tr>

<tr>
<th>O </th>
<td>outbound </td>
</tr>

<tr>
<th>L </th>
<td>local bid in progress </td>
</tr>

<tr>
<th>R </th>
<td>remote bid accepted </td></tr>
</table></li></ul>

<li> PROCESSGRP provides the process group name (DENVER). In this example, user 3 is running with an OBSOLETE process group: the process group was stopped and a DEFINE PROCESSGROUP command was issued to change the process group definition for subsequent usage. User 4 is running with the most recent version of the process group definition. </li>
</ul>

==MONITOR PROCESSGROUP example==

The following command specifies reports concerning a specific process group:

MONITOR PROCESSGROUP 


In this example, two PROCESSGROUP reports are produced. The first report is for an active conversation. The second report reflects the stopping and redefinition of the active conversation, which is allocated to another conversation (OBSOLETE with the same process name). Until the conversation with the obsolete process group ends, separate reports are produced for each process group to reflect the more current set of attributes.

 MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 A

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 5 4 BI

MONITOR PROCESSGROUP DENVER

LINKNAME REMOTEID BNDSES INCONVS OTCONVS FLGS
-------- -------- ------ ------- ------- ----
HEADQTRS DENVACB 2 1 0 AX

USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI


Where:

<ul>
<li><var>LINKNAME</var> names the associated link (<code>HEADQTRS</code>).</li>

<li><var>REMOTEID</var> provides the Remote LU name (<code>DENVACB</code>).</li>

<li><var>BNDSES</var> indicates the number of bound sessions (2).</li>

<li><var>INCONVS</var> indicates the number of active inbound conversations (1).</li>

<li><var>OTCONVS</var> indicates the number of active outbound conversations (0).</li>

<li><var>FLGS</var> indicates the status of the processgroup (<code>A</code>). The processgroup status flags are:
<table class="thJustBold">
<tr>
<th>A </th>
<td>Active </td>
</tr>

<tr>
<th>S </th>
<td>Stopped </td>
</tr>

<tr>
<th>X </th>
<td>Obsolete </td>
</tr>
</table></li>
</ul>


The second line of statistics is a detail line for each active conversation.

<ul>
<li><var>USER</var> indicates the external user number (4).</li>

<li><var>PROCESS</var> provides the name of the program as it is known to network users (<code>PROCESS1</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (5).</li>

<li><var>RECVS</var> indicates the number of physical receives (4).</li>

<li><var>FLGS</var> indicates the status of the session status (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>
</ul>

==MONITOR PROCESS example==

The following command specifies information about a particular process:

MONITOR PROCESS PROCESS1


In this example, two inbound conversations invoked from PROCESSGROUP DENVER (users 3 and 4) are in progress with the process named <code>PROCESS1</code>. The conversation ID (CID) that was assigned in the SOUL <var>OPEN PROCESS</var> statement is <code>PROGRAM1</code>.

MONITOR PROCESS PROCESS1

USER CID PROCESSGRP STARTED SENDS RECVS FLGS STATE
----- -------- ---------- ----------- ----- ----- ---- ------
3 PROGRAM1 DENVER 88349135723 5 4 BI RECV
4 PROGRAM1 DENVER 88349135803 5 4 BI RECV

<ul>
<li><var>USER</var> indicates the external user number (<code>3</code>, <code>4</code>).</li>

<li><var>CID</var> provides the conversation ID (<code>PROGRAM1</code>).</li>

<li><var>PROCESSGRP</var> indicates the name of the processgroup (<code>DENVER</code>).</li>

<li><var>STARTED</var> provides the Julian date and time the conversation began (<code>88349</code> and <code>13:57:23</code>).</li>

<li><var>SENDS</var> indicates the number of physical sends (<code>5</code>, <code>5</code>).</li>

<li><var>RECVS</var> indicates the number of physical receives (<code>4</code>, <code>4</code>).</li>

<li><var>FLGS</var> indicates the status of the session (<code>BI</code>). Status flags are:
<table class="thJustBold">
<tr>
<th>B </th>
<td>Bound </td>
</tr>

<tr>
<th>F </th>
<td>First speaker </td>
</tr>

<tr>
<th>I </th>
<td>Inbound </td>
</tr>

<tr>
<th>O </th>
<td>Outbound </td>
</tr>
</table></li>

<li><var>STATE</var> indicates the state of the conversation (<code>RECV</code>). Conversation states can be:

:ACCEPT
:CLOSE
:CONFCLS
:CONFIRM
:CONFSND
:INITIAL
:RECV
:SEND
</li>
</ul>

==MONITOR DISKBUFF example==

You can use the <var>[[MONITOR command: Disk buffers|MONITOR DISKBUFF]]</var> commands to analyze the buffer pool utilizations:

<ul>
<li><var>MONITOR DISKBUFF</var> output shows buffer usage combining above and below the bar buffers.</li>

<li><var>MONITOR DISKBUFFG</var> output shows buffer pool usage for only above the bar buffers.</li>

<li><var>MONITOR DISKBUFFL</var> output shows buffer pool usage for only below the bar buffer usage.</li>
</ul>


Use these commands throughout the day across varied types of daily and event processing to evaluate your buffer allocations.

===Using MONITOR DISKBUFF commands===

You can see the types of pages that are in your buffer pools at any point in time using the <var>MONITOR DISKBUFF</var> command. The output of this command displays the types of pages that are in buffers and how many of each type.

MONITOR DISKBUFF

FILENAME FCT TBLA TBLB TBLC TBLD TBLE TBLX *TOTAL*
-------- --- ------ ------ ------ ------ ------ ------ -------
CCATEMP 0 40 0 0 0 0 0 40
PROC1 1 0 0 0 11 0 0 12
FILETBLX 1 1 10 0 2 0 2 16
TESTZ 1 1 11 0 3 185 0 201
*TOTAL* 3 42 21 0 16 185 2 269


[[Category:System management]]
[[Category:Model 204 operational issues]]

Under construction

2020-05-20T13:31:34Z

DCameron: Blanked the page

Under construction

2020-05-20T13:31:11Z

DCameron: Created page with "fred"

fred

Release notes for Model 204 version 7.8

2020-05-13T12:53:46Z

DCameron: /* MONITOR */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-13T12:51:39Z

DCameron: /* MONITOR */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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>

===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-13T12:44:35Z

DCameron: /* MONITOR */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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

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
>

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>
</ul>

===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-13T12:38:30Z

DCameron: /* New and changed commands */

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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===

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
>


===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T16:20:06Z

DCameron: /* Internal performance improvements */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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 IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T16:16:28Z

DCameron: /* Internal performance improvements */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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>
</ul>

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T16:13:47Z

DCameron: /* Performance enhancements */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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>
</ul>

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T15:14:46Z

DCameron: /* Limiting the production of MSIR.0019 and MSIR.0020 messages */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

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==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T15:13:00Z

DCameron: /* Limiting the production of MSIR.0019 and MSIR.0020 messages */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

is now limited to a maximum of one each per time interval set by the <var>[[MAXAUSEW_parameter|MAXAUSEW]]</var> parameter ( minimum seconds between MAXAUSER 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 ).

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T15:11:40Z

DCameron: /* Limiting the production of MSIR.0019 and MSIR.0020 messages */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

MSIR.0020 Connection request rejected for port (port), no SDAEMONS available

is now limited to a maximum of one each per time interval set by the MAXAUSEW parameter ( minimum seconds between MAXAUSER 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 ).

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T15:02:12Z

DCameron: /* Janus product enhancements */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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===

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-05-06T08:57:17Z

DCameron: /* Recovery enhancements */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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.

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.8

2020-04-14T15:41:05Z

DCameron: /* Compatibility issues */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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:
printText {~="War and Peace":endsWith("Peace")}
printText {~="War and Peace":endsWith("War")}

displays:
"War and Peace":endsWith("Peace")=True
"War and Peace":endsWith("War")=False


===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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.

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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. 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==
===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==

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

[[Category: Release notes]]

New and updated messages in Model 204 version 7.8

2020-02-26T15:35:56Z

DCameron: /* M204.2974 Action disabled by commit exit */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}
===M204.2971 No 2PC ports named token with coordinators named token2 defined===



Response:

{{Template:M204.2971 footer}}
===M204.2972 Warning SIRTERM X'02' bit not set - WSF Query not supported===



Response:

{{Template:M204.2972 footer}}
===M204.2973 Unable to reset Model to token: token2===



Response:

{{Template:M204.2973 footer}}
===M204.2974 Action disabled by commit exit===

An attempt to invoke the Commit Exit features failed. For example this might occur because the commit Exit apsy defined by the COMMITX parameter is not defined to CCASYS, or becasuse apsy processing ( SYSOPT 1 ) is not available to the current run even though COMMITX is set in CCAIN. The user session invoking the Commit Exit feature is restarted, and the updates causing Commit Exit to be invoked are backed out.


Response:

{{Template:M204.2974 footer}}

===M204.2975 token connection to host token2token3token4 port number token5 using Janus 2PC port token6===



Response:

{{Template:M204.2975 footer}}
===M204.2976 Attempt to update non-TBO file in a global transaction===



Response:

{{Template:M204.2976 footer}}
===M204.2977 Global transaction error: token===



Response:

{{Template:M204.2977 footer}}
===M204.2978 Implicit commit of global transaction failed===



Response:

{{Template:M204.2978 footer}}
===M204.2979 There were errors before RESTART===



Response:

{{Template:M204.2979 footer}}
===M204.2988 VTAM transfer failed, Session Parametes(LOGMODE, Cryptography, or VPACING) not valid===



Response:

{{Template:M204.2988 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-26T15:06:39Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}
===M204.2971 No 2PC ports named token with coordinators named token2 defined===



Response:

{{Template:M204.2971 footer}}
===M204.2972 Warning SIRTERM X'02' bit not set - WSF Query not supported===



Response:

{{Template:M204.2972 footer}}
===M204.2973 Unable to reset Model to token: token2===



Response:

{{Template:M204.2973 footer}}
===M204.2974 Action disabled by commit exit===



Response:

{{Template:M204.2974 footer}}
===M204.2975 token connection to host token2token3token4 port number token5 using Janus 2PC port token6===



Response:

{{Template:M204.2975 footer}}
===M204.2976 Attempt to update non-TBO file in a global transaction===



Response:

{{Template:M204.2976 footer}}
===M204.2977 Global transaction error: token===



Response:

{{Template:M204.2977 footer}}
===M204.2978 Implicit commit of global transaction failed===



Response:

{{Template:M204.2978 footer}}
===M204.2979 There were errors before RESTART===



Response:

{{Template:M204.2979 footer}}
===M204.2988 VTAM transfer failed, Session Parametes(LOGMODE, Cryptography, or VPACING) not valid===



Response:

{{Template:M204.2988 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-26T14:56:24Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}
===M204.2971 No 2PC ports named token with coordinators named token2 defined===



Response:

{{Template:M204.2971 footer}}
===M204.2972 Warning SIRTERM X'02' bit not set - WSF Query not supported===



Response:

{{Template:M204.2972 footer}}
===M204.2973 Unable to reset Model to token: token2===



Response:

{{Template:M204.2973 footer}}
===M204.2974 Action disabled by commit exit===



Response:

{{Template:M204.2974 footer}}
===M204.2975 token connection to host token2token3token4 port number token5 using Janus 2PC port token6===



Response:

{{Template:M204.2975 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-26T14:44:35Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}
===M204.2971 No 2PC ports named token with coordinators named token2 defined===



Response:

{{Template:M204.2971 footer}}
===M204.2972 Warning SIRTERM X'02' bit not set - WSF Query not supported===



Response:

{{Template:M204.2972 footer}}
===M204.2973 Unable to reset Model to token: token2===



Response:

{{Template:M204.2973 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-26T14:33:54Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}
===M204.2971 No 2PC ports named token with coordinators named token2 defined===



Response:

{{Template:M204.2971 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

Release notes for Model 204 version 7.8

2020-02-19T14:49:46Z

DCameron: /* Increase URL length returned with $web_form_action */

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

These release notes list the enhancements and other changes contained in Model 204 version 7.8, 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.8 release.
Before beginning your installation, please read through this information about product installation and changes.

==New in this release==
The table below cites some highlights of Model 204 version 7.8. For a full list of features, refer to the Table of Contents.
See also the [[#Compatibility issues|Compatibility]] section for possible issues.
<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>
Note: 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 requirements===

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

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

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

===Hardware requirements===

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

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

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

For more information on Connect★ installation, see the [[:Category:Connect*|Connect★ 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>

===$ProcOpn===
<var>[[$ProcOpn|$ProcOpn]]</var> now supports the opening of a procedure with an all-numeric name, and including a leading zero, such as:

%result = $procOpn('0123', 'MYFILE')

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:
 begin
variables are undefined
%isValid is boolean initial (True)
if (%isValid) then
print 'in IF'
end if
end 

will now compile and run successfully, since this syntax:

if (%isValid) then 

is logically equivalent to this:

if %isValid then 

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:
 begin
%x is object object
%y is object object
%y = new
%x = %y:copy
end 

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

will produce this result:

 %(Local):(%func)=red 

whereas previously this line:

 %func = (colour):red 

would have been rejected with this message:

MSIR.0993: Assignment invalid: mismatch between method and method variable 

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:
function getRemote( -
%target is string len 32, %errorReason is string len 80 optional output -
) is float
...

In this example, if <code>%errorReason</code> is not specified in a call and then set to a value longer than 80 bytes it wil 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:

EXTERNAL REMOVE modulename

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

SNAPID 1 19226.060155 M204.0022: Bug .. nnnnn PAGE 1 

whereas the same snap header under v7.8 would show as:

SNAPID 1 2019/08/14 06:01:06 M204.0022: Bug .. nnnnn PAGE 1 

Also, due to improvements in handling trailing blanks in snap output, a snap generated under v7.8 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|DEBUGL]]</var> parameter. Note that the <var>DEBUGUL</var> approach will introduce extra QTBL overhead. (<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.)
</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:

M204.2966: Error at line n, procedure ''procname'' in file ''procfile''

which identifies the line within a procedure where the error is occurring, in addition to the usual message:

M204.0552: Variable too small for result

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


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

If neither <var>SIRFACT X'01'</var> nor <var>DEBUGUL</var> is set, then the "variable too small" error produces the following messages:
 M204.0552: Variable too small for result
M204.2968: Error: no debug info 

====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.
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:
M204.0569: File ''filename'', Find: Table B records to be searched = ''nnnn''
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:
Cancelling request: M204.2969: MBSCAN (''mm'') exceeded, records to be searched = ''nnnn''

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:
 b
call sub1
sub1: subroutine
fd1:
in clients fd city = ONTARIO
end find
fr fd1
pai
print
end for
end subroutine
end 

then the following messages are produced, assuming any prompts are responded to with an 'N':
 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 

===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==
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.
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.
==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.
NOTE: This parameter and the 78 version (or later) of AUDIT204 may be used against a 77 (or later) CCAJRNL.
For example:
//CCAIN DD *
FORMAT YEARFORM 4
TIMEHH
TYPE ER MS LI

==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.

==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.

===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 for non-SSL ports to the following:
JANUS WEB portname DISALLOW *


This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies unless overridden by user-added rules.

<blockquote class="note">
Note: 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: 
RESET WEBDFLT=1
</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

MSIR.0019 Connection request rejected for port (port), MAXCON exceeded

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.

==Debugger enhancements==
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==

===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.

==New and changed commands==
===MONITOR IODEV===
This new command displays the total number, the current usage and the maximum number of each IODEV type. 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 '*'. 
M IODEV 
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===
DISPLAY ECF {{ M | N | U } like ?} 

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

(flags may be D=deleted; S=shared; H=halted; I=Idle)

<code>D ECF N</code> displays contents of the name table. For example: D ECF N
Module Logical-call-name
QATUM13C MOD_QATUM13C
QATUM13B MOD_QATUM13B
QATUM13A MOD_QATUM13A 

<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:
 D ECF U
User# Userid Module Parmlen
00002 ADMIN --none--
00003 ADMIN COBSAMP1 00000002
00004 ADMIN COBSAMP1 00000002 

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

D ECF U L A
or
D ECF U L A*

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:
 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} ]

The default for the using ddname is CCAGEN, but any ddname may be used to allocate an input journal and used. For example:
 ALLOCATE REGEN1 WITH SCOPE=SYSTEM DSN=PROD1.GDGJ OLD SEQUENTIAL GEN=+2
REGENERATE USING REGEN1 FILE TEST

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:
 M204.1430: Failed to open file TEST
M204.1436: Stopped processing file TEST 

$STATUS will now be set for <var>REGENERATE</var> with the following values:
<blockquote>
0 - Success 
1 - No files were processed 
2 - At least one file stopped processing 
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 %x is string len 1
%y is string len 2
%y = 'ab'
%x = %y
printtext {~} = {%x} 

would cause silent truncation, and give the result
%x = a 

If <var>EVALOPT</var> is set to 1, then the above code produces the following message:
M204.0552: Variable too small for result 

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===
Introduced in zap 77z257.
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>

Each new parameter defaults to unlimited. 
If a parameter value is set, a transaction is cancelled if that value is exceeded, and the following message is displayed:
M204.0524: Maximum number (num) of parameter exceeded.
where num is the value set for parameter (<var>MAXPRE</var>, <var>MAXBOUT</var>, or <var>MAXSUBT</var>).

===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.

==New and changed statistics==
===MPR, MBO, MCP, and RCV===
Introduced in zap 77z257.
These statistics provide high water mark transaction information. (Since-last values will not be available until V78 GA.)
They are useful in conjunction with the <var>[[#MAXPRE, MAXBOUT, MAXSUBT|MAXPRE, MAXBOUT, and MAXSUBT]]</VAR> parameters. 

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>
Notes: 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]].


===DKWTS and DKWTMICS===
Introduced in zap 77z7289.
The new system statistics DKWTS (DisK WaiTs) and DKWTMICS (DisK WaiT MICroSeconds) collect data to provide rough disk I/O service time numbers.

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.

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

==Compatibility issues==
===$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]].
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.

<blockquote class="note">Note: Strictly speaking, this would not be considered a compilation error, because previously although <code>.. 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>$Listxxx</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:

CALL IFSTRTN(RC,'logonid;password;'...)

If a semicolon does not follow the password string, the following message will now be issued:

M204.2964: Password missing or too long 

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:

 M204.1123: Parameter TCPOPTS not reset

===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:
 M204.1875 UNABLE TO RESET MODEL TO %C
M204.1123: Parameter MODEL not reset

the following message will now be issued:

 M204.1008: LOUTPB must be increased to at least <number> 

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.

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

==New 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==

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

[[Category: Release notes]]

New and updated messages in Model 204 version 7.8

2020-02-12T15:46:25Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0562: Request too long - tableName tableValue===

From v7.8 onwards, the message text for this message includes the current table setting, as above. Prior to V7.8, the message text was as follows

M204.0562: Request too long - tableName

{{Template:M204.0562 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T15:26:31Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1289: (LGTBL - GTBLHASH*10) must be at least 288 for subsystem processing

{{Template:M204.1289 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T15:22:18Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1215: XTBL, LXTBL=nnnn - not enough space===

From v7.8 onwards, the message text for this message includes the current LXTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1215: XTBL - not enough space

{{Template:M204.1215 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T15:09:28Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1167: ITBL full, LITBL=nnnn -- argument string ignored===

From v7.8 onwards, the message text for this message includes the current LITBL setting, as above. Prior to V7.8, the message text was as follows

M204.1167: ITBL full -- argument string ignored

{{Template:M204.1167 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T15:03:19Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0861: FTBL full, LFTBL=nnnn can't open group===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0861: FTBL full, can't open group

{{Template:M204.0861 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T14:56:00Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0819: FTBL full, LFTBL=nnnn .. can't add GFT entry===

From v7.8 onwards, the message text for this message includes the current LFTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0819: FTBL full .. can't add GFT entry

{{Template:M204.0819 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}

New and updated messages in Model 204 version 7.8

2020-02-12T14:49:36Z

DCameron: /* M204 messages */

[[Release notes for Model 204 version 7.8|Back to release notes]]

<div class="noautonum">__TOC__</div>
This topic lists messages that were added or changed for Model 204 version 7.8.

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

==M204 messages==
===M204.0039: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0039: Request too long -- STBL

{{Template:M204.0039 footer}}

===M204.0084: Insufficient FTBL space for NGROUP, LFTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LFTBL setting as above. Prior to V7.8, the message text was as follows

M204.0084: Insufficient FTBL space for NGROUP

{{Template:M204.0084 footer}}

===M204.0141: Bug .. duplicate file name in checkpoint record===

A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. 

System manager response: Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: 
<ul>
<li>Audit trail from the previous run </li>
<li>Journal from the previous run </li>
</ul>

Operator response: Notify the system manager. 
{{Template:M204.0141 footer}}

===M204.0143: No files changed after last checkpoint, RESTART bypassed===
This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. 
{{Template:M204.0143 footer}}

===M204.0165: Missing an update unit from ICL (InComplete List)===

While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: 
<ul>
<li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
<li>A copy was not done. </li>
</ul>

System manager response: If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: 
<ul>
<li>Audit trail of the original run </li>
<li>Snap </li>
<li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
<li>UTILC of the restart data set or a copy of this data set on tape </li>
</ul>
{{Template:M204.0165 footer}}

===M204.0198: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0198: Request too long -- VTBL

{{Template:M204.0198 footer}}

===M204.0211: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0211: Request too long -- QTBL

{{Template:M204.0211 footer}}

===M204.0224: Request too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0224: Request too long -- NTBL

{{Template:M204.0224 footer}}

===M204.0226: Request too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0226: Request too long -- QTBL

{{Template:M204.0226 footer}}

===M204.0262: FSCB full, LFSCB=nnnn. Screen/Menu/Image compilation aborted===

From v7.8 onwards, the message text for this message includes the current LFSCBL setting, as above. Prior to V7.8, the message text was as follows

M204.0262: FSCB full. Screen/Menu/Image compilation aborted

{{Template:M204.0262 footer}}

===M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===

The layout of this message has been reformatted to accommodate five digit user numbers.

{{Template:M204.0352 footer}}

===M204.0442: Unable to run subsystem subsysName login procedure - GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0442: Unable to run subsystem subsysName login procedure - GTBL full 

{{Template:M204.0442 footer}}

===M204.0452: TTBL full, LTTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LTTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0452: TTBL full

{{Template:M204.0452 footer}}

===M204.0479: process group not found: processgroupname===

A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.

System manager response: The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.

Return codes: I 0 0 AUDITMS
----

===M204.0480: Invalid backpage request: backPage===

A backpage command of the form <var>P -n</var> or <var>P +n</var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:
M204.0480: Invalid backpage request: P -99(X'D74060F9F9')

Response: Correct the backpage command, or set <var>NBKPG</var> greater than 0.

{{Template:M204.0480 footer}}

===M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===

The named procedure in the named subsystem could not be made resident in resident request storage.


Response: Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.

{{Template:M204.0481 footer}}

===M204.0541:Procedure is in use: procedure===
The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. 
Response: Retry the command when the procedure is no longer in use. 
{{Template:M204.0541 footer}}

===M204.0550: Editing space exhausted -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0550: Editing space exhausted -- QTBL

{{Template:M204.0550 footer}}

===M204.0551: Request too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0551: Request too long -- STBL

{{Template:M204.0551 footer}}

===M204.0565: Can't process on token - VTBL full, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0565: Can't process on token - VTBL full

{{Template:M204.0565 footer}}

===M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
{{Template:M204.0569 footer}}

===M204.0573: Value(s) too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0573: Value(s) too long -- STBL

{{Template:M204.0573 footer}}

===M204.0574: Request too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0574: Request too long -- VTBL

{{Template:M204.0574 footer}}

===M204.0577: QTBL full, LQTBL=nnnn -- direct search===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0577: QTBL full -- direct search

{{Template:M204.0577 footer}}

===M204.0578: Too many call levels - VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0578: Too many call levels - VTBL

{{Template:M204.0578 footer}}

===M204.0735: No room for new value of global - $incrg, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0735: No room for new value of global - $incrg

{{Template:M204.0735 footer}}

===M204.0905: Value too long -- STBL, LSTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LSTBL setting as above. Prior to V7.8, the message text was as follows

M204.0905: Value too long -- STBL

{{Template:M204.0905 footer}}

===M204.0907: IFAM job too long -- QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0907: IFAM job too long -- QTBL

{{Template:M204.0907 footer}}

===M204.0911: Field or variable name list too long - QTBL, LQTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0911: Field or variable name list too long - QTBL

{{Template:M204.0911 footer}}

===M204.0916: IFAM job too long -- VTBL, LVTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0916: IFAM job too long -- VTBL

{{Template:M204.0916 footer}}

===M204.0917: IFAM job too long -- NTBL, LNTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LNTBL setting, as above. Prior to V7.8, the message text was as follows

M204.0917: IFAM job too long -- NTBL

{{Template:M204.0917 footer}}

===M204.0955 IFAM2 CRAM open error, IFAM halted - channel = chanName===

From v7.8 onwards, this message will produce an rc of 80, thus terminating the ONLINE run, should the message occur.

{{Template:M204.0955 footer}}

===M204.1070: ALLOCATE ddName failed - reason===
This message has been changed to add the ddname of the failing dataset to the message text.
{{Template:M204.1070 footer}}

===M204.1110: QTBL, LQTBL=nnnn - too small for selective type display===

From v7.8 onwards, the message text for this message includes the current LQTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1110: QTBL too small for selective type display

{{Template:M204.1110 footer}}

===M204.1124: Bump of %C %C scheduled by %C for %C user(s)===
This message has been changed to add the type of bump and the user who did so.
{{Template:M204.1124 footer}}

===M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1188: Unable to run procedure procName for subsystem subsysName-GTBL full

{{Template:M204.1188 footer}}

===M204.1342: Unable to run CCASYS procedure: TBL= ?TBL, L?TBL=nnnn===

From v7.8 onwards, the message text for this message includes the current ?TBL setting, as above, where ?TBL ( QTBL, NTBL, etc.. ) is the server table that has filled. Prior to V7.8, the message text was as follows

M204.1342: M204.1342: Unable to run CCASYS procedure: TBL= ?TBL 

{{Template:M204.1342 footer}}

===M204.1392: Soft restart of user due to %C ===
This message has been changed to add the reason and/or who caused the restart.
{{Template:M204.1392 footer}}

===M204.1500: token ===
Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.

When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:
M204.1500: CCASTAT logons not allowed
{{Template:M204.1500 footer}}

----

===M204.1592: VTBL full, LVTBL=nnnn, sorted output impossible===

From v7.8 onwards, the message text for this message includes the current LVTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1592: VTBL full, sorted output impossible

{{Template:M204.1592 footer}}

===M204.1749: Subsystem parameters lost, GTBL full, LGTBL=nnnn===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.1749: Subsystem parameters lost, GTBL full

{{Template:M204.1749 footer}}

===M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1899 footer}}

===M204.1900 User userId transferred to targetVtamName from sourceVtamName===
This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.

The change in message text is enabled within V7.7 with the application of zap 77z310.
{{Template:M204.1900 footer}}

===M204.2020 File fileName; condition?,? OPEN command rejected===
The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.

The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced

M204.2020: File filename; DDNAME not found, OPEN command rejected

{{Template:M204.2020 footer}}

===M204.2302: No room in GTBL, LGTBL=nnnn - SETGRC===

From v7.8 onwards, the message text for this message includes the current LGTBL setting, as above. Prior to V7.8, the message text was as follows

M204.2302: No room in GTBL - SETGRC

{{Template:M204.2302 footer}}

===M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===

A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
sub-transaction in progress has passed that phase of its processing during which it can be aborted.

{{Template:M204.2700 footer}}

===M204.2964 Password missing or too long===

A password string within an IFSTRTN call has not been delimited with a semicolon.


Response:
Ensure that the password string is delimited by a semicolon, as in the following example

CALL IFSTRTN(RC,'logonid;password;'...)
Version introduced:
7.8

Return codes: E 00 04 AUDITMS NOCOUNT

===M204.2965 Unable to cleanly close log file(s)===
Introduced in zap 77z243.
This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.
Response: Use the snap/dump generated by the message to diagnose the cause of the error.
Return codes: E 88 88 DUMP SNAP AUDITAD NOTERM OPR
----

===M204.2966 what line number?,? procedure proc in file file===

This message provides diagnostic information following various types of error messages. 

The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2966 messages after an error to try to diagnose the cause of the error.

{{Template:M204.2966 footer}}
----
===M204.2967 what line number of command level program===

This message provides diagnostic information after various types of error messages. 

The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. 

<var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. 

Response: Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.

{{Template:M204.2967 footer}}
----
===M204.2968 what: no debug info===

An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. 

Response: If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.

{{Template:M204.2968 footer}}
----
===M204.2969 MBSCAN (mbscan) exceeded?,? records to be searched ?=? number===

A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. 

Response: Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.

{{Template:M204.2969 footer}}
----
===M204.2970 Maximum call stack limit (limit) reached===

The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. 

Response: Examine the preceding M204.2966 messages.

{{Template:M204.2970 footer}}

==MSIR messages==
===MSIR.0942 Debugger token0 port defaulted to token2===
This message has been changed from an error message to an informational message
{{Template:MSIR.0942 footer}}