m204wiki - User contributions [en]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T15:39:51Z

Gwalter:

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

===New HDRCTL setting for DAEMONS===

==System Enhancements==
===EAV support for SIRTUNED===

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New and changed messages==

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

[[Category: Release notes]]

New and updated messages in Model 204 version 7.9

2024-01-18T15:21:59Z

Gwalter:

New and updated messages in Model 204 version 7.9

2024-01-18T15:20:56Z

Gwalter:

VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information.

[[Release_notes_for_Model_204_version_7.9_(Beta)|Release notes for Model 204 version7.9]]

[[Category: Release notes]]

New and updated messages in Model 204 version 7.9

2024-01-18T15:20:07Z

Gwalter:

VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information.

[[Release_notes_for_Model_204_version_7.9_Beta)|Release_notes_for_Model_204_version_7.9]]

[[Category: Release notes]]

New and updated messages in Model 204 version 7.9

2024-01-18T15:19:13Z

Gwalter:

VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information.

[[Release_notes_for_Model_204_version_7.9_(Beta)]]

[[Category: Release notes]]

New and updated messages in Model 204 version 7.9

2024-01-18T15:18:14Z

Gwalter:

VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information.

[[Category: Release notes]]

New and updated messages in Model 204 version 7.9

2024-01-18T15:15:34Z

Gwalter: Created page with "VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information."

VTAM Open and Close Error error messages have been enhanced to provide a great deal of additional information.

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T15:14:29Z

Gwalter: /* New and changed messages */

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

===New HDRCTL setting for DAEMONS===

==System Enhancements==

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T15:04:58Z

Gwalter: /* New in this release */

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

===New HDRCTL setting for DAEMONS===

==System Enhancements==

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T15:01:01Z

Gwalter:

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

==System Enhancements==

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T14:58:49Z

Gwalter:

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

==System Enhancements==

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New products==

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T14:56:51Z

Gwalter: /* Debugger enhancements */

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

==Operating system and hardware requirements==

===Operating system requirements===

==System Enhancements==

==Debugger enhancements==
Enhancements have been made for debugging applications that use IMAGEs to all of Model 204 debuggers (Janus Debugger, Tn3270 Debugger and SoftSpy).

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New products==

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T14:52:11Z

Gwalter: /* ATB Storage Usage Greatly Increased */

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

==Operating system and hardware requirements==

===Operating system requirements===

==System Enhancements==

==Debugger enhancements==
These enhancements apply to the Janus and TN3270 debuggers.

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===
Many more M204 data structures can be placed in ATB storage with 7.9. Probably the most important of these is the Push Down List (PDL).

==New products==

==New and changed messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.9 (Beta)

2024-01-18T14:49:52Z

Gwalter: /* Performance enhancements */

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

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

==New in this release==
===Regular expression engine enhancements===
<p>
The [[Regex processing|regular expression engine]] can now produce traces of regular expression processing to hep debug and optimize regular expressions. There are new user parameters [[REGEXTR parameter|REGEXTR]] and [[MREGEXTR parameter|MREGEXTR]], as well as a new [[Regex_processing#Common_regex_options|"t" option]] on regex method and $function invocations to control this tracing.
</p>
<p>
The regular expression engine now supports [https://www.regular-expressions.info/backref.html back references]. The following illustrates the use of a back reference (\1 in the example) to display all lines in procedure FOO where the left side of an assignment also appears on the right side. Note that this example is somewhat simplistic in that it it doesn't account for continuation lines and might not be what one wants if the left side of an assignment is an object member or array element.
</p>
<p class="code">b

%i is float
%sl is object stringlist

%sl = new
$procopn("FOO", "FOOPROC")
%sl:appendOpenProcedure

%i = 1
repeat while %i le %sl:count
%i = %sl:regexLocate("(%[a-z._$]+) *=.*\1", %i, options="i")
if %i eq 0 then loop end; end if
print %ls(%i)
%i = %i + 1
end repeat

end
</p>
===New Regex class===
<p>
Regular expressions can now be compiled into [[Regex class|Regex objects]]. This can be useful in allowing the compilations of dynamically generated regular expressions to be reused without recompilation. There is a new system parameter, [[REGXSTBL parameter|REGXSTBL]] that controls how much STBL space is to be reserved for each <var>Regex</var> object.
</p>

==Operating system and hardware requirements==

===Operating system requirements===

==System Enhancements==

==Debugger enhancements==
These enhancements apply to the Janus and TN3270 debuggers.

==Performance enhancements==
===Regex Rewrite===
<p>
The [[Regex processing|regular expression engine]] has been completely rewritten to make it significantly faster. Tests indicate simple regex is at least three times as fast as the earlier regular expression engine, and 10 times or more faster for more complex regular expressions. In addition, constant regular expressions are now compiled when the containing procedure is compiled to eliminate the runtime cost of regular expression compilation and to detect errors in regular expressions at SOUL compile-time lather than evaluation time.
</p>
===ATB Storage Usage Greatly Increased===

==New products==

==New and changed messages==

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

[[Category: Release notes]]

Category:Commands

2017-09-13T13:15:21Z

Gwalter:

The <var class="product">[[Model 204]]</var> nucleus contains a wide variety of commands, and those nucleus commands are documented here <i>along with the commands from the <var class="product">[[Sirius Mods]]</var></i>. The <var class="product">Sirius Mods</var> included [[Sirius Software product list|many products]], and <var class="product">Sirius Mods</var> customers also had access to a set of commands that appear and behave as standard <var class="product">Model 204</var> commands. Those Sirius-added commands were ''not'' part of the base <var class="product">Model 204</var> nucleus until the merging of the <var class="product">Sirius Mods</var> with the <var class="product">Model 204</var> base in <var class="product">Model 204</var> version 7.5.

Until <var class="product">Model 204</var> version 7.5, the <var class="product">Sirius Mods</var> commands and parameters are ''only'' available to customers who have installed the <var class="product">Sirius Mods</var>. And even for <var class="product">Sirius Mods</var> customers, many commands are available only at sites authorized for specific products. Other commands, while available, don't really do anything unless a site is authorized for specific products.

All commands associated with the <var class="product">Sirius Mods</var> and <var class="product">Model 204</var> are documented in this wiki. Those that Sirius added and those that are restricted to sites authorized for particular products are indicated as such in the individual command descriptions.

For a description of Model 204 command types and commands and how to use them, see the [[Overview_of_Model_204_commands|commands overview]].

<p>
For a description of <var class="product">Model 204</var>-related CMS utility command modules, which you <b>do not</b> issue from within the <var class="product">Model 204</var> environment, see [[CMS utility command modules]].</p>

M204wiki main page

2017-09-11T17:32:28Z

Gwalter:

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

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

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

__TOC__

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

M204wiki main page

2017-09-11T17:31:31Z

Gwalter:

Release notes for Model 204 version 7.7

2017-09-10T14:25:15Z

Gwalter:

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

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

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

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

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

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

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

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

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

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

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

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

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

==Operating system and hardware requirements==

===Operating system requirements===

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

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

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

===Hardware requirements===

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

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

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

===Connect<sup>★</sup> compatibility with Model 204===

Connect<span class="superstar">★</span> version 7.5 or 7.7 is compatible with Model 204 version 7.7.

For more information on Connect<span class="superstar">★</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">★</span> wiki pages]].

==SOUL (User Language) enhancements==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A simple example is:
<p class="code">assert %x gt 0, info ('abc' with 'def') </p>

<blockquote class="note">
<p><b>Note:</b> This enhancement introduces a slight backward incompatibility: An <var>Assert</var> statement like the following, whose <var>Info</var> value begins with an opening parenthesis but has no closing parenthesis, compiled without error prior to version 7.7: </p>
<p class="code">assert %x gt 0, info (</p>
<p>
From 7.7 on, such a statement produces a compilation error, because the compiler expects an expression after the open parenthesis. </p>
</blockquote>

==Security enhancements==
===Long password support===
<p>
Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters.
<br />Also, passwords and passphrases can now contain one or more embedded spaces. (Leading and trailing spaces are stripped.)</p>
<p>
The long password feature includes support for: </p>
<ul>
<li><var>[[LOGIN or LOGON command|LOGON]]</var> command</li>
<li><var>[[LOGINCP or LOGONCP command|LOGONCP]]</var> command, used to change a password</li>

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

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

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

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

<li>Long passwords (passphrases) for use with the following [[Security interfaces overview|external security interfaces]]: CA-ACF2 MVS, Security Server (formerly RACF), and CA-Top Secret</li>
</ul>
<p class="note"><b>Note:</b> This feature is available for logon passwords only; it does not apply to file passwords.</p>
<p>
No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.</p>

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

==Janus product enhancements==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<li>The automatic <var>[[JANUS WEB ALLOW]]</var> rule, which allowed any user to access the port without requiring a login, is changed <i>for non-SSL ports</i> to the following:
<p class="code">JANUS WEB <i>portname</i> DISALLOW *
</p>
<p>
This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies (after zap 77Z088 in version 7.7, or after zap 76Z418 in version 7.6) unless overridden by user-added rules.
</p>
<blockquote class="note">
<p><b>Note:</b> With version 7.7 zap 77Z090 or version 7.6 zap 76Z420, you can make the default <var>ALLOW</var> rule as it was in version 7.5 and earlier (<code>ALLOW *</code>). To do so, turn on the 1 bit of the <var>[[WEBDFLT parameter|WEBDFLT]]</var> parameter: </p>
<p class="code">RESET WEBDFLT=1</p>
</blockquote></li>

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

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

==Fast/Unload enhancements==

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

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

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

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

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

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

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

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

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

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

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

===PUT statement enhancements===


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

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

For better readability and lower CPU cost than the techniques currently used to achieve the same result, the <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<p class="code">... PUT <i>info</i> .. AS [<i>format</i>] COUNTED[1|2] </p>
<p>
For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.</p>
<p>
With this feature, you can replace FUEL code such as the following: </p>
<p class="code">%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL </p>
<p>With: </p>
<p class="code">PUT %VAL AS COUNTED2 </p>

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

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

===#STRIP function enhancements===


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

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

This argument can be conveniently combined with the
new <var>[[#Length prefix for PUT output values|COUNTED]]</var> options for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.
<p>
Combining the new fourth argument, the new <var>COUNTED2</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:</p>
<p class="code">%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</p>
<p>
You can replace the above statements by the more readable and efficient: </p>
<p class="code">PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2
</p>

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

<var>P</var> and <var>N</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the <var>#STRIP</var> first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.
<p>
<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:</p>
<p class="code">%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR %VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF </p>
<p>
You can replace the above statements with the following, which outputs a numeric value with leading zeroes stripped: </p>
<p class="code">PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2
</p>
<p class="note"><b>Note:</b> A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.</p></li>

<li id="optn">The new <var>N</var> option strips neither leading-characters nor trailing-characters.
<p>
For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</p></li>
</ul>

==New and changed commands==


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

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

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

<p class="code">M204.0509: No action taken by FREE command; <i>ddname</i> not allocated </p>
<p>
In earlier versions, no such message followed. </p>

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

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


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

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

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

<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'</p>

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

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

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

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

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

==New and changed parameters==


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

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

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

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

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

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

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

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

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

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

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

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

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>
<p>
This parameter applies to z/OS only.</p>

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

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

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

If <var>SERVSIZE</var> was not set but was [[Defining the runtime environment (CCAIN)#Sizing user server areas|calculated by the system]] to a value less than 64K, the following message is issued:
<p class="code">M204.0163: SERVSIZE increased to 65536
</p>
<p>
This change is propagated by zap maintenance to versions 7.6, 7.5, and 7.4 of Model 204. </p>

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

==Performance enhancements==

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

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

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

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

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

==Statistics enhancements==

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

For the <var>MONITOR</var> command, the [[ONLINE monitoring#User information in formatted displays|QUE column]] now reports new values OFFO and OFFI instead of OFFQ for invisible users:
<ul>
<li>OFFO is invisible and blocked out. </li>
<li>OFFI is invisible and blocked in. </li>
</ul>
<p>
The BLKO QUE value continues to mean blocked out and visible (on some queue), and BLKI means blocked in and visible.</p>

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

<p class="note"><b>Note:</b> CCATDIFF is a rough guide, not definitive: it might give false high readings for some users, but it will indicate a user whose usage is extremely extraordinary. </p>

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

==Other enhancements==

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

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

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

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

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

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

==Debugger updates==

===SoftSpy authorization===
<p>
SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.</p>
<p>
EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.</p>

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

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

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

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

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

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

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

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

==Compatibility issues==

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

<p class="code">M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative</p>

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

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

For example, the following was allowed in older versions of Model 204:
<p class="code">a: audit 'About to FDV'
fdv foo
b: frv in a</p>

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

<p class="code">M204.0311 Unacceptable statement reference</p>

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

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

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

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

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

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

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

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

==New and updated messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2017-09-10T14:24:03Z

Gwalter:

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

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

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

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

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

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

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

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

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

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

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

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

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

==Operating system and hardware requirements==

===Operating system requirements===

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

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

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

===Hardware requirements===

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

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

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

===Connect<sup>★</sup> compatibility with Model 204===

Connect<span class="superstar">★</span> version 7.5 or 7.7 is compatible with Model 204 version 7.7.

For more information on Connect<span class="superstar">★</span> installation, see the [[:Category:Connect*|Connect<span class="superstar">★</span> wiki pages]].

==SOUL (User Language) enhancements==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A simple example is:
<p class="code">assert %x gt 0, info ('abc' with 'def') </p>

<blockquote class="note">
<p><b>Note:</b> This enhancement introduces a slight backward incompatibility: An <var>Assert</var> statement like the following, whose <var>Info</var> value begins with an opening parenthesis but has no closing parenthesis, compiled without error prior to version 7.7: </p>
<p class="code">assert %x gt 0, info (</p>
<p>
From 7.7 on, such a statement produces a compilation error, because the compiler expects an expression after the open parenthesis. </p>
</blockquote>

==Security enhancements==
===Long password support===
<p>
Logon passwords, maintained in CCASTAT, can now contain as many as 127 characters.
<br />Also, passwords and passphrases can now contain one or more embedded spaces. (Leading and trailing spaces are stripped.)</p>
<p>
The long password feature includes support for: </p>
<ul>
<li><var>[[LOGIN or LOGON command|LOGON]]</var> command</li>
<li><var>[[LOGINCP or LOGONCP command|LOGONCP]]</var> command, used to change a password</li>

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

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

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

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

<li>Long passwords (passphrases) for use with the following [[Security interfaces overview|external security interfaces]]: CA-ACF2 MVS, Security Server (formerly RACF), and CA-Top Secret</li>
</ul>
<p class="note"><b>Note:</b> This feature is available for logon passwords only; it does not apply to file passwords.</p>
<p>
No changes to CCASTAT and no new CCAIN parameters are required to enable long password support.</p>

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

==Janus product enhancements==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<li>The automatic <var>[[JANUS WEB ALLOW]]</var> rule, which allowed any user to access the port without requiring a login, is changed <i>for non-SSL ports</i> to the following:
<p class="code">JANUS WEB <i>portname</i> DISALLOW *
</p>
<p>
This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
The rule applies (after zap 77Z088 in version 7.7, or after zap 76Z418 in version 7.6) unless overridden by user-added rules.
</p>
<blockquote class="note">
<p><b>Note:</b> With version 7.7 zap 77Z090 or version 7.6 zap 76Z420, you can make the default <var>ALLOW</var> rule as it was in version 7.5 and earlier (<code>ALLOW *</code>). To do so, turn on the 1 bit of the <var>[[WEBDFLT parameter|WEBDFLT]]</var> parameter: </p>
<p class="code">RESET WEBDFLT=1</p>
</blockquote></li>

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

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

==Fast/Unload enhancements==

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

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

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

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

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

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

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

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

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

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

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

===PUT statement enhancements===


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

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

For better readability and lower CPU cost than the techniques currently used to achieve the same result, the <var>AS</var> clause of a <var>PUT</var> statement will now allow the <var>COUNTED</var> keyword:
<p class="code">... PUT <i>info</i> .. AS [<i>format</i>] COUNTED[1|2] </p>
<p>
For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.</p>
<p>
With this feature, you can replace FUEL code such as the following: </p>
<p class="code">%VAL = ITEM.CODE(%OCC)
%LEN = #LEN( %VAL )
PUT %LEN AS FIXED(2)
PUT %VAL </p>
<p>With: </p>
<p class="code">PUT %VAL AS COUNTED2 </p>

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

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

===#STRIP function enhancements===


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

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

This argument can be conveniently combined with the
new <var>[[#Length prefix for PUT output values|COUNTED]]</var> options for <var>PUT</var>, because a length-prefixed format allows a reliable, unambiguous representation of a series of null strings.
<p>
Combining the new fourth argument, the new <var>COUNTED2</var> option, and the new [[#optn|N option]] of the second argument provides a simpler alternative to FUEL code such as the following:</p>
<p class="code">%VAL = ITEM.STRING(%OCC)
IF %VAL EQ '_' THEN
PUT 0 AS FIXED(2)
ELSE
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF
</p>
<p>
You can replace the above statements by the more readable and efficient: </p>
<p class="code">PUT #STRIP(ITEM.STRING(%OCC), 'N', , '_') AS COUNTED2
</p>

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

<var>P</var> and <var>N</var> strip-type options are added to the <var>#STRIP</var> function:
<ul>
<li>The new <var>P</var> option strips all but one leading <var class="term">pad</var>-argument characters from the <var>#STRIP</var> first argument returned value, if that value contains a non-zero length string of only <var class="term">pad</var> characters.
<p>
<var>P</var>, together with other new Fast/Unload <var>PUT</var> features, provides a simpler alternative to FUEL code such as the following:</p>
<p class="code">%VAL = ITEM.NUMBER(%OCC)
IF %VAL EQ '_' OR %VAL EQ '' THEN
PUT 0 AS FIXED(2)
ELSE
%VAL = #STRIP(%VAL, 'L', '0')
IF %VAL EQ '' THEN
%VAL = '0'
END IF
%LEN = #LEN(%VAL)
PUT %LEN AS FIXED(2)
PUT %VAL
END IF </p>
<p>
You can replace the above statements with the following, which outputs a numeric value with leading zeroes stripped: </p>
<p class="code">PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2
</p>
<p class="note"><b>Note:</b> A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.</p></li>

<li id="optn">The new <var>N</var> option strips neither leading-characters nor trailing-characters.
<p>
For an example, see [[#New #STRIP fourth argument|New #STRIP fourth argument]], above.</p></li>
</ul>

==New and changed commands==


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

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

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

<p class="code">M204.0509: No action taken by FREE command; <i>ddname</i> not allocated </p>
<p>
In earlier versions, no such message followed. </p>

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

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


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

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

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

<p class="code">JANUS WEB WEBPORT ON /TEST/* OPEN FILE TEST CMD 'I "M.*'</p>

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

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

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

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

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

==New and changed parameters==


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

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

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

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

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

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

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

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

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

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

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

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

<li>If started, how aggressively non-SRB MP subtasks pick up work from the zIIP offload queue. </li>
</ul>
<p>
This parameter applies to z/OS only.</p>

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

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

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

If <var>SERVSIZE</var> was not set but was [[Defining the runtime environment (CCAIN)#Sizing user server areas|calculated by the system]] to a value less than 64K, the following message is issued:
<p class="code">M204.0163: SERVSIZE increased to 65536
</p>
<p>
This change is propagated by zap maintenance to versions 7.6, 7.5, and 7.4 of Model 204. </p>

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

==Performance enhancements==

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

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

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

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

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

==Statistics enhancements==

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

For the <var>MONITOR</var> command, the [[ONLINE monitoring#User information in formatted displays|QUE column]] now reports new values OFFO and OFFI instead of OFFQ for invisible users:
<ul>
<li>OFFO is invisible and blocked out. </li>
<li>OFFI is invisible and blocked in. </li>
</ul>
<p>
The BLKO QUE value continues to mean blocked out and visible (on some queue), and BLKI means blocked in and visible.</p>

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

<p class="note"><b>Note:</b> CCATDIFF is a rough guide, not definitive: it might give false high readings for some users, but it will indicate a user whose usage is extremely extraordinary. </p>

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

==Other enhancements==

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

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

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

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

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

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

==Debugger updates==

===SoftSpy authorization===
<p>
SoftSpy and Muse are now authorized using the standard zap AUTH mechanism.</p>
<p>
EDIT CONFIG is no longer used to enter authorization keys, and the second (key entry) screen of SPY EDIT CONFIG no longer appears.</p>

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

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

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

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

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

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

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

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

==Compatibility issues==

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

<p class="code">M204.2958: APSYPAGE is obsolete as of 7.6.
Rocket recommends using RESPAGE and/or TEMPPAGE as the alternative</p>

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

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

For example, the following was allowed in older versions of Model 204:
<p class="code">a: audit 'About to FDV'
fdv foo
b: frv in a</p>

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

<p class="code">M204.0311 Unacceptable statement reference</p>

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

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

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

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

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

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

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

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

==New and updated messages==

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

[[Category: Release notes]]

Release notes for Model 204 version 7.7

2017-09-10T14:20:46Z

Gwalter:

Release notes for Model 204 version 7.7

2017-09-08T20:42:09Z

Gwalter:

Release notes for SirScan V7.7

2017-09-08T20:39:35Z

Gwalter:

This document lists the changes that have been made for <var class="product">SirScan</var> version 7.7.
<p><var class="product">SirScan</var> 7.7 is designed for use with Model 204 V7.7 and later but is backward compatible to Model 204 V7.6.</p>

<var class="product">SirScan</var> is a member of the <var class="product">[[RKTools]]</var> product family; see also the [[Release notes for RKTools V7.7|release notes for RKTools version 7.7]].

==RKWeb UI for SirScan functionality==
The [[RKWeb]] tool, new in RKTools 7.7, enables you to access SirScan journal browsing functionality using a task-based web UI. From RKWeb, you can set the journal scan specifications and then view the journal entries.
<p>The standard 3270 SirScan interface has not changed; RKWeb simply provides an easy to use, mobile-friendly alternative.</p>

<p>For more information, see the [[RKWeb#Journal Scan|Journal Scan section of RKWeb]].</p>

Release notes for SirScan V7.7

2017-09-08T20:38:45Z

Gwalter:

This document lists the changes that have been made for <var class="product">SirScan</var> version 7.7.
<p><var class="product">SirScan</var> 7.7 is designed for use with Model 204 V7.7 and later but is backward compatible to Model 204 V7.6.</p>

<var class="product">SirScan</var> is a member of the <var class="product">[[RKTools]]</var> product family; see also the [[Release notes for RKTools V7.7|release notes for RKTools version 7.7]].

==RKWeb UI for SirScan functionality==
The [[RKWeb]] tool, new in RKTools 7.7, enables you to access SirScan journal browsing functionality using a task-based web UI. From RKWeb, you can set the journal scan specifications and then view the journal entries.
<p>The standard 3270 SirScan interface has not changed; RKWeb simply provides an easy to use, mobile-friendly alternative. </p>

<p>For more information, see the [[RKWeb#Journal Scan|Journal Scan section of RKWeb]].</p>

Release notes for Model 204 version 7.7

2017-09-08T20:26:43Z

Gwalter:

Release notes for Model 204 version 7.7

2017-09-08T20:24:08Z

Gwalter:

Release notes for Model 204 version 7.7

2017-09-08T20:21:51Z

Gwalter:

What's new

2015-10-20T13:21:44Z

Gwalter: /* Janus/TN3270 Debugger Build 64 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 64 contains improvements and fixes for the Debugger Client <b>IE Mode</b> settings of <b>mergedPac</b> or <b>NewPac</b> which are used with a Microsoft IE browser.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a Microsoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:20:14Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 64 contains improvements and fixes for the Debugger Client IE Mode settings of mergedPac or NewPac which are used with a Microsoft IE browser.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a Microsoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:19:53Z

Gwalter: /* Janus/TN3270 Debugger Build 64 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 64 contains improvements and fixes for the Debugger Client IE Mode settings of mergedPac or NewPac which are used with a Microsoft IE browser.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a MicroSoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:17:43Z

Gwalter: /* Janus/TN3270 Debugger Build 64 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 64 contains improvements and fixes for the HTTP PAC feature, which is a feature
that may be used when debugging Web applications while using MS Internet Explorer.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a MicroSoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:16:56Z

Gwalter: /* Janus/TN3270 Debugger Build 64 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 64 contains improvements and fixes for the HTTP PAC feature (which is feature
that may be used when debugging Web applications while using MS Internet Explorer.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a MicroSoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:14:27Z

Gwalter:

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 63 contains

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a MicroSoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-10-20T13:13:38Z

Gwalter:

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 64==
<div class="mw-collapsible-content">
On October 7 2015, Build 64 of the Janus/TN3270 Debugger Client was released.

Build 63 contains

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 64 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/TN3270 Debugger Client was released.

Build 63 contains support for <code>HTTP:</code> style URLs for PAC (Proxy Auto Config) files, for sites
using a Debugger Client <b>IE Mode</b> setting of <b>mergedPac</b> or <b>NewPac</b> with a MicroSoft IE browser. Previously, only <code>FILE:</code> style URLs were supported for PAC files.

When Build 63 is used with Model 204 version 7.6, two additional features are available:
* Run Until, White List, and Black List processing is now done for procedures on daemon threads as well as for those on the master thread.
* The Expand Object feature supports the JSON system object type, which was added for Model 204 7.6.

Please consult the Debugger <var class="book">[[Media:JdebugrNew.pdf|User's Guide]]</var> for details (see Build 63 in the "Release Notes" chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

<p class="note"><b>Note:</b>
These features were formerly part of the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, these features were incorporated into <var class="product">Model 204</var> such that <var class="product">SOUL</var> applications continue to work as they always have. <var class="product">Janus SOAP</var> remains as an add-on product that provides support for [[Janus SOAP|XML processing]]. </p>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

What's new

2015-07-06T20:12:16Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the JSON system object type that was added for Version 7.6.

Please consult [http://m204wiki.rocketsoftware.com/images/9/91/JdebugrNew.pdf The Debugger Manual] for details (start under Build 63 in the Release Notes chapter).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:10:50Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the JSON system object type that was added for Version 7.6.

Please consult [http://m204wiki.rocketsoftware.com/images/9/91/JdebugrNew.pdf The Debugger Manual] for details (start under Build 63 in the Release Notes chapter).

</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:08:06Z

Gwalter:

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the JSON system object type that was added for Version 7.6.

Pleas consult [[http://m204wiki.rocketsoftware.com/images/9/91/JdebugrNew.pdf]] for details.

</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:02:44Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the JSON system object type that was added for Version 7.6.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:02:05Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the new JSON system object type that was added for Version 7.6.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:01:39Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6, 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK LIST processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the new JSON system object type that was added for Version 7.6.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T20:01:15Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6, 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.

When Build 63 is used with Model 204 Version 7.6, two additional features are available:
* RUN UNTIL/WHITE LIST/BLACK list processing is now done on daemon threads as well as the master thread.
* The expand object feature supports the new JSON system object type that was added for Version 7.6.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T19:58:26Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6, 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for sites
using Debugger Client IEMODE=mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T19:56:59Z

Gwalter: /* Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6, 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: style URLs for PAC (Proxy Auto Config) files, for those sites
using IEMODE mergedPac/NewPac with MSIE. Previously, only FILE: style URLs were supported for PAC files.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T19:54:33Z

Gwalter: /* Janus/TN3270 Debugger Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Build 63 with Model 204 Version 7.6==
<div class="mw-collapsible-content">
On July 6, 2015, Build 63 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: URL style PAC (Proxy Auto Config) files, for those sited
using the PAC feature with MSIE (previously, only FILE: style URLs were supported for PAC files).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

What's new

2015-07-06T19:53:18Z

Gwalter: /* Janus/TN3270 Debugger Version 7.6 */

__NOTOC__
This page contains recent and forthcoming additions of note to Model 204 documentation.

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==Janus/TN3270 Debugger Version 7.6==
<div class="mw-collapsible-content">
On July 6, 1025 Build 53 of the Janus/Tn3270 debugger client was released.

Build 63 contains support for HTTP: URL style PAC (Proxy Auto Config) files, for those sited
using the PAC feature with MSIE (previously, only FILE: style URLs were supported for PAC files).
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Fast/Unload Version 4.7==
<div class="mw-collapsible-content">
Highlights of this version include support for EAV (Extended Attribute Volume) disks,
<var>CHUNK</var> fields (introduced in version 7.5 of Model 204), and <var>FILEORG</var> X'200' (files with 48M records).

The main features in this release (December, 2014) are described in [[Release notes for Fast/Unload V4.7]].
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">

==Model 204 Version 7.5==
<div class="mw-collapsible-content">

Version 7.5 of Model 204 (December, 2014) follows the acquisition of the Sirius Software product line and integrates the Sirius and Janus software products into the Model 204 nucleus. One of the more exciting results of the integration is Simple Objective User Language, or SOUL. SOUL adds object-oriented programming to, and replaces the name of, User Language. It comes with no additional cost, and it is backward compatible with existing User Language applications.

===Release notes===
The main features in this release of Model 204 are summarized on this page and described in greater detail in the [[Release notes for Model 204 version 7.5|version 7.5 release notes]].

===SOUL===
Here are some of the new SOUL features:
<ul>
<li>Mixed case User Language support
<li>Generic User Language sorting, searching, and subsetting facilities
<li>Improved syntax for setting/retrieving large object (LOB) values (directly to/from longstrings)
<li>Enhanced printing and auditing statements
<li>Implicit concatenation
<li>The Assert and Loop Next statements
<li>A macro language
<li>Data types:
<ul>
<li>Longstring (including image string items > 255 bytes)
<li>Unicode
</ul>
<li>Full OO programming capabilities including:
<ul>
<li>Class and object definitions, methods, public/private class variables, inheritance, polymorphism, etc.
<li>Support for exceptions such as Try, Catch, and Throw statements
<li>Support for named parameters
<li>Support for method variables, that is, variables that can be used to dynamically invoke functions or subroutines
</ul>
<li>Shorthand right-side assignment operators:
<ul>
<li>%a = @ + 1
<li>%a = @ * 1
<li>%a = @ / 1
<li>%a = @ :div(1)
</ul>
</ul>

===64-bit enablement of the Model 204 infrastructure===
Model 204 moves “Above the Bar” to increase scalability, performance, and growth potential. With this release of Model 204, 64-bit addressing becomes the de-facto standard for all subsequent versions. This might bring new challenges to customers who have written assembler language functions for use within Model 204, and Rocket Software has prepared a new set of service offerings to help accommodate upgrade and conversion needs.

===Physical field groups===
Model 204 supports non-relational, denormalized data structures, and its efficient processing of multiply-occurring fields provides significant cost and performance benefits. This processing is enhanced by the availability of physical field groups, which let you view and process groups of fields as logical entities.

===Range searching by Ordered Index (OI) chunk===
The new CHUNK attribute of the DEFINE FIELD command offers significantly more efficient searching on Ordered Index numeric (ORDERED NUMERIC) field ranges. The storage for the file's values of these fields is automatically maintained, divided into ordered sub-ranges ("OI chunks") whose interval-size is part of the CHUNK definition. Finds of value ranges of these fields search by OI chunk rather than by individual value, so they entail fewer scans of the Ordered Index entries.

===Expanded file-record limit===
In version 7.5 of Model 204, the record limit per file increases from sixteen million records to forty-eight million records.

===New debugging tools===
Developing web and screen applications that use Model 204 is made easier by newly acquired debuggers: <var class="product">Janus Debugger</var>, <var class="product">TN3270 Debugger</var>, and <var class="product">SoftSpy</var>.
</div></div><br clear=all>

<div class="mw-collapsible mw-collapsed" data-expandtext="▼" data-collapsetext="▲">
==The status of Janus SOAP==
<div class="mw-collapsible-content">
<var class="product">Janus SOAP</var> was an important product in the Sirius Software product set and is still referenced frequently in the M204wiki pages. Significantly, Janus SOAP included
the Janus SOAP User Language Interface, also known as the Janus SOAP ULI. The Janus SOAP ULI was a collection of extensions to <var class="product">User Language</var> originally intended to simplify the coding of
applications that used the <var class="product">Janus SOAP</var> product. In version 7.5 of Model 204, the <var class="product">Janus SOAP ULI</var> features were incorporated into Model 204. They are the new SOUL features [[#SOUL|highlighted above]]. <var class="product">Janus SOAP</var> continues as a separate product providing support for [[Janus SOAP|XML processing]].

<blockquote class="note">
<b>Note: </b>The <var class="product">Janus SOAP ULI</var> extensions did not alter the behavior of <var class="product">User Language</var>. This is important on two counts:
<ol>
<li>When the extensions formerly known as the <var class="product">Janus SOAP ULI</var> are used, <var class="product">SOUL</var> applications continue to work as they always have.

<li>All documentation concerning <var class="product">SOUL/User Language</var> remains valid.
</ol>
</blockquote>
</div></div><br clear=all>

Debugger Client Beta documentation

2015-06-02T14:15:53Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button: </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button, and the <b>PAC Options</b> dialog is presented:</li>
[[file:PacOptions.png]]
<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>

Debugger Client Beta documentation

2015-06-02T14:15:26Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button. </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button, and the <b>PAC Options</b> dialog is presented:</li>
[[file:PacOptions.png]]
<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>

Debugger Client Beta documentation

2015-06-02T14:15:01Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button. </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button, and the PAC Options dialog is presented:</li>
[[file:PacOptions.png]]
<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>

Debugger Client Beta documentation

2015-06-02T14:14:45Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button. </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button, and the PAC Options dialog is presented.</li>
[[file:PacOptions.png]]
<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>

Debugger Client Beta documentation

2015-06-02T14:14:03Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button. </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button. </li>
[[file:PacOptions.png]]
<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>

Debugger Client Beta documentation

2015-06-02T14:13:34Z

Gwalter: /* Preferences UI changes */

==Introduction==
This page describes any beta versions of the Janus/TN3270 Debugger Workstation Client that
are available.

==Build 63, Tag 1 Beta==

===Run Until, White lists, Black lists with Daemons===
When used with Model 204 Version 7.6 and higher, Client Build 63 extends to
[[Sdaemons|sdaemon]] threads the procedure-name matching for Run Until, White List, and Black List processing that formerly ran only at the main/master thread level. For example, <code>runUntil ''desiredProc''</code> now stops if a Daemon thread includes the ''desiredProc'' procedure.

===HTTP PAC file URLs===
The Janus Debugger Client supports Proxy Auto Config (PAC) files,
providing a method to control which web requests are routed through the Janus
Debugger Client when the Internet Explorer (IE) browser is used.

IE references PAC files
with a URL. Prior to Build 63 of the Debugger Client, the Client supported only file-mode URLs (<code>file://</code>), so the PAC files it generated had to be stored on the local file system of the workstation running the Client. As of its version 11, IE is deprecating the use of file URLs for PAC files and wants HTTP (<code>http://</code>) URLs to be used. Eventually file URLs will not be supported at all, hence the need for the Client to use an HTTP URL.

The client has been modified to upload the PAC files generated in the existing "New Pac" or "Merged Pac" modes to an HTTP server. It had also been modified to set the PAC URL in IE to an HTTP-style URL that points to the PAC that was generated and uploaded.

====HTTP Server requirements/setup for PAC files====
Before changing Client settings, you must provide an HTTP (Web) server to hold the PAC files.
Any web server that supports HTTP PUT and GET may be used. This document provides an example of how to set up a Janus Web Server to handle HTTP-based PAC files. Note that the PAC files are temporary: when the Client starts, a new PAC is generated and uploaded. This prevents the
problem of HTTP PAC files being out of date, since they are based on workstation-based configuration files which can change at any time.

The following SOUL program takes one command line argument, a TCP/IP port number, and creates a Janus Web server for uploading and serving PAC files:
<p class="code">begin
variables are undefined
local subroutine closeFile(%iFile is string len 8 input)
* Close the file whose name is passed. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
$close('FILE ' with %iFile)
$resetn('MSGCTL', 0, %rc)
end subroutine
local function openFile(%iFile is string len 8 input) is float
* Open the file whose name is passed and return 0 for success or
* non-zero for failure. Messages surpressed.
%rc is float
$resetn('MSGCTL', 6, %rc)
openc file %iFile
$resetn('MSGCTL', 0, %rc)
return $status
end function
* Get and validate the command line argument: port number
%args is object stringlist
%args = %(system):arguments:unspace:parseLines(', ')
%portNumber is float
if (%args:count eq 0) then
print 'No port number specified'
stop
elseif (%args:count > 1) then
print 'Too many arguments'
stop
elseif (%args(1) is not like '/2-5(#)') then
print 'Invalid port number'
stop
else
%portNumber = %args(1)
end if
%pacRepo is string len 8 initial('JDPACREP')
%worker is object daemon auto new
%workForDaemon is object Stringlist auto new

* See if the memory file for a PAC repository is there, if not create it
if (%(local):openFile(%pacRepo) eq 0) then
printText Memory file {%pacRepo} already present
%(local):closeFile(%pacRepo)
else
printText creating memory file {%pacRepo}
text to %workForDaemon = new
ALLOCATE {%pacrepo} WITH MEMORY PAGES=300
CREATE {%pacrepo}
PARAMETER BSIZE=1, DSIZE=250
END
OPENC {%pacrepo}
IN {%pacrepo} INITIALIZE
CLOSE {%pacrepo}
end text
%worker:run(%workForDaemon):print
end if

* Set up a simple Janus web server with web rules for loading
* serving and listing PAC files generated bythe debugger client.
%portName is string len 8 initial('JDPACSRV')

* Get rid of any earlier one, so this script can be rerun as needed
text to %workForDaemon = new
JANUS DRAIN {%portName}
JANUS DELETE {%portName}
end text
%worker:run(%workForDaemon)

* Create the server and its rules
text to %workForDaemon = new
* Create a web server
JANUS DEFINE {%portName} {%portNumber} WEBSERV 20 TRACE 7
* Allow upload of PAC files via HTTP PUT of a URL of format /pacman/xxx.js
JANUS WEB {%portName} ON PUT /PACMAN/*.JS OPEN FILE {%pacRepo} RECV *.JS BASE64
JANUS WEB {%portName} ALLOW PUT /PACMAN/*.JS
* Provide HTTP GET access for URLs of format /pacman/xxx.js
JANUS WEB {%portName} ON GET /PACMAN/*.JS OPEN FILE {%pacRepo} -
SEND *.JS BINARY EXPIRE +0
* Start the web server
JANUS START {%portName}
end text
%worker:run(%workForDaemon):print
end</p>
Since the PAC files are temporary, they are stored in a memory file (not persistent between runs). This also means that this procedure does not need any disk files, DD cards, etc. The PAC files are stored as Model 204 procedures. The PAC file procedures created by the Client (see the following sections), have names based on the IP number of the Client workstation to avoid conflicts.

====DebuggerConfig.xml changes====
Once the HTTP server is set up to accept and serve PAC files, the Debugger Client configuration
must be updated to identify it. This is done with the new <var>httpPacURL</var> tag in the debuggerConfig.xml file:
<p class="syntax"><debuggerConfig version="1.0">
<httpPacURL>http://''pacServerHost'':''pacServerPort''/pacman</httpPacURL></p>
Where:
<ul>
<li><var class="term">pacServerHost</var> is the host name or IP number of the PAC Janus Web Server described above. </li>

<li><var class="term"> pacServerPort</var> is the port number passed the to SOUL program shown above. </li>
</ul>

When the Debugger Client is started, and <code>httpPacURL</code> is specified in the configuration, it is validated.
Validation consists of HTTP PUT and GET of a test file. If there is a problem with <var>httpPacURL</var>, an error is displayed in the Audit tab.

====Preferences UI changes====
Once the server has been set up and the client configuration includes <code>httpPacURL</code>, you enable the HTTP Pac feature through user preferences:
<ol>
<li>Start the client. </li>

<li>Select <code>File > preferences</code>. </li>

<li>Select <code>newPac</code> or <code>mergedPac</code> for an IE Mode; this enables the <b>PAC Options</b> button. </li>
[[file:IeOptions.png]]
<li>Click the <b>PAC Options</b> button. </li>

<li>Select <code>file://</code> or <code>http://</code> mode for the PAC URL. </li>
</ol>

As an alternative, you can use the <var>setIEMode</var> command, which is enhanced to support this feature.

====SetIeMode command changes====
If a <var>setIEMode</var> command specifies a PAC mode (newPac or mergedPac), you may
specify <code>file</code> or <code>http</code> to control which type of PAC URL is used. <code>file</code> is the default:
<p class="code">setIeMode {none|proxy|newPac|mergedPac} [<u>file</u>|http]</p>

====ShowIE command changes====
<var>ShowIE</var> output has been enhanced to display URL info for any PAC file in use by the Debugger Client. For example:
<p class="code">Current ie mode: mergedPac
Current ie settings
...Proxy flags=(5)
...Proxy server=()
...Proxy bypass=()
...Proxy autoConfigUrl=(http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS)
...Raw flag byte=(05)
...Read from registry
key=(HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings)
Generated New Pac file: c:\debugger\stateFiles\debuggerInternalPac.js
Added: 54 web servers from the configuration.
Generated Pac File:
''Pac file shown here''
pacURLMode: http <== New line
httpPacUrl='http://''pacServerHost'':''pacServerPort''/pacman/' <== New line
httpPac upload filename: 'PAC.10.111.2.82.JS' <== New line</p>

====RetryHTTPPac command====
If you have an error on the validation of the HTTP PAC server when you bring up the client, and then fix the HTTP Server, you can issue the <var>RetryHTTPPAC</var> command from the client as an alternative to restarting the client.

====&&currentPacFile function added====
The <var>&&currentPacFile</var> function returns the URL of the PAC file in use or <code>""</code> if none. The URL returned could be either a <code>file:</code> or <code>http:</code> URL.
<p class="code">Command: echo &&currentPacFile
Macro message:
http://''pacServerHost'':''pacServerPort''/pacman/PAC.10.111.2.82.JS</p>

====Other new commands====
As part of developing and testing the HTTP URL support, three additional commands were added which may also be of general use:
<ul>
<li><code>httpPutFile ''file url''</code> — Do an HTTP PUT file upload for the file and URL specified </li>

<li><code>httpPutString ''string url''</code> — Do an HTTP PUT file upload for the string and URL specified </li>

<li><code>httpGet ''file url''</code> — Do an HTTP GET for the URL specified, display in console </li>
</ul>