m204wiki - User contributions [en]

Release notes for Model 204 version 7.5

2014-03-31T17:13:16Z

LGradus:

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

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

==New in this release==
This section summarizes the new features and enhancements for Model 204 version 7.5.0.

===SOUL (User Language)===
The significantly enhanced, object-oriented, version of User Language is now called SOUL. All existing User Language programs will continue to work under SOUL, so User Language can be considered to be a subset of SOUL, though the name "User Language" is now deprecated.
<ul>
<li>Sirius object-oriented language extensions integration</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|ECF]] statements can pass up to 60 parameters</li>
</ul>

===System Management===
<ul>
<li>Writing records to the SMF data set without an SVC installed</li>
</ul>

===Performance===
<ul>
<li>GTBL can be stored above the bar</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]]</li>
</ul>

==Operating system requirements==
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the following operating system support:
<ul>
<li>For IBM z/OS: Version 1 Release 7 is sufficient for all new functionality except for the following
features:
<ul>
<li>Large (1 MB) page support requires Version 1 Release 9.
<li>Extended address volumes (EAV) requires Version 1 Release 12.
</ul>
<li>For IBM z/VM: Version 5 Release 4.0 or later
<li>For IBM z/VSE:
<ul>
<li>Version 5 Release 1 or
<li>Version 4 Release 3 or
<li>Version 4 Release 2.1 or
<li>Version 4 Release 2.0, with these program temporary fixes (PTFs) installed:
<ul>
<li>UD53436
<li>UD53437
<li>UD53438
<li>UD53439
</ul>
</ul>
</ul>

=== Hardware requirements ===
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the IBM z/890 or above processor, except for the following feature:

The large (1 MB) page support feature requires the IBM z10 or above processor. 

===Model 204 compatibility with operating systems===
Content for version 7.5 is still to be determined.
For information on Model 204 certification with IBM operating systems, see:
http://www.rocketsoftware.com/products/rocket-model-204/technical-information

===Model 204 compatibility with Connect*===
All supported versions of Connect* are compatible with Model 204 version 7.5.0.
However, CLOB/BLOB support requires Connect* version 7.4.0 or higher. Use of Connect* versions earlier than version 7.4.0 to SELECT, UPDATE, or INSERT CLOB/BLOB data will fail and might produce unexpected application behavior and/or return an error.
Connect* version 7.5.0 is compatible with versions of Model 204 that are earlier than version 7.5.0.

==SOUL (User Language) enhancements==
Much of the substantial new and enhanced functionality described in the following subsections is available as a result of the acquisition of Sirius Software. The functionality that is the subject of the initial subsection, "Object oriented programming," motivates the new name for User Language, '''SOUL''', often thought of as Simple Objective User Language.

===Object oriented programming===
As of version 7.5 of Model 204 (and backward compatible with existing User Language applications), the SOUL language is equipped with [http://en.wikipedia.org/wiki/Object-oriented Object-Oriented Programming](sometimes abbreviated OO) capabilities comparable or superior to other contemporary object oriented languages. The OO features were formerly contained in the [[Janus SOAP User Language Interface]], and you can use [[Object oriented programming in SOUL]] as an entry point to the extensive SOUL OO documentation. In particular, you might want to begin with the [[Getting started with OOP for User Language programmers|OO tutorial]].

===Record capacity increase===
In this version of Model 204, the record limit is increased from sixteen million records to forty-eight million records per file.

===New SOUL statements===
{{Template:User Language statements}}

===Non-OO enhancements in SOUL===
{{Template:User Language syntax enhancements}}

===SOUL support for field groups===

====ADD (or INSERT or DELETE) FIELDGROUP statements====
The <var>ADD FIELDGROUP</var> statement and the <var>INSERT FIELDGROUP</var> statement behavior parallels the behavior of the <var>ADD</var> and <var>INSERT</var> statements for simple fields. The <var>DELETE FIELDGROUP</var> statement handles more situations and is therefore more complex.
See [[Data maintenance#Updating field groups|Updating field groups]] for details.

====Statements for handling field groups====
SOUL now provides several statements for handling field groups:
<ul>
<li><var>FOR FIELDGROUP</var></li>
<li><var>FOR ALL OCCURRENCES OF FIELDGROUP (FAO FIELDGROUP)</var></li>
<li><var>FOR EACH OCCURRENCE OF FIELDGROUP (FEO FIELDGROUP)</var></li>
</ul>

See [[Operations on multiply occurring fields#Special statements for multiply occurring fields and field groups|Special statements for multiply occurring fields and field groups]] for details.

====Output statements for field groups====

The following SOUL statements provide display output for Model 204 field groups:
AUDIT ALL FIELDGROUP INFORMATION (AAFGI)
PRINT ALL FIELDGROUP INFORMATION (PAFGI)


See [[Basic SOUL statements and commands#Output statements|Output statements]] for details.

====Field group SORT support====
You can use field groups in [[Sorting#Field group SORT support|sorted sets]]. <var>SORT</var> statement support for field groups lets you sort records with field groups as well as reference field groups in the sorted sets. For example, you can issue a <code>FAO FIELDGROUP</code> statement or <code>FEO FIELDGROUP</code> statement against the sorted set.

===EQ VALUE retrieval condition===

SOUL now provides the <var>EQ VALUE</var> clause to support expressions in <var>FIND</var> statements.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] for details.

===EQ WITH retrieval condition for concatenated fields===
SOUL now provides the <var>EQ WITH</var> clause for retrieving <var>CONCATENATION-OF</var> fields. Model 204 automatically builds the concatenated value.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] and [[Record retrievals#EQ WITH retrieval condition for concatenated fields|EQ with retrieval condition for concatenated fields]] for details.

===External Call Facility (ECF)===
<var>EXTERNAL CALL</var> statements can now pass more parameters.
The maximum number of parameters that can be passed in an <var>EXTERNAL CALL</var> statement has been increased from 40 to 60.
The maximum value setting for <var>[[ECPSIZE parameter|ECPSIZE]]<var> is increased from 1310680 to 1966020 to accommodate the extra parameters.

ECF is available only on z/OS systems. For more information about the External Call Facility and the <var>EXTERNAL CALL</var> statement, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

===REPEAT statement UNTIL option===
The <var>REPEAT</var> statement now supports the <var>UNTIL</var> option. In previous releases, only <var>REPEAT WHILE</var> was supported.

A <var>[[Flow of control in User Language#REPEAT UNTIL statement|REPEAT UNTIL]]</var> statement enters the loop body prior to checking the condition.

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

====New HttpRequest TranslateTable property====
The <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property makes it possible to set the translate table to be used for EBCDIC to ASCII translation of data in an <var>HttpRequest</var> object.

====New InvalidTranslateTable class====
Objects of the [[InvalidTranslateTable class|InvalidTranslateTable exception class]] are thrown when a requested system translate table cannot be found. It is currently thrown only by the <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property.

====New bit manipulation String functions====
New bit manipulation functions <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitCountString (String function)|BitCountString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, <var>[[BitSetString (String function)|BitSetString]]</var>, and <var>[[BitValueString (String function)|BitValueString]]</var> make it easier to manipulate the bits in a string.

====New InvalidBitNumber class====
Objects of the [[InvalidBitNumber class|InvalidBitNumber exception class]] are thrown when an invalid bit number is requested by a bit manipulation function. It is currently thrown only by the <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, [[BitSetString (String function)|BitSetString]], and <var>[[BitValueString (String function)|BitValueString]]</var> functions.

====Disable base64 encoding in LoadFromRecord and related methods====
The <var>Base64Encode</var>=<var>False</var> argument can be used with the <var>[[LoadFromRecord (XmlDoc/XmlNode subroutine)|LoadFromRecord]]</var> method to disable any base64 encoding of field values.

Alternatively, the <var>CharacterMap</var> argument (with a non-null value) can be used to disable any base64 encoding of field values, and to specify translations, which can avoid request translation due to X'00' and/or untranslatable characters in field values.

These arguments are also added to the <var>[[NewFromRecord (XmlDoc function)|NewFromRecord]]</var> and <var>[[ToXmlDoc (Record function)|ToXmlDoc]]</var> methods.

====New option for AppendJournalData====
The <var>QT</var> option is added to the <var>[[AppendJournalData (Stringlist function)#Options parameter|AppendJournalData]]</var> method, to include QT type audit entries.

====New parameter for AddField====
The <var>Strip</var> option is added to the <var>Screen</var> class method <var>[[AddField (Screen function)|AddField]]</var> to allow suppression of leading and trailing blank removal from input fields.

===New and changed $functions===

====Former Sirius $functions====
The $functions referred to by the link below are added to SOUL as a result of the acquisition of Sirius Software:
:[[List of $functions|Sirius $functions]]

====$SNDMAIL attachment ASCII translation====
The <var>$SNDMAIL</var> function can now translate an attachment to ASCII before sending it.
This translation is useful if the <var>$SNDMAIL</var> attachment is a <var>CLOB</var> (<var>CHARACTER-LARGE-OBJECT</var>) such as a text document.

The <var>$SNDMAIL</var> function now accepts an optional parameter after the name of the attached object. If this parameter is set to 'C' (or to a percent variable with the value 'C'), the object in the buffer is translated to ASCII before being attached to the email.

If this parameter is not specified, the object in the buffer is sent as a binary object.

In this example:
%RC = $SNDMAIL(%SUBJECT,,%BODY,%FROM,%TO,,,,'CLOB.TXT','C')

the <code>CLOB.TXT</code> attachment will be translated to ASCII before being attached to the email.

====New function calls for field groups====
When a field group is added, a [[Data maintenance#Updating field groups|field group ID]] is assigned to the field group.
<ul>
<li><var>[[$FIELDGROUPID]]</var> returns the ID of the current field group.</li>
<li><var>[[$FIELDGROUPOCCURRENCE]]</var> returns the current occurrence number of the field group.</li>
</ul>

==Sirius products and product enhancements==
[[Sirius Software product list|The former-Sirius products]] are now available to Model 204 customers as separately purchased items as a result of the acquisition of Sirius Software.

===Changes to Janus SSL support===
Under Model 204 version 7.5, Janus products:

<ul>
<li>Drop support for version 2 of the Secure Sockets Layer encryption protocol (SSL V2)

You can use the <var>[[SSLPROT parameter|SSLPROT]]</var> parameter on the <var>JANUS DEFINE</var> command for a port to explicitly specify, or limit, the SSL protocols available for a connection. The <var>SSLPROT</var> documentation describes the SSL protocols that Janus supports. 

Janus support for SSL V2 also included an option to specify a larger than "legal" input buffer for connections not strictly conforming to the V2 standard. You specify that buffer size with the <var>JANUS DEFINE</var> <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter, and the <var>SSLIBSIZE</var> maximum value as of Model 204 V7.5 is reduced (from 32767 bytes) to the SSL maximum allowed size of 16384. </li>

<li>Add support for new ciphers and TLS levels

You can use the <var>[[SSLCIPH parameter|SSLCIPH]]</var> <var>JANUS DEFINE</var> parameter to specify the SSL ciphers available for a connection. The <var>SSLCIPH</var> documentation describes the SSL ciphers that Janus supports. </li>
</ul>

===WEBOPT parameter change===
The <var>[[WEBOPT parameter|WEBOPT]]</var> parameter default value is changed to X'03' from 0. <var>WEBOPT</var> affects the interaction of Model 204 and RACF security.

==File-related enhancements==

===Support for physical field groups===
Model 204 supports non-relational, de-normalized data structures. Many Model 204 sites have enjoyed significant cost and performance benefits from efficiently processing multiply occurring fields. This concept has been enhanced to introduce physical field groups that let you view and process groups of fields as a logical entity.

You can define a physical field group only for files with the [[#FILEORG (new settings)|FILEORG X'100' setting]]. To take advantage of field groups in files defined before Model 204 version 7.5, you must reorganize the files with a <var>FILEORG</var> setting that includes the X'100' bit.

Files with <var>FILEORG</var> X'100' can have up to 32,000 fields.

For more information, see [[Field group design (File management)|field group design]].

===Increased Table B record number capacity===
[[Table B (File architecture)|Table B]] can now contain up to 48M possible record numbers. (The previous limit was 16M.)

Set the [[#FILEORG (new settings)|FILEORG X'200' bit]] at file creation time to allow for the increased record numbers.
<blockquote class="note">
Notes: 
<ul>
<li>The limit for <var>BSIZE</var> remains at 16M.

<code>BSIZE * BRECPPG</code> must be less than or equal to 48M (actually decimal 50,331,648 to be exact). 

For example, if <var>BSIZE</var> is 16M, <var>BRECPPG</var> cannot be more than 3. </li>

<li>The <var>FILEORG</var> X'200' bit cannot be set for files with hash key or sorted file organization.</li>
</ul>
</blockquote>

===Automatic fields===
Model 204 now lets you define a field whose value is [[Field design (File management)#Automatic fields|automatically maintained]]. A field can count occurrences of another field so that every store or delete of the field occurrence changes the count in the automatic field. Automatic fields are defined with the following attributes:
<ul>
<li><var>COUNT-OCCURRENCES-OF</var></li>
<li><var>CREATE-TIME</var></li>
<li><var>CREATE-TIMEUTC</var></li>
<li><var>CREATE-USER</var></li>
<li><var>UPDATE-TIME</var></li>
<li><var>UPDATE-TIMEUTC</var></li>
<li><var>UPDATE-USER</var></li>
</ul>

The value of an automatic field is updated at the start of a transaction by Model 204 and you cannot set it explicitly by a program. Any valid update statement causes the appropriate time and user stamps to be updated. For example, the time and user stamps will be undated when <code>DELETE FOO(8)</code> is processed, even if there are no occurrences of FOO in the record and an actual update does not take place.

Once you define an automatic value for a field, you cannot redefine the automatic value.

===Concatenated fields===
Model 204 now lets you define [[Field design (File management)#Concatenated fields|concatenated fields]].

Fields that make up concatenated field values must be <var>AT-MOST-ONE</var>, <var>EXACTLY-ONE</var>, or <var>OCCURS</var> 1 and must all be in the same field group context (or not in a field group). Fields that occur in all field groups (<var>FIELDGROUP *</var>) cannot be used in a concatenation.

If a concatenated field becomes longer than 255 bytes after adding separator and escape characters, the update request is cancelled.

===New field attributes===
Model 204 version 7.5 introduces the new <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> attributes described in this section. These attributes apply to all fields in Model 204. 

Note: These attributes all require that the <var>[[FILEORG parameter|FILEORG]]</var> parameter X'100' bit must be set on the file containing the fields.

Changes in the new field attributes are detected during the redefinition of an existing field. When such a change is detected, the following messages might be issued:
M204.1260: [FIELD | FIELDGROUP] WAS PREVIOUSLY DEFINED WITH DIFFERENT ATTRIBUTES,
NEW [FIELD | FIELDGROUP] OPTIONS IGNORED

or
M204.2884: [FIELD WAS PREVIOUSLY DEFINED AS A FIELDGROUP | FIELDGROUP WAS PREVIOUSLY
DEFINED AS A FIELD], NEW DEFINITION IGNORED


The table below lists the new field attributes. 
<table>
<tr class="head">
<th>Attribute</th><th>Abbreviation</th><th>Description</th>
</tr>

<tr>
<td>[[DEFINE_FIELD_command#Ordered_index_CHUNK_attribute|CHUNK]]</td>
<td>CNK</td>
<td>Defines "OI chunks" of data in Ordered Index numeric range fields to enable more efficient searching.</td>
</tr>

<tr>
<td>[[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF]]</td>
<td>(CAT)</td>
<td>Lists the fields that make up a concatenated field</td>
</tr>

<tr>
<td nowrap>[[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF]]</td>
<td>(CTO)</td>
<td>Automatically maintains a count of the number of occurrences of the specified field.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIME]]</td>
<td>(CRTM)</td>
<td>Captures the time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIMEUTC]]</td>
<td>(CRTMU)</td>
<td>Captures the Coordinated Universal Time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-USER]]</td>
<td>(CRUS)</td>
<td>Captures the user ID of the user who created the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME]]</td>
<td>(DT)</td>
<td>Specifies the format of the date and time data stored in Table B. The default is YYYYMMDDHHMISSXXXXXX.</td>
</tr>

<tr><td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GE]]</td>
<td>(DTGE)</td>
<td>With DATETIME-GT, DATETIME-LE, and DATETIME-LT, used to establish a range for date/time values. Specifies that the date/time value must be later than or the same as the date/time value that follows. </td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GT]]</td>
<td>(DTGT)</td>
<td>Specifies that the date/time value must be later than the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LE]]</td>
<td>(DTLE)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LT]]</td>
<td>(DELT)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DEFAULT-VALUE .28DV.29 attribute|DEFAULT-VALUE]]</td>
<td>(DV)</td>
<td>Specifies the value to use for the field when the record is created and no value has been assigned to the field.

(The value of the STORE-DEFAULT setting determines whether the DEFAULT-VALUE is physically stored on the record or if it is just used as the default value when the field is missing.)</td>
</tr>

<tr>
<td>[[Field design (File management)#ESCAPE .28ESC.29 attribute|ESCAPE]]</td>
<td>(ESC)</td>
<td>Specifies an escape character to insert before separator and escape characters in a concatenated field, differentiating those characters from real data. The default value is X’01’.</td>
</tr>

<tr>
<td>[[Field design (File management)#AT-MOST-ONE.2C REPEATABLE and EXACTLY-ONE attributes|EXACTLY-ONE]]</td>
<td>(EXONE)</td>
<td>Specifies that a field always has exactly one occurrence in its record or field group context. The default value is 1.</td>
</tr>

<tr><td>[[Field design (File management)#FIELDGROUP attribute|FIELDGROUP]]</td>
<td>(FG)</td>
<td>Specifies the name of the field group that the defined field is associated with (contained in).</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GE]]</td>
<td>(FLTGE)</td>
<td>With FLOAT-GT, FLOAT-LE, and FLOAT-LT, used to establish a range for float values when defining a field. Specifies that the float value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GT]]</td>
<td>(FLTGT)</td>
<td>Specifies that the float value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LE]]</td>
<td>(FLTLE)</td>
<td>Specifies that the float value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LT]]</td>
<td>(FLTLT)</td>
<td>Specifies that the float value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GE]]</td>
<td>(INTGE)</td>
<td>With INTEGER-GT, INTEGER-LE, and INTEGER-LT, used to establish a range for integer values when defining a field. Specifies that the integer value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GT]]</td>
<td>(INTGT)</td>
<td>Specifies that the integer value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LE]]</td>
<td>(INTLE)</td>
<td>Specifies that the integer value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LT]]</td>
<td>(INTLT)</td>
<td>Specifies that the integer value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-EQ .28LEQ.29 attribute|LENGTH-EQ]]</td>
<td>(LEQ)</td>
<td>Used to set a length constraint when defining a field. Specifies the required length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-GE .28LGE.29 attribute|LENGTH-GE]]</td>
<td>(LGE)</td>
<td>Specifies the minimum length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-LE .28LLE.29 attribute|LENGTH-LE]]</td>
<td>(LLE)</td>
<td>Specifies the maximum length of a field.</td>
</tr>

<tr><td>[[Field design (File management)#Setting a pattern for a field value: the LIKE attribute|LIKE]]</td>
<td>(LK)</td>
<td>Sets a pattern that a field value must conform to.</td>
</tr>

<tr>
<td>[[Field design (File management)#BLOB.2C CLOB.2C and MINLOBE attributes|MINLOBE]]</td>
<td>(MLBE)</td>
<td>Defines the minimum size of a BLOB or CLOB field value that will be stored in Table E. This avoids wasting Table E pages on small values that could be stored in Table B (or Table X). The default is 0.</td>
</tr>

<tr>
<td>NO-DOMAIN-CONSTRAINTS</td>
<td/>
<td>Specifies that the field has no [[Field design (File management)#Content constraints|content constraint]] attributes. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove existing constraints on a field.</td>
</tr>

<tr>
<td>NO-DEFAULT-VALUE</td>
<td>(NDV)</td>
<td>Specifies that the field has no default value. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove an existing default value on a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#SEPARATOR .28SEP.29 attribute|SEPARATOR]]</td>
<td>(SEP)</td>
<td>Specifies a separator character used between field values in concatenated fields. The default is X’00’.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-DEFAULT]]</td>
<td>(SD)</td>
<td>Specifies whether to physically store the default value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-NULL]]</td>
<td>(SN)</td>
<td>Specifies whether to physically store the null value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIME]]</td>
<td>(UPTM)</td>
<td>Captures the time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIMEUTC]]</td>
<td>(UPTMU)</td>
<td>Captures the Coordinated Universal Time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-USER]]</td>
<td>(UPUS)</td>
<td>Captures the user ID of the user who updated the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-8]]</td>
<td>(UTF8)</td>
<td>Data is stored in UTF-8 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-16]]</td>
<td>(UTF16)</td>
<td>Data is stored in UTF-16 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>
</table>

==System management enhancements==

===Writing records to the SMF data set===
Having Model 204 write records to the SMF data set no longer requires the installation of an SVC.

Therefore, the <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is no longer required and, if present, will be ignored and flagged with the following informational message:
M204.0204: PARAMETER SMFSVC OBSOLETE AND NOT RESET
However, the <var>[[SMFLORN parameter|SMFLORN]]</var> and <var>[[SMFSLRN parameter|SMFSLRN]]</var> parameters must still be present in CCAIN if SMF records are required.

==Performance enhancements==

===64-bit addressing and Above The Bar (ATB) storage===
Model 204 moves above the (2G) 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.

In addition to the ATB support for FTBL released with Model 204 version 7.4, version 7.5 adds ATB support for GTBL, NTBL, and QTBL, using the same <var>[[SERVNSA parameter|SERVNSA]]</var> and <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameters used for FTBL.

When using non-swappable ATB server space, each user will get SERVNSSZ bytes of ATB space, even if the thread is logged out or running resident requests. For greater efficiency, Model 204 version 7.5 also provides swappable ATB server areas that can supplement or replace the non-swappable areas. These swappable ATB server areas are controlled by the <var>[[SERVGA parameter|SERVGA]]</var> and <var>[[SERVGSZ parameter|SERVGSZ]]</var> parameters.

====GTBL, NTBL, QTBL in above the bar storage====
GTBL, NTBL and QTBL can now be placed into swappable or non-swappable server storage area above the bar.
In order to store a table in ATB storage:
<ul>
<li>Increase the <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameter by the corresponding table size.
<li>Set the proper bit in <var>[[SERVNSA parameter|SERVNSA]]</var>:
<ul>
<li>for GTBL set the second byte to <code>X’80’</code>, so the value of <var>SERVNSA</var> is <code>X'00800000'</code></li>
<li>for NTBL set the third byte to <code>X’40’</code>, so the value of <var>SERVNSA</var> is <code>X'00004000'</code></li>
<li>for QTBL set the third byte to <code>X’20’</code>, so the value of <var>SERVNSA</var> is <code>X'00002000'</code></li>
</ul>
</ul>
'''Note:'''
The settings for each server table above the bar are independent of each other.
So if FTBL, GTBL, NTBL , and, QTBL are all placed above the bar, then <var>SERVNSA</var> should be set to <code>X'02806000'</code>.

====XmlDoc pages in above the bar buffer pool====
With this release, the CCATEMP pages used for <var>XmlDoc</var> objects use the above the bar buffer pool, which may allow the below the bar buffer pool to be reduced, perhaps providing more storage for server areas. It also may provide a reduction in CPU utilization, especially when the <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> parameter is used to allocate CCATEMP in memory.

===Improved range searching by Ordered Index (OI) chunk===
The new <var>[[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK]]</var> attribute for the <var>DEFINE FIELD</var> command enables more efficient range searching on Ordered Index numeric (<var>ORDERED NUMERIC</var>) fields. <var>CHUNK</var> improves performance of the <var>FIND</var> statement <var>RANGE</var> and <var>BETWEEN</var> terms. The <var>CHUNK</var> field attribute defines a subrange ("OI chunk") of the data range. Searching by OI chunks on a range of data requires fewer scans of the ordered index entries to find the desired data. Once OI chunk fields are defined, they are automatically used by FIND processing, so no application code needs to be changed.

After defining an <var>ORDERED NUMERIC</var> field, you define one or more related OI chunk fields containing data from the original base field rounded down by a specified <var>CHUNK</var> size.

Example:
DEFINE FIELD YYYYMMDD WITH ORDERED NUMERIC
DEFINE FIELD YYYYMM WITH ORDERED NUMERIC INVISIBLE CHUNK 100 FOR YYYYMMDD
DEFINE FIELD YYYY WITH ORDERED NUMERIC INVISIBLE CHUNK 10000 FOR YYYYMMDD


<var>CHUNK</var> requires the <var>[[#FILEORG (new settings)|FILEORG]]</var> X'100' bit setting and the <var>INVISIBLE</var> and <var>ORDERED NUMERIC</var> field attributes.

==Debugging and testing enhancements==
The SoftSpy debugging, testing, and performance tuning product is now included as part of the Model 204 core product. For more information on SoftSpy release 7.5, see the [[SoftSpy 7.5 release notes]].

==MQ/204 enhancements==

===Freeing MQ/204 subtasks and associated storage===
The new <var>MQDELDTP</var> PST (pseudo subtask) checks for MQ/204 subtasks that are in a delayed detach state. <var>MQDELDTP</var> detaches MQ/204 subtasks that have finished their work and releases their associated storage areas.

==Other features==
===AT-MOST-ONE and field groups===

The <var>AT-MOST-ONE</var> attribute is now applicable to a field group definition.

===Storing and updating LOBs===

All large object data (LOBs) in a <var>FILEORG</var> X'100' file are chained. There are four bytes per Table E page overhead for chained LOBs. The pages used by a chained LOB are not contiguous.


Handling LOBs in <var>FILEORG</var> X'100' files also has the following effects:
<ul>
<li>LOBs can be changed as needed. The <var>RESERVE</var> clause is ignored in a LOB field <var>ADD</var> statement processing, as well as the <var>STORE RECORD</var> statement processing of fieldname=value pairs. Consequently, the <var>CHANGE</var> statement does not fail because of insufficient reserved space. If the <var>CHANGE</var> statement requires that a LOB field be extended, it is.</li>

<li>The value of the <var>[[EHIGHPG parameter|EHIGHPG]]</var> parameter is always one less than the high water mark of the number of pages used to hold LOBs. (Unless none were ever added, in which case it is zero, not -1).</li>

<li>The value of the <var>[[EPGSUSED parameter|EPGSUSED]]</var> parameter is always the number of pages currently being used to hold LOBs.</li>

<li>The <var>COMPACTE</var> command does not process <var>FILEORG</var> X'100' files, just as it does not process a file created in V6R1 or earlier. Thus, issuing a <var>COMPACTE</var> command for a <var>FILEORG</var> X'100' file produces an error message.</li>

<li>The <var>TABLEE</var> command is effectively executinga <code>VIEW ESIZE EHIGHPG EPGSUSED</code> command for a <var>FILEORG</var> X'100' file. Consequently there are no <var>TABLEE</var> overhead pages in a <var>FILEORG</var> X'100' file.</li>
</ul>

===Constraint attributes===
You can set range constraints on fields using the constraint attributes. Each set of range attributes is comprised of four attributes (<var>GE</var>, <var>GT</var>, <var>LE</var>, <var>LT</var>) that you can use to establish a range for integer values, float values, or date-time stamp values. The types of range attributes are mutually exclusive. For example, you cannot define a field with the <var>FLOAT-GE</var> and <var>INTEGER-LE</var> attributes.

If a range constraint is redefined, it replaces the existing field constraint.

 Note: 
The range constraints do not have to match the data type of the stored field. That is, you could have a date-time constraint for a <var>STRING</var> field or an integer constraint for a <var>FLOAT</var> field, and so on.

You can set the following constraint attributes:
<ul>
<li>date-time value</li>
<li>pattern for a field value</li>
<li>length</li>
<li>integer value</li>
</ul>

See [[Field design (File management)#Content constraints|Content constraints]] for details.

===Changes to journal record layouts===
Four bytes have been added to the journal record header for user statistic entries:
1 byte to hold the <var>IODEV</var> number and 3 bytes for future use.

All user since-last statistics (LAST=) lines will now show the <var>IODEV</var> value:
ST $$$ USERID='<var class="term">userid</var>' ACCOUNT='<var class="term">accountname</var>' IODEV='<var class="term">devicetype</var>' LAST='<var class="term">acty</var>'

For more information on journal records and user statistics, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

==Compatibility issues==
This section describes any compatibility issues between V7.5 and prior versions of Model 204.
An incompatibility arises if an operation that was previously performed without any indication of error, now operates (given the same inputs and conditions) in a different manner.

A normal bug fix resolving behavior that, although not indicating an error, was "clearly and obviously" incorrect, also introduces an incompatibility, but it might not be included below.

===Change to the Ordered Index layout===
Formerly all ORDERED NUMERIC fields came after all ORDERED CHARACTER fields in the Ordered Index. Now, the fields are interspersed in field code order.

===ZFIELD Image===
The [[ZFIELD image detail as of Model 204 V7.5|ZFIELD image]] has been updated for this release. The image is used with $LSTFLD and $FDEF function calls. One change is that FDEF is now longer (to accommodate FDEF1, LOOPVAR, and FDEF2).

===INTERCOMM is no longer supported===
The INTERCOMM interface supports the use of Teletype and 3270 terminals in line-at-a-time mode, using the Model 204 IODEV=29 thread type.

INTERCOMM is no longer supported as of Model 204 version 7.5.

See the <var class="book">Rocket Model 204 Terminal User's Guide</var> for a discussion of terminal interfaces.

===User PDL overflow===
The new <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter might require you to increase the size of the user Push Down List (using UTABLE LPDLST) by up to 3072 bytes, or more if you specify a value for SEQPDL that is larger than the 4096 default value.

===LPDLST parameter maximum value===
The maximum value for the <var>[[LPDLST parameter|LPDLST]]</var> parameter has been increased from 32760 to 65536.

===SSLIBSIZE parameter maximum value===
The maximum value for the <var>JANUS DEFINE</var> command <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter has been decreased from 32767 to 16384.

==New and changed commands==

===DECREASE (new option: DYNAMIC)===
The DYNAMIC option on the <var>[[DECREASE command|DECREASE]]</var> command lets you decrease Table B dynamically, even if the file is open by others or has requests compiled against it.

===DEFINE DATASET (new parameter: GDGRECNT)===
The GDGRECNT parameter for the <var>[[DEFINE DATASET command|DEFINE DATASET]]</var> command causes Model 204 to check the catalog information for the latest relative GDG generation number whenever allocating a GDG data set.

===DEFINE FIELD (new or changed attributes)===
In Model 204 version 7.5, the <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> command has new attributes information:
<ul>
<li>the new <var>[[#Improved range searching by Ordered Index .28OI.29 chunk|CHUNK]]</var> attribute, which improves the efficiency of range finds using ordered index processing</li>
<li>many other <var>[[FILEORG parameter|FILEORG=x'100']]</var> related new or changed [[Release notes for Model 204 version 7.5 (DRAFT)#New field attributes|field attributes]]</li>
</ul>

===DEFINE FIELDGROUP (new in V7.5)===
The <var>[[DEFINE FIELDGROUP command|DEFINE FIELDGROUP]]</var> command establishes the contents of a field group, including the fields and field groups associated with the field group being defined.

===DELETE FIELD (changed to handle CAT and CTO fields)===
The <var>[[DELETE FIELD command|DELETE FIELD]]</var> command has been changed to take [[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF (CAT)]] and [[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF (CTO)]] fields into account. DELETE FIELD does not allow deletion of fields referred to by an existing CAT or CTO field.

===DELETE FIELDGROUP (new in V7.5)===
The <var>[[DELETE FIELDGROUP command|DELETE FIELDGROUP]]</var> command deletes a field group from a Model 204 file.

===DISPLAY FIELD (new option: COMMA)===
In Model 204 version 7.5, the <var>[[DISPLAY FIELD command|DISPLAY FIELD]]</var> command has added
the <var>COMMA</var> option, which uses commas to separate displayed field attributes.

===DISPLAY MODMAP (new in V7.5)===
<var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> displays the Model 204 link map in address order. System manager privileges are required.

===REGENERATE and REGENERATE ONEPASS (improved TO UPDATE option)===
The TO UPDATE option of the <var>[[REGENERATE command|REGENERATE]]</var> and <var>[[REGENERATE ONEPASS command|REGENERATE ONEPASS]]</var> commands can now handle multiple files.
If TO UPDATE <var class="term">nn</var> OF <var class="term">id</var> is specified, it must appear only on the first FILE statement, and no other ‘TO’ options are allowed on subsequent files.
All additional files will be recovered as though they each specified the same 'TO UPDATE' option. Once the 'end of transaction' is reached, further processing will stop and all inflight transactions will be backed out.

===RENAME FIELDGROUP (new in V7.5)===
The <var>[[RENAME FIELDGROUP command|RENAME FIELDGROUP]]</var> command changes the name of a field group.

===UNICODE (new codepage: 1154)===
The <var>[[UNICODE command|UNICODE]]</var> command now accepts 1154 as a codepage name. This codepage has 92 Unicode characters in the range U+0400 through U+045F, representing the Basic Russian alphabet and all of the Cyrillic extensions excepting the four which have grave accents.


==Reliability enhancements==
===SEQPDL parameter===
The new <var>[[SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List (PDL) in order for the SOUL sequencer to proceed with the next quad code. The minimum and default value is 4096 bytes. The maximum value is 8192 bytes. SEQPDL is a user resettable parameter and can be set on the user's parameter line or reset with the UTABLE command.

Formerly 1024 bytes of PDL free space were hardcoded internally in the Model 204 core. With 1024 bytes there were edge cases where abends would break files, resulting in ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED. SEQPDL is provided to allow enough PDL space so that all of the lower level journaling routines can process error conditions without breaking files.

If your applications are using close to the amount of PDL space currently set by the LPDLST value, you might need to increase LPDLST to reflect SEQPDL's increase in free space.

==New and changed parameters==
In addition to the following specific parameter changes, <var class="product">Model 204</var> parameter descriptions, for example as displayed by the <var>VIEW</var> command, are now in mixed case (unless translated to uppercase due to <var>[[#UPCASMSG (new in V7.5)|UPCASMSG]]</var>.)

Note: The [[Sirius Mods]] parameters are merged with the <var class="product">Model 204</var> base as of <var class="product">Model 204</var> version 7.5, and they are available to all version 7.5 customers. The combined set of parameters is displayed on the [[List of Model 204 parameters]] page. The former Sirius parameters in that listing are marked with an (S). 


===DEFCNTX and APDFCNTX (for $View function only, new in V7.5)===
The string
<code>DEFCNTX</code> or <code>APDFCNTX</code> can be used as an
argument to the <var>[[$VIEW|$View]]</var> function to
get the default file or group context. Using these strings is better than using <code>$View('CURFILE')</code> because:
<ul>
<li><code>CURFILE</code> returns a null string if the default context is a group.

<li><code>CURFILE</code> is affected by the <var>IN</var> clause prior to a <var>Begin</var> command and
can be affected by the <var>In</var> clause prior to many SOUL statements.
</ul>

If there is no default context, <code>$View('DEFCNTX')</code> returns a null
string.

Otherwise <code>$View('DEFCNTX')</code> returns the type of context (<code>FILE</code>, <code>TEMP GROUP</code>, or
<code>PERM GROUP</code>) followed by the file or group name, with trailing blanks
removed.

<code>$View('APDFCNTX')</code> returns the same information based on the default
context when the APSY was entered.

Note: These <code>$View</code> arguments were implemented as part of
maintenance to version 7.5 (via zap number 54). They are not available as ordinary parameters on the <var>VIEW</var> command.
In version 7.6 of Model 204,
they will also be available with the <var>VIEW</var> command.


===DSPOPT (change to default setting)===
The default setting for [[DSPOPT parameter|DSPOPT]] has been changed from X'00' to X'01'. The X'01' setting allocates space for servers in memory in chunks of 4K pages, not as a permanent contiguous area. This allocation lets you move fewer 4K pages, keeping the virtual storage allocated for servers in memory less fragmented and possibly using fewer paging tables.

===ECPSIZE (change to max value)===
The maximum value setting for [[ECPSIZE parameter|ECPSIZE]] has been increased from 1310680 to 1966020 to accommodate more [[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|External Call Facility]] parameters.

===FILEORG (new settings)===
<ul>
<li>
The <var>[[FILEORG parameter|FILEORG]] X'100'</var> setting for enhanced data handling files is now available.

X'100' enables a number of enhancements to the file structure, including: 
<ul>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]] </li>

<li>The definition of as many as 32000 fields in a file </li>

<li>System maintained [[Field design (File management)#Automatic Fields|Automatic fields]] </li>

<li>[[Field design (File management)#Field constraints|Field constraints]] providing content validation </li>

<li>Improved space management of fields containing [[Field design (File management)#BLOB, CLOB, and MINLOBE attributes|Large Objects]] </li>

<li>[[#New field attributes|New DEFINE FIELD attributes]], such as <var>CHUNK</var>
</ul>

If X'100' is selected, the X'80' bit (optimized field extraction files) is automatically set.</li>

<li>The <var>FILEORG X'200'</var> setting for large file support is now available. </li>

X'200' allows files to hold up to 48 million records.
</li>
</ul>

===FISTAT (change to X'08' setting)===
The <var>[[FISTAT parameter|FISTAT]] X'08'</var> (file full) setting is now automatically cleared in a transaction back out file if table D is increased enough so that DSIZE is greater than or equal to DPGSRES+DPGSUSED.

===LRETBL (setting increase may be necessary)===
Because there might be a slight increase in record locking table usage in V7.5, an increase in the value of the <var>[[LRETBL parameter|LRETBL]]</var> parameter is advised. The amount of the increase is best estimated by multiplying by 16 the <code>HWM HEADERS</code> value (from a <var>[[MONITOR ENQ command|MONITOR ENQ]]</var> report), then dividing by the value of the <var>NUSERS</var> parameter. For example, if <code>HWM HEADERS = 100000</code> and <code>NUSERS=2000</code>, the recommended <var>LRETBL</var> increase is <code>16*100000/2000</code>, or 800.

===MISCOPT (obsolete)===
The <var>[[MISCOPT parameter|MISCOPT]]</var> parameter is now obsolete. In Model 204 version 7.5, MISCOPT is still viewable but is not resettable.

===MODTIM (new in V7.5)===
The <var>[[MODTIM parameter|MODTIM]]</var> system parameter displays the most recent assembly date and time of the Model 204 load module.

===OUTPUT (change to allow OUTPUT=DUMMY)===
IODEV=3 threads definitions now allow OUTPUT=DUMMY.
When defining IODEV=3 threads, if output is not required, the OUTPUT parameter can be coded as OUTPUT=DUMMY.
For example:
IODEV=3,INPUT=IOD3IN1,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN2,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN3,OUTPUT=DUMMY
and so on.

This means that no DD statement is required for the output data set, and in cases where many
IODEV=3 threads are defined to simulate a large number of users, this enhancement will reduce the number of DD statements required by one half.

===RECLOCKO (X'04' bit now ignored)===
The <var>[[RECLOCKO parameter|RECLOCKO]]</var> X'04' bit is now ignored, and the extra information of the conflicting user number and lock time are now always available.

===RESPAGE (new in V7.5)===
The <var>[[RESPAGE parameter|RESPAGE]]</var> parameter activates the APSY Precompiled Procedures in storage feature using above the bar pages by specifying a number of 4K operating system pages.

===RETRVKEY (change to allow forward retrieve PF key)===
New in this release, if you specify a non-zero setting of <var>[[RETRVKEY parameter|RETRVKEY]]</var>:
<ul>
<li>If you have set the <code>X'01'</code> or <code>X'10'</code> bits of the <var>[[RETRVOPT parameter|RETRVOPT]]</var> parameter, you can use a
forward retrieve PF key, in addition to the backward retrieve PF key specified by <var>RETRVKEY</var>.
'''Note:'''
If either of these bits is set, the <code>X'02'</code> bit is strongly recommended as well.
<li>The size of the allocated storage area, and hence the number and length of input lines available for retrieval, is specified
by the value of the <var>[[RETRVBUF parameter|RETRVBUF]]</var> parameter.</ul>

===SEQPDL (new in V7.5)===
The <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List in order for the SOUL sequencer to proceed with the next quad code. SEQPDL allows enough PDL space for the lower level journaling routines to handle error conditions properly without breaking files and causing ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED.

===SESMAXTO (new in V7.5)===
The <var>[[SESMAXTO parameter|SESMAXTO]]</var> parameter can be used limit the maximum [[Sessions|session]] timeout value or to cause all current closed sessions to be immediately discarded.

===SMFSVC (obsolete)===
The <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is [[Release notes for Model 204 version 7.5 (DRAFT)#Writing records to the SMF data set|obsolete]] as of Model 204 version 7.5.

===UPCASMSG (new in V7.5)===
The <var>[[UPCASMSG parameter|UPCASMSG]]</var> parameter can be used to translate messages issued by <var class="product">Model 204</var> to uppercase; otherwise (depending on the message being issued) they are displayed in mixed (upper and lower) case.




==Documentation conversion==
Rocket Model 204 documentation is being converted from individual manuals in PDF format to a set of cross-linked HTML articles in this integrated wiki, M204wiki.

As of Model 204 release 7.5, several manuals are now in wiki format and the rest remain in PDF format, available from the [http://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm Rocket Software Documentation Library].

For details, see [[Model 204 and Sirius documentation]].

==New and updated messages==

Many messages have been updated and added in this release. See [[New and updated messages in Model 204 version 7.5]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.5

2014-03-28T17:43:32Z

LGradus: /* NTBL and QTBL in above the bar storage */

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

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

==New in this release==
This section summarizes the new features and enhancements for Model 204 version 7.5.0.

===SOUL (User Language)===
The significantly enhanced, object-oriented, version of User Language is now called SOUL. All existing User Language programs will continue to work under SOUL, so User Language can be considered to be a subset of SOUL, though the name "User Language" is now deprecated.
<ul>
<li>Sirius object-oriented language extensions integration</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|ECF]] statements can pass up to 60 parameters</li>
</ul>

===System Management===
<ul>
<li>Writing records to the SMF data set without an SVC installed</li>
</ul>

===Performance===
<ul>
<li>GTBL can be stored above the bar</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]]</li>
</ul>

==Operating system requirements==
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the following operating system support:
<ul>
<li>For IBM z/OS: Version 1 Release 7 is sufficient for all new functionality except for the following
features:
<ul>
<li>Large (1 MB) page support requires Version 1 Release 9.
<li>Extended address volumes (EAV) requires Version 1 Release 12.
</ul>
<li>For IBM z/VM: Version 5 Release 4.0 or later
<li>For IBM z/VSE:
<ul>
<li>Version 5 Release 1 or
<li>Version 4 Release 3 or
<li>Version 4 Release 2.1 or
<li>Version 4 Release 2.0, with these program temporary fixes (PTFs) installed:
<ul>
<li>UD53436
<li>UD53437
<li>UD53438
<li>UD53439
</ul>
</ul>
</ul>

=== Hardware requirements ===
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the IBM z/890 or above processor, except for the following feature:

The large (1 MB) page support feature requires the IBM z10 or above processor. 

===Model 204 compatibility with operating systems===
Content for version 7.5 is still to be determined.
For information on Model 204 certification with IBM operating systems, see:
http://www.rocketsoftware.com/products/rocket-model-204/technical-information

===Model 204 compatibility with Connect*===
All supported versions of Connect* are compatible with Model 204 version 7.5.0.
However, CLOB/BLOB support requires Connect* version 7.4.0 or higher. Use of Connect* versions earlier than version 7.4.0 to SELECT, UPDATE, or INSERT CLOB/BLOB data will fail and might produce unexpected application behavior and/or return an error.
Connect* version 7.5.0 is compatible with versions of Model 204 that are earlier than version 7.5.0.

==SOUL (User Language) enhancements==
Much of the substantial new and enhanced functionality described in the following subsections is available as a result of the acquisition of Sirius Software. The functionality that is the subject of the initial subsection, "Object oriented programming," motivates the new name for User Language, '''SOUL''', often thought of as Simple Objective User Language.

===Object oriented programming===
As of version 7.5 of Model 204 (and backward compatible with existing User Language applications), the SOUL language is equipped with [http://en.wikipedia.org/wiki/Object-oriented Object-Oriented Programming](sometimes abbreviated OO) capabilities comparable or superior to other contemporary object oriented languages. The OO features were formerly contained in the [[Janus SOAP User Language Interface]], and you can use [[Object oriented programming in SOUL]] as an entry point to the extensive SOUL OO documentation. In particular, you might want to begin with the [[Getting started with OOP for User Language programmers|OO tutorial]].

===Record capacity increase===
In this version of Model 204, the record limit is increased from sixteen million records to forty-eight million records per file.

===New SOUL statements===
{{Template:User Language statements}}

===Non-OO enhancements in SOUL===
{{Template:User Language syntax enhancements}}

===SOUL support for field groups===

====ADD (or INSERT or DELETE) FIELDGROUP statements====
The <var>ADD FIELDGROUP</var> statement and the <var>INSERT FIELDGROUP</var> statement behavior parallels the behavior of the <var>ADD</var> and <var>INSERT</var> statements for simple fields. The <var>DELETE FIELDGROUP</var> statement handles more situations and is therefore more complex.
See [[Data maintenance#Updating field groups|Updating field groups]] for details.

====Statements for handling field groups====
SOUL now provides several statements for handling field groups:
<ul>
<li><var>FOR FIELDGROUP</var></li>
<li><var>FOR ALL OCCURRENCES OF FIELDGROUP (FAO FIELDGROUP)</var></li>
<li><var>FOR EACH OCCURRENCE OF FIELDGROUP (FEO FIELDGROUP)</var></li>
</ul>

See [[Operations on multiply occurring fields#Special statements for multiply occurring fields and field groups|Special statements for multiply occurring fields and field groups]] for details.

====Output statements for field groups====

The following SOUL statements provide display output for Model 204 field groups:
AUDIT ALL FIELDGROUP INFORMATION (AAFGI)
PRINT ALL FIELDGROUP INFORMATION (PAFGI)


See [[Basic SOUL statements and commands#Output statements|Output statements]] for details.

====Field group SORT support====
You can use field groups in [[Sorting#Field group SORT support|sorted sets]]. <var>SORT</var> statement support for field groups lets you sort records with field groups as well as reference field groups in the sorted sets. For example, you can issue a <code>FAO FIELDGROUP</code> statement or <code>FEO FIELDGROUP</code> statement against the sorted set.

===EQ VALUE retrieval condition===

SOUL now provides the <var>EQ VALUE</var> clause to support expressions in <var>FIND</var> statements.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] for details.

===EQ WITH retrieval condition for concatenated fields===
SOUL now provides the <var>EQ WITH</var> clause for retrieving <var>CONCATENATION-OF</var> fields. Model 204 automatically builds the concatenated value.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] and [[Record retrievals#EQ WITH retrieval condition for concatenated fields|EQ with retrieval condition for concatenated fields]] for details.

===External Call Facility (ECF)===
<var>EXTERNAL CALL</var> statements can now pass more parameters.
The maximum number of parameters that can be passed in an <var>EXTERNAL CALL</var> statement has been increased from 40 to 60.
The maximum value setting for <var>[[ECPSIZE parameter|ECPSIZE]]<var> is increased from 1310680 to 1966020 to accommodate the extra parameters.

ECF is available only on z/OS systems. For more information about the External Call Facility and the <var>EXTERNAL CALL</var> statement, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

===REPEAT statement UNTIL option===
The <var>REPEAT</var> statement now supports the <var>UNTIL</var> option. In previous releases, only <var>REPEAT WHILE</var> was supported.

A <var>[[Flow of control in User Language#REPEAT UNTIL statement|REPEAT UNTIL]]</var> statement enters the loop body prior to checking the condition.

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

====New HttpRequest TranslateTable property====
The <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property makes it possible to set the translate table to be used for EBCDIC to ASCII translation of data in an <var>HttpRequest</var> object.

====New InvalidTranslateTable class====
Objects of the [[InvalidTranslateTable class|InvalidTranslateTable exception class]] are thrown when a requested system translate table cannot be found. It is currently thrown only by the <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property.

====New bit manipulation String functions====
New bit manipulation functions <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitCountString (String function)|BitCountString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, <var>[[BitSetString (String function)|BitSetString]]</var>, and <var>[[BitValueString (String function)|BitValueString]]</var> make it easier to manipulate the bits in a string.

====New InvalidBitNumber class====
Objects of the [[InvalidBitNumber class|InvalidBitNumber exception class]] are thrown when an invalid bit number is requested by a bit manipulation function. It is currently thrown only by the <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, [[BitSetString (String function)|BitSetString]], and <var>[[BitValueString (String function)|BitValueString]]</var> functions.

====Disable base64 encoding in LoadFromRecord and related methods====
The <var>Base64Encode</var>=<var>False</var> argument can be used with the <var>[[LoadFromRecord (XmlDoc/XmlNode subroutine)|LoadFromRecord]]</var> method to disable any base64 encoding of field values.

Alternatively, the <var>CharacterMap</var> argument (with a non-null value) can be used to disable any base64 encoding of field values, and to specify translations, which can avoid request translation due to X'00' and/or untranslatable characters in field values.

These arguments are also added to the <var>[[NewFromRecord (XmlDoc function)|NewFromRecord]]</var> and <var>[[ToXmlDoc (Record function)|ToXmlDoc]]</var> methods.

====New option for AppendJournalData====
The <var>QT</var> option is added to the <var>[[AppendJournalData (Stringlist function)#Options parameter|AppendJournalData]]</var> method, to include QT type audit entries.

====New parameter for AddField====
The <var>Strip</var> option is added to the <var>Screen</var> class method <var>[[AddField (Screen function)|AddField]]</var> to allow suppression of leading and trailing blank removal from input fields.

===New and changed $functions===

====Former Sirius $functions====
The $functions referred to by the link below are added to SOUL as a result of the acquisition of Sirius Software:
:[[List of $functions|Sirius $functions]]

====$SNDMAIL attachment ASCII translation====
The <var>$SNDMAIL</var> function can now translate an attachment to ASCII before sending it.
This translation is useful if the <var>$SNDMAIL</var> attachment is a <var>CLOB</var> (<var>CHARACTER-LARGE-OBJECT</var>) such as a text document.

The <var>$SNDMAIL</var> function now accepts an optional parameter after the name of the attached object. If this parameter is set to 'C' (or to a percent variable with the value 'C'), the object in the buffer is translated to ASCII before being attached to the email.

If this parameter is not specified, the object in the buffer is sent as a binary object.

In this example:
%RC = $SNDMAIL(%SUBJECT,,%BODY,%FROM,%TO,,,,'CLOB.TXT','C')

the <code>CLOB.TXT</code> attachment will be translated to ASCII before being attached to the email.

====New function calls for field groups====
When a field group is added, a [[Data maintenance#Updating field groups|field group ID]] is assigned to the field group.
<ul>
<li><var>[[$FIELDGROUPID]]</var> returns the ID of the current field group.</li>
<li><var>[[$FIELDGROUPOCCURRENCE]]</var> returns the current occurrence number of the field group.</li>
</ul>

==Sirius products and product enhancements==
[[Sirius Software product list|The former-Sirius products]] are now available to Model 204 customers as separately purchased items as a result of the acquisition of Sirius Software.

===Changes to Janus SSL support===
Under Model 204 version 7.5, Janus products:

<ul>
<li>Drop support for version 2 of the Secure Sockets Layer encryption protocol (SSL V2)

You can use the <var>[[SSLPROT parameter|SSLPROT]]</var> parameter on the <var>JANUS DEFINE</var> command for a port to explicitly specify, or limit, the SSL protocols available for a connection. The <var>SSLPROT</var> documentation describes the SSL protocols that Janus supports. 

Janus support for SSL V2 also included an option to specify a larger than "legal" input buffer for connections not strictly conforming to the V2 standard. You specify that buffer size with the <var>JANUS DEFINE</var> <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter, and the <var>SSLIBSIZE</var> maximum value as of Model 204 V7.5 is reduced (from 32767 bytes) to the SSL maximum allowed size of 16384. </li>

<li>Add support for new ciphers and TLS levels

You can use the <var>[[SSLCIPH parameter|SSLCIPH]]</var> <var>JANUS DEFINE</var> parameter to specify the SSL ciphers available for a connection. The <var>SSLCIPH</var> documentation describes the SSL ciphers that Janus supports. </li>
</ul>

===WEBOPT parameter change===
The <var>[[WEBOPT parameter|WEBOPT]]</var> parameter default value is changed to X'03' from 0. <var>WEBOPT</var> affects the interaction of Model 204 and RACF security.

==File-related enhancements==

===Support for physical field groups===
Model 204 supports non-relational, de-normalized data structures. Many Model 204 sites have enjoyed significant cost and performance benefits from efficiently processing multiply occurring fields. This concept has been enhanced to introduce physical field groups that let you view and process groups of fields as a logical entity.

You can define a physical field group only for files with the [[#FILEORG (new settings)|FILEORG X'100' setting]]. To take advantage of field groups in files defined before Model 204 version 7.5, you must reorganize the files with a <var>FILEORG</var> setting that includes the X'100' bit.

Files with <var>FILEORG</var> X'100' can have up to 32,000 fields.

For more information, see [[Field group design (File management)|field group design]].

===Increased Table B record number capacity===
[[Table B (File architecture)|Table B]] can now contain up to 48M possible record numbers. (The previous limit was 16M.)

Set the [[#FILEORG (new settings)|FILEORG X'200' bit]] at file creation time to allow for the increased record numbers.
<blockquote class="note">
Notes: 
<ul>
<li>The limit for <var>BSIZE</var> remains at 16M.

<code>BSIZE * BRECPPG</code> must be less than or equal to 48M (actually decimal 50,331,648 to be exact). 

For example, if <var>BSIZE</var> is 16M, <var>BRECPPG</var> cannot be more than 3. </li>

<li>The <var>FILEORG</var> X'200' bit cannot be set for files with hash key or sorted file organization.</li>
</ul>
</blockquote>

===Automatic fields===
Model 204 now lets you define a field whose value is [[Field design (File management)#Automatic fields|automatically maintained]]. A field can count occurrences of another field so that every store or delete of the field occurrence changes the count in the automatic field. Automatic fields are defined with the following attributes:
<ul>
<li><var>COUNT-OCCURRENCES-OF</var></li>
<li><var>CREATE-TIME</var></li>
<li><var>CREATE-TIMEUTC</var></li>
<li><var>CREATE-USER</var></li>
<li><var>UPDATE-TIME</var></li>
<li><var>UPDATE-TIMEUTC</var></li>
<li><var>UPDATE-USER</var></li>
</ul>

The value of an automatic field is updated at the start of a transaction by Model 204 and you cannot set it explicitly by a program. Any valid update statement causes the appropriate time and user stamps to be updated. For example, the time and user stamps will be undated when <code>DELETE FOO(8)</code> is processed, even if there are no occurrences of FOO in the record and an actual update does not take place.

Once you define an automatic value for a field, you cannot redefine the automatic value.

===Concatenated fields===
Model 204 now lets you define [[Field design (File management)#Concatenated fields|concatenated fields]].

Fields that make up concatenated field values must be <var>AT-MOST-ONE</var>, <var>EXACTLY-ONE</var>, or <var>OCCURS</var> 1 and must all be in the same field group context (or not in a field group). Fields that occur in all field groups (<var>FIELDGROUP *</var>) cannot be used in a concatenation.

If a concatenated field becomes longer than 255 bytes after adding separator and escape characters, the update request is cancelled.

===New field attributes===
Model 204 version 7.5 introduces the new <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> attributes described in this section. These attributes apply to all fields in Model 204. 

Note: These attributes all require that the <var>[[FILEORG parameter|FILEORG]]</var> parameter X'100' bit must be set on the file containing the fields.

Changes in the new field attributes are detected during the redefinition of an existing field. When such a change is detected, the following messages might be issued:
M204.1260: [FIELD | FIELDGROUP] WAS PREVIOUSLY DEFINED WITH DIFFERENT ATTRIBUTES,
NEW [FIELD | FIELDGROUP] OPTIONS IGNORED

or
M204.2884: [FIELD WAS PREVIOUSLY DEFINED AS A FIELDGROUP | FIELDGROUP WAS PREVIOUSLY
DEFINED AS A FIELD], NEW DEFINITION IGNORED


The table below lists the new field attributes. 
<table>
<tr class="head">
<th>Attribute</th><th>Abbreviation</th><th>Description</th>
</tr>

<tr>
<td>[[DEFINE_FIELD_command#Ordered_index_CHUNK_attribute|CHUNK]]</td>
<td>CNK</td>
<td>Defines "OI chunks" of data in Ordered Index numeric range fields to enable more efficient searching.</td>
</tr>

<tr>
<td>[[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF]]</td>
<td>(CAT)</td>
<td>Lists the fields that make up a concatenated field</td>
</tr>

<tr>
<td nowrap>[[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF]]</td>
<td>(CTO)</td>
<td>Automatically maintains a count of the number of occurrences of the specified field.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIME]]</td>
<td>(CRTM)</td>
<td>Captures the time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIMEUTC]]</td>
<td>(CRTMU)</td>
<td>Captures the Coordinated Universal Time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-USER]]</td>
<td>(CRUS)</td>
<td>Captures the user ID of the user who created the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME]]</td>
<td>(DT)</td>
<td>Specifies the format of the date and time data stored in Table B. The default is YYYYMMDDHHMISSXXXXXX.</td>
</tr>

<tr><td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GE]]</td>
<td>(DTGE)</td>
<td>With DATETIME-GT, DATETIME-LE, and DATETIME-LT, used to establish a range for date/time values. Specifies that the date/time value must be later than or the same as the date/time value that follows. </td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GT]]</td>
<td>(DTGT)</td>
<td>Specifies that the date/time value must be later than the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LE]]</td>
<td>(DTLE)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LT]]</td>
<td>(DELT)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DEFAULT-VALUE .28DV.29 attribute|DEFAULT-VALUE]]</td>
<td>(DV)</td>
<td>Specifies the value to use for the field when the record is created and no value has been assigned to the field.

(The value of the STORE-DEFAULT setting determines whether the DEFAULT-VALUE is physically stored on the record or if it is just used as the default value when the field is missing.)</td>
</tr>

<tr>
<td>[[Field design (File management)#ESCAPE .28ESC.29 attribute|ESCAPE]]</td>
<td>(ESC)</td>
<td>Specifies an escape character to insert before separator and escape characters in a concatenated field, differentiating those characters from real data. The default value is X’01’.</td>
</tr>

<tr>
<td>[[Field design (File management)#AT-MOST-ONE.2C REPEATABLE and EXACTLY-ONE attributes|EXACTLY-ONE]]</td>
<td>(EXONE)</td>
<td>Specifies that a field always has exactly one occurrence in its record or field group context. The default value is 1.</td>
</tr>

<tr><td>[[Field design (File management)#FIELDGROUP attribute|FIELDGROUP]]</td>
<td>(FG)</td>
<td>Specifies the name of the field group that the defined field is associated with (contained in).</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GE]]</td>
<td>(FLTGE)</td>
<td>With FLOAT-GT, FLOAT-LE, and FLOAT-LT, used to establish a range for float values when defining a field. Specifies that the float value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GT]]</td>
<td>(FLTGT)</td>
<td>Specifies that the float value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LE]]</td>
<td>(FLTLE)</td>
<td>Specifies that the float value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LT]]</td>
<td>(FLTLT)</td>
<td>Specifies that the float value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GE]]</td>
<td>(INTGE)</td>
<td>With INTEGER-GT, INTEGER-LE, and INTEGER-LT, used to establish a range for integer values when defining a field. Specifies that the integer value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GT]]</td>
<td>(INTGT)</td>
<td>Specifies that the integer value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LE]]</td>
<td>(INTLE)</td>
<td>Specifies that the integer value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LT]]</td>
<td>(INTLT)</td>
<td>Specifies that the integer value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-EQ .28LEQ.29 attribute|LENGTH-EQ]]</td>
<td>(LEQ)</td>
<td>Used to set a length constraint when defining a field. Specifies the required length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-GE .28LGE.29 attribute|LENGTH-GE]]</td>
<td>(LGE)</td>
<td>Specifies the minimum length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-LE .28LLE.29 attribute|LENGTH-LE]]</td>
<td>(LLE)</td>
<td>Specifies the maximum length of a field.</td>
</tr>

<tr><td>[[Field design (File management)#Setting a pattern for a field value: the LIKE attribute|LIKE]]</td>
<td>(LK)</td>
<td>Sets a pattern that a field value must conform to.</td>
</tr>

<tr>
<td>[[Field design (File management)#BLOB.2C CLOB.2C and MINLOBE attributes|MINLOBE]]</td>
<td>(MLBE)</td>
<td>Defines the minimum size of a BLOB or CLOB field value that will be stored in Table E. This avoids wasting Table E pages on small values that could be stored in Table B (or Table X). The default is 0.</td>
</tr>

<tr>
<td>NO-DOMAIN-CONSTRAINTS</td>
<td/>
<td>Specifies that the field has no [[Field design (File management)#Content constraints|content constraint]] attributes. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove existing constraints on a field.</td>
</tr>

<tr>
<td>NO-DEFAULT-VALUE</td>
<td>(NDV)</td>
<td>Specifies that the field has no default value. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove an existing default value on a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#SEPARATOR .28SEP.29 attribute|SEPARATOR]]</td>
<td>(SEP)</td>
<td>Specifies a separator character used between field values in concatenated fields. The default is X’00’.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-DEFAULT]]</td>
<td>(SD)</td>
<td>Specifies whether to physically store the default value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-NULL]]</td>
<td>(SN)</td>
<td>Specifies whether to physically store the null value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIME]]</td>
<td>(UPTM)</td>
<td>Captures the time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIMEUTC]]</td>
<td>(UPTMU)</td>
<td>Captures the Coordinated Universal Time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-USER]]</td>
<td>(UPUS)</td>
<td>Captures the user ID of the user who updated the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-8]]</td>
<td>(UTF8)</td>
<td>Data is stored in UTF-8 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-16]]</td>
<td>(UTF16)</td>
<td>Data is stored in UTF-16 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>
</table>

==System management enhancements==

===Writing records to the SMF data set===
Having Model 204 write records to the SMF data set no longer requires the installation of an SVC.

Therefore, the <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is no longer required and, if present, will be ignored and flagged with the following informational message:
M204.0204: PARAMETER SMFSVC OBSOLETE AND NOT RESET
However, the <var>[[SMFLORN parameter|SMFLORN]]</var> and <var>[[SMFSLRN parameter|SMFSLRN]]</var> parameters must still be present in CCAIN if SMF records are required.

==Performance enhancements==

===64-bit addressing and Above The Bar (ATB) storage===
Model 204 moves above the (2G) 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.

In addition to the ATB support for FTBL released with Model 204 version 7.4, version 7.5 adds ATB support for GTBL, NTBL, and QTBL, using the same <var>[[SERVNSA parameter|SERVNSA]]</var> and <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameters used for FTBL.

When using non-swappable ATB server space, each user will get SERVNSSZ bytes of ATB space, even if the thread is logged out or running resident requests. For greater efficiency, Model 204 version 7.5 also provides swappable ATB server areas that can supplement or replace the non-swappable areas. These swappable ATB server areas are controlled by the <var>[[SERVGA parameter|SERVGA]]</var> and <var>[[SERVGSZ parameter|SERVGSZ]]</var> parameters.

====GTBL, NTBL, QTBL in above the bar storage====
GTBL, NTBL and QTBL can now be placed into non-swappable server storage area above the bar.
In order to store a table in ATB storage:
<ul>
<li>Increase the <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameter by the corresponding table size.
<li>Set the proper bit in <var>[[SERVNSA parameter|SERVNSA]]</var> : for GTBL set second byte to <code>X’80’</code>, so the value of <var>SERVNSA</var> is <code>X'00800000'</code>, for NTBL set third byte to <code>X’40’</code>, so the value of <var>SERVNSA</var> is <code>X'00004000'</code>, for QTBL set the third byte to <code>X’80’</code>, so the value of <var>SERVNSA</var> is <code>X'00002000'</code>. </ul>
'''Note:'''
The settings for each server table above the bar are independent of each other.
So if FTBL, GTBL, NTBL , and, QTBL are all placed above the bar, then <var>SERVNSA</var> should be set to <code>X'02806000'</code>.

====XmlDoc pages in above the bar buffer pool====
With this release, the CCATEMP pages used for <var>XmlDoc</var> objects use the above the bar buffer pool, which may allow the below the bar buffer pool to be reduced, perhaps providing more storage for server areas. It also may provide a reduction in CPU utilization, especially when the <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> parameter is used to allocate CCATEMP in memory.

===Improved range searching by Ordered Index (OI) chunk===
The new <var>[[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK]]</var> attribute for the <var>DEFINE FIELD</var> command enables more efficient range searching on Ordered Index numeric (<var>ORDERED NUMERIC</var>) fields. <var>CHUNK</var> improves performance of the <var>FIND</var> statement <var>RANGE</var> and <var>BETWEEN</var> terms. The <var>CHUNK</var> field attribute defines a subrange ("OI chunk") of the data range. Searching by OI chunks on a range of data requires fewer scans of the ordered index entries to find the desired data. Once OI chunk fields are defined, they are automatically used by FIND processing, so no application code needs to be changed.

After defining an <var>ORDERED NUMERIC</var> field, you define one or more related OI chunk fields containing data from the original base field rounded down by a specified <var>CHUNK</var> size.

Example:
DEFINE FIELD YYYYMMDD WITH ORDERED NUMERIC
DEFINE FIELD YYYYMM WITH ORDERED NUMERIC INVISIBLE CHUNK 100 FOR YYYYMMDD
DEFINE FIELD YYYY WITH ORDERED NUMERIC INVISIBLE CHUNK 10000 FOR YYYYMMDD


<var>CHUNK</var> requires the <var>[[#FILEORG (new settings)|FILEORG]]</var> X'100' bit setting and the <var>INVISIBLE</var> and <var>ORDERED NUMERIC</var> field attributes.

==Debugging and testing enhancements==
The SoftSpy debugging, testing, and performance tuning product is now included as part of the Model 204 core product. For more information on SoftSpy release 7.5, see the [[SoftSpy 7.5 release notes]].

==MQ/204 enhancements==

===Freeing MQ/204 subtasks and associated storage===
The new <var>MQDELDTP</var> PST (pseudo subtask) checks for MQ/204 subtasks that are in a delayed detach state. <var>MQDELDTP</var> detaches MQ/204 subtasks that have finished their work and releases their associated storage areas.

==Other features==
===AT-MOST-ONE and field groups===

The <var>AT-MOST-ONE</var> attribute is now applicable to a field group definition.

===Storing and updating LOBs===

All large object data (LOBs) in a <var>FILEORG</var> X'100' file are chained. There are four bytes per Table E page overhead for chained LOBs. The pages used by a chained LOB are not contiguous.


Handling LOBs in <var>FILEORG</var> X'100' files also has the following effects:
<ul>
<li>LOBs can be changed as needed. The <var>RESERVE</var> clause is ignored in a LOB field <var>ADD</var> statement processing, as well as the <var>STORE RECORD</var> statement processing of fieldname=value pairs. Consequently, the <var>CHANGE</var> statement does not fail because of insufficient reserved space. If the <var>CHANGE</var> statement requires that a LOB field be extended, it is.</li>

<li>The value of the <var>[[EHIGHPG parameter|EHIGHPG]]</var> parameter is always one less than the high water mark of the number of pages used to hold LOBs. (Unless none were ever added, in which case it is zero, not -1).</li>

<li>The value of the <var>[[EPGSUSED parameter|EPGSUSED]]</var> parameter is always the number of pages currently being used to hold LOBs.</li>

<li>The <var>COMPACTE</var> command does not process <var>FILEORG</var> X'100' files, just as it does not process a file created in V6R1 or earlier. Thus, issuing a <var>COMPACTE</var> command for a <var>FILEORG</var> X'100' file produces an error message.</li>

<li>The <var>TABLEE</var> command is effectively executinga <code>VIEW ESIZE EHIGHPG EPGSUSED</code> command for a <var>FILEORG</var> X'100' file. Consequently there are no <var>TABLEE</var> overhead pages in a <var>FILEORG</var> X'100' file.</li>
</ul>

===Constraint attributes===
You can set range constraints on fields using the constraint attributes. Each set of range attributes is comprised of four attributes (<var>GE</var>, <var>GT</var>, <var>LE</var>, <var>LT</var>) that you can use to establish a range for integer values, float values, or date-time stamp values. The types of range attributes are mutually exclusive. For example, you cannot define a field with the <var>FLOAT-GE</var> and <var>INTEGER-LE</var> attributes.

If a range constraint is redefined, it replaces the existing field constraint.

 Note: 
The range constraints do not have to match the data type of the stored field. That is, you could have a date-time constraint for a <var>STRING</var> field or an integer constraint for a <var>FLOAT</var> field, and so on.

You can set the following constraint attributes:
<ul>
<li>date-time value</li>
<li>pattern for a field value</li>
<li>length</li>
<li>integer value</li>
</ul>

See [[Field design (File management)#Content constraints|Content constraints]] for details.

===Changes to journal record layouts===
Four bytes have been added to the journal record header for user statistic entries:
1 byte to hold the <var>IODEV</var> number and 3 bytes for future use.

All user since-last statistics (LAST=) lines will now show the <var>IODEV</var> value:
ST $$$ USERID='<var class="term">userid</var>' ACCOUNT='<var class="term">accountname</var>' IODEV='<var class="term">devicetype</var>' LAST='<var class="term">acty</var>'

For more information on journal records and user statistics, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

==Compatibility issues==
This section describes any compatibility issues between V7.5 and prior versions of Model 204.
An incompatibility arises if an operation that was previously performed without any indication of error, now operates (given the same inputs and conditions) in a different manner.

A normal bug fix resolving behavior that, although not indicating an error, was "clearly and obviously" incorrect, also introduces an incompatibility, but it might not be included below.

===Change to the Ordered Index layout===
Formerly all ORDERED NUMERIC fields came after all ORDERED CHARACTER fields in the Ordered Index. Now, the fields are interspersed in field code order.

===ZFIELD Image===
The [[ZFIELD image detail as of Model 204 V7.5|ZFIELD image]] has been updated for this release. The image is used with $LSTFLD and $FDEF function calls. One change is that FDEF is now longer (to accommodate FDEF1, LOOPVAR, and FDEF2).

===INTERCOMM is no longer supported===
The INTERCOMM interface supports the use of Teletype and 3270 terminals in line-at-a-time mode, using the Model 204 IODEV=29 thread type.

INTERCOMM is no longer supported as of Model 204 version 7.5.

See the <var class="book">Rocket Model 204 Terminal User's Guide</var> for a discussion of terminal interfaces.

===User PDL overflow===
The new <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter might require you to increase the size of the user Push Down List (using UTABLE LPDLST) by up to 3072 bytes, or more if you specify a value for SEQPDL that is larger than the 4096 default value.

===LPDLST parameter maximum value===
The maximum value for the <var>[[LPDLST parameter|LPDLST]]</var> parameter has been increased from 32760 to 65536.

===SSLIBSIZE parameter maximum value===
The maximum value for the <var>JANUS DEFINE</var> command <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter has been decreased from 32767 to 16384.

==New and changed commands==

===DECREASE (new option: DYNAMIC)===
The DYNAMIC option on the <var>[[DECREASE command|DECREASE]]</var> command lets you decrease Table B dynamically, even if the file is open by others or has requests compiled against it.

===DEFINE DATASET (new parameter: GDGRECNT)===
The GDGRECNT parameter for the <var>[[DEFINE DATASET command|DEFINE DATASET]]</var> command causes Model 204 to check the catalog information for the latest relative GDG generation number whenever allocating a GDG data set.

===DEFINE FIELD (new or changed attributes)===
In Model 204 version 7.5, the <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> command has new attributes information:
<ul>
<li>the new <var>[[#Improved range searching by Ordered Index .28OI.29 chunk|CHUNK]]</var> attribute, which improves the efficiency of range finds using ordered index processing</li>
<li>many other <var>[[FILEORG parameter|FILEORG=x'100']]</var> related new or changed [[Release notes for Model 204 version 7.5 (DRAFT)#New field attributes|field attributes]]</li>
</ul>

===DEFINE FIELDGROUP (new in V7.5)===
The <var>[[DEFINE FIELDGROUP command|DEFINE FIELDGROUP]]</var> command establishes the contents of a field group, including the fields and field groups associated with the field group being defined.

===DELETE FIELD (changed to handle CAT and CTO fields)===
The <var>[[DELETE FIELD command|DELETE FIELD]]</var> command has been changed to take [[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF (CAT)]] and [[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF (CTO)]] fields into account. DELETE FIELD does not allow deletion of fields referred to by an existing CAT or CTO field.

===DELETE FIELDGROUP (new in V7.5)===
The <var>[[DELETE FIELDGROUP command|DELETE FIELDGROUP]]</var> command deletes a field group from a Model 204 file.

===DISPLAY FIELD (new option: COMMA)===
In Model 204 version 7.5, the <var>[[DISPLAY FIELD command|DISPLAY FIELD]]</var> command has added
the <var>COMMA</var> option, which uses commas to separate displayed field attributes.

===DISPLAY MODMAP (new in V7.5)===
<var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> displays the Model 204 link map in address order. System manager privileges are required.

===REGENERATE and REGENERATE ONEPASS (improved TO UPDATE option)===
The TO UPDATE option of the <var>[[REGENERATE command|REGENERATE]]</var> and <var>[[REGENERATE ONEPASS command|REGENERATE ONEPASS]]</var> commands can now handle multiple files.
If TO UPDATE <var class="term">nn</var> OF <var class="term">id</var> is specified, it must appear only on the first FILE statement, and no other ‘TO’ options are allowed on subsequent files.
All additional files will be recovered as though they each specified the same 'TO UPDATE' option. Once the 'end of transaction' is reached, further processing will stop and all inflight transactions will be backed out.

===RENAME FIELDGROUP (new in V7.5)===
The <var>[[RENAME FIELDGROUP command|RENAME FIELDGROUP]]</var> command changes the name of a field group.

===UNICODE (new codepage: 1154)===
The <var>[[UNICODE command|UNICODE]]</var> command now accepts 1154 as a codepage name. This codepage has 92 Unicode characters in the range U+0400 through U+045F, representing the Basic Russian alphabet and all of the Cyrillic extensions excepting the four which have grave accents.


==Reliability enhancements==
===SEQPDL parameter===
The new <var>[[SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List (PDL) in order for the SOUL sequencer to proceed with the next quad code. The minimum and default value is 4096 bytes. The maximum value is 8192 bytes. SEQPDL is a user resettable parameter and can be set on the user's parameter line or reset with the UTABLE command.

Formerly 1024 bytes of PDL free space were hardcoded internally in the Model 204 core. With 1024 bytes there were edge cases where abends would break files, resulting in ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED. SEQPDL is provided to allow enough PDL space so that all of the lower level journaling routines can process error conditions without breaking files.

If your applications are using close to the amount of PDL space currently set by the LPDLST value, you might need to increase LPDLST to reflect SEQPDL's increase in free space.

==New and changed parameters==
In addition to the following specific parameter changes, <var class="product">Model 204</var> parameter descriptions, for example as displayed by the <var>VIEW</var> command, are now in mixed case (unless translated to uppercase due to <var>[[#UPCASMSG (new in V7.5)|UPCASMSG]]</var>.)

Note: The [[Sirius Mods]] parameters are merged with the <var class="product">Model 204</var> base as of <var class="product">Model 204</var> version 7.5, and they are available to all version 7.5 customers. The combined set of parameters is displayed on the [[List of Model 204 parameters]] page. The former Sirius parameters in that listing are marked with an (S). 


===DEFCNTX and APDFCNTX (for $View function only, new in V7.5)===
The string
<code>DEFCNTX</code> or <code>APDFCNTX</code> can be used as an
argument to the <var>[[$VIEW|$View]]</var> function to
get the default file or group context. Using these strings is better than using <code>$View('CURFILE')</code> because:
<ul>
<li><code>CURFILE</code> returns a null string if the default context is a group.

<li><code>CURFILE</code> is affected by the <var>IN</var> clause prior to a <var>Begin</var> command and
can be affected by the <var>In</var> clause prior to many SOUL statements.
</ul>

If there is no default context, <code>$View('DEFCNTX')</code> returns a null
string.

Otherwise <code>$View('DEFCNTX')</code> returns the type of context (<code>FILE</code>, <code>TEMP GROUP</code>, or
<code>PERM GROUP</code>) followed by the file or group name, with trailing blanks
removed.

<code>$View('APDFCNTX')</code> returns the same information based on the default
context when the APSY was entered.

Note: These <code>$View</code> arguments were implemented as part of
maintenance to version 7.5 (via zap number 54). They are not available as ordinary parameters on the <var>VIEW</var> command.
In version 7.6 of Model 204,
they will also be available with the <var>VIEW</var> command.


===DSPOPT (change to default setting)===
The default setting for [[DSPOPT parameter|DSPOPT]] has been changed from X'00' to X'01'. The X'01' setting allocates space for servers in memory in chunks of 4K pages, not as a permanent contiguous area. This allocation lets you move fewer 4K pages, keeping the virtual storage allocated for servers in memory less fragmented and possibly using fewer paging tables.

===ECPSIZE (change to max value)===
The maximum value setting for [[ECPSIZE parameter|ECPSIZE]] has been increased from 1310680 to 1966020 to accommodate more [[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|External Call Facility]] parameters.

===FILEORG (new settings)===
<ul>
<li>
The <var>[[FILEORG parameter|FILEORG]] X'100'</var> setting for enhanced data handling files is now available.

X'100' enables a number of enhancements to the file structure, including: 
<ul>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]] </li>

<li>The definition of as many as 32000 fields in a file </li>

<li>System maintained [[Field design (File management)#Automatic Fields|Automatic fields]] </li>

<li>[[Field design (File management)#Field constraints|Field constraints]] providing content validation </li>

<li>Improved space management of fields containing [[Field design (File management)#BLOB, CLOB, and MINLOBE attributes|Large Objects]] </li>

<li>[[#New field attributes|New DEFINE FIELD attributes]], such as <var>CHUNK</var>
</ul>

If X'100' is selected, the X'80' bit (optimized field extraction files) is automatically set.</li>

<li>The <var>FILEORG X'200'</var> setting for large file support is now available. </li>

X'200' allows files to hold up to 48 million records.
</li>
</ul>

===FISTAT (change to X'08' setting)===
The <var>[[FISTAT parameter|FISTAT]] X'08'</var> (file full) setting is now automatically cleared in a transaction back out file if table D is increased enough so that DSIZE is greater than or equal to DPGSRES+DPGSUSED.

===LRETBL (setting increase may be necessary)===
Because there might be a slight increase in record locking table usage in V7.5, an increase in the value of the <var>[[LRETBL parameter|LRETBL]]</var> parameter is advised. The amount of the increase is best estimated by multiplying by 16 the <code>HWM HEADERS</code> value (from a <var>[[MONITOR ENQ command|MONITOR ENQ]]</var> report), then dividing by the value of the <var>NUSERS</var> parameter. For example, if <code>HWM HEADERS = 100000</code> and <code>NUSERS=2000</code>, the recommended <var>LRETBL</var> increase is <code>16*100000/2000</code>, or 800.

===MISCOPT (obsolete)===
The <var>[[MISCOPT parameter|MISCOPT]]</var> parameter is now obsolete. In Model 204 version 7.5, MISCOPT is still viewable but is not resettable.

===MODTIM (new in V7.5)===
The <var>[[MODTIM parameter|MODTIM]]</var> system parameter displays the most recent assembly date and time of the Model 204 load module.

===OUTPUT (change to allow OUTPUT=DUMMY)===
IODEV=3 threads definitions now allow OUTPUT=DUMMY.
When defining IODEV=3 threads, if output is not required, the OUTPUT parameter can be coded as OUTPUT=DUMMY.
For example:
IODEV=3,INPUT=IOD3IN1,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN2,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN3,OUTPUT=DUMMY
and so on.

This means that no DD statement is required for the output data set, and in cases where many
IODEV=3 threads are defined to simulate a large number of users, this enhancement will reduce the number of DD statements required by one half.

===RECLOCKO (X'04' bit now ignored)===
The <var>[[RECLOCKO parameter|RECLOCKO]]</var> X'04' bit is now ignored, and the extra information of the conflicting user number and lock time are now always available.

===RESPAGE (new in V7.5)===
The <var>[[RESPAGE parameter|RESPAGE]]</var> parameter activates the APSY Precompiled Procedures in storage feature using above the bar pages by specifying a number of 4K operating system pages.

===RETRVKEY (change to allow forward retrieve PF key)===
New in this release, if you specify a non-zero setting of <var>[[RETRVKEY parameter|RETRVKEY]]</var>:
<ul>
<li>If you have set the <code>X'01'</code> or <code>X'10'</code> bits of the <var>[[RETRVOPT parameter|RETRVOPT]]</var> parameter, you can use a
forward retrieve PF key, in addition to the backward retrieve PF key specified by <var>RETRVKEY</var>.
'''Note:'''
If either of these bits is set, the <code>X'02'</code> bit is strongly recommended as well.
<li>The size of the allocated storage area, and hence the number and length of input lines available for retrieval, is specified
by the value of the <var>[[RETRVBUF parameter|RETRVBUF]]</var> parameter.</ul>

===SEQPDL (new in V7.5)===
The <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List in order for the SOUL sequencer to proceed with the next quad code. SEQPDL allows enough PDL space for the lower level journaling routines to handle error conditions properly without breaking files and causing ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED.

===SESMAXTO (new in V7.5)===
The <var>[[SESMAXTO parameter|SESMAXTO]]</var> parameter can be used limit the maximum [[Sessions|session]] timeout value or to cause all current closed sessions to be immediately discarded.

===SMFSVC (obsolete)===
The <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is [[Release notes for Model 204 version 7.5 (DRAFT)#Writing records to the SMF data set|obsolete]] as of Model 204 version 7.5.

===UPCASMSG (new in V7.5)===
The <var>[[UPCASMSG parameter|UPCASMSG]]</var> parameter can be used to translate messages issued by <var class="product">Model 204</var> to uppercase; otherwise (depending on the message being issued) they are displayed in mixed (upper and lower) case.




==Documentation conversion==
Rocket Model 204 documentation is being converted from individual manuals in PDF format to a set of cross-linked HTML articles in this integrated wiki, M204wiki.

As of Model 204 release 7.5, several manuals are now in wiki format and the rest remain in PDF format, available from the [http://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm Rocket Software Documentation Library].

For details, see [[Model 204 and Sirius documentation]].

==New and updated messages==

Many messages have been updated and added in this release. See [[New and updated messages in Model 204 version 7.5]] for details.

[[Category: Release notes]]

Release notes for Model 204 version 7.5

2014-03-28T17:41:50Z

LGradus: /* GTBL in above the bar storage */

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

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

==New in this release==
This section summarizes the new features and enhancements for Model 204 version 7.5.0.

===SOUL (User Language)===
The significantly enhanced, object-oriented, version of User Language is now called SOUL. All existing User Language programs will continue to work under SOUL, so User Language can be considered to be a subset of SOUL, though the name "User Language" is now deprecated.
<ul>
<li>Sirius object-oriented language extensions integration</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|ECF]] statements can pass up to 60 parameters</li>
</ul>

===System Management===
<ul>
<li>Writing records to the SMF data set without an SVC installed</li>
</ul>

===Performance===
<ul>
<li>GTBL can be stored above the bar</li>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]]</li>
</ul>

==Operating system requirements==
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the following operating system support:
<ul>
<li>For IBM z/OS: Version 1 Release 7 is sufficient for all new functionality except for the following
features:
<ul>
<li>Large (1 MB) page support requires Version 1 Release 9.
<li>Extended address volumes (EAV) requires Version 1 Release 12.
</ul>
<li>For IBM z/VM: Version 5 Release 4.0 or later
<li>For IBM z/VSE:
<ul>
<li>Version 5 Release 1 or
<li>Version 4 Release 3 or
<li>Version 4 Release 2.1 or
<li>Version 4 Release 2.0, with these program temporary fixes (PTFs) installed:
<ul>
<li>UD53436
<li>UD53437
<li>UD53438
<li>UD53439
</ul>
</ul>
</ul>

=== Hardware requirements ===
Requirements for Model 204 version 7.5 are still being determined.

Model 204 version 7.4 required the IBM z/890 or above processor, except for the following feature:

The large (1 MB) page support feature requires the IBM z10 or above processor. 

===Model 204 compatibility with operating systems===
Content for version 7.5 is still to be determined.
For information on Model 204 certification with IBM operating systems, see:
http://www.rocketsoftware.com/products/rocket-model-204/technical-information

===Model 204 compatibility with Connect*===
All supported versions of Connect* are compatible with Model 204 version 7.5.0.
However, CLOB/BLOB support requires Connect* version 7.4.0 or higher. Use of Connect* versions earlier than version 7.4.0 to SELECT, UPDATE, or INSERT CLOB/BLOB data will fail and might produce unexpected application behavior and/or return an error.
Connect* version 7.5.0 is compatible with versions of Model 204 that are earlier than version 7.5.0.

==SOUL (User Language) enhancements==
Much of the substantial new and enhanced functionality described in the following subsections is available as a result of the acquisition of Sirius Software. The functionality that is the subject of the initial subsection, "Object oriented programming," motivates the new name for User Language, '''SOUL''', often thought of as Simple Objective User Language.

===Object oriented programming===
As of version 7.5 of Model 204 (and backward compatible with existing User Language applications), the SOUL language is equipped with [http://en.wikipedia.org/wiki/Object-oriented Object-Oriented Programming](sometimes abbreviated OO) capabilities comparable or superior to other contemporary object oriented languages. The OO features were formerly contained in the [[Janus SOAP User Language Interface]], and you can use [[Object oriented programming in SOUL]] as an entry point to the extensive SOUL OO documentation. In particular, you might want to begin with the [[Getting started with OOP for User Language programmers|OO tutorial]].

===Record capacity increase===
In this version of Model 204, the record limit is increased from sixteen million records to forty-eight million records per file.

===New SOUL statements===
{{Template:User Language statements}}

===Non-OO enhancements in SOUL===
{{Template:User Language syntax enhancements}}

===SOUL support for field groups===

====ADD (or INSERT or DELETE) FIELDGROUP statements====
The <var>ADD FIELDGROUP</var> statement and the <var>INSERT FIELDGROUP</var> statement behavior parallels the behavior of the <var>ADD</var> and <var>INSERT</var> statements for simple fields. The <var>DELETE FIELDGROUP</var> statement handles more situations and is therefore more complex.
See [[Data maintenance#Updating field groups|Updating field groups]] for details.

====Statements for handling field groups====
SOUL now provides several statements for handling field groups:
<ul>
<li><var>FOR FIELDGROUP</var></li>
<li><var>FOR ALL OCCURRENCES OF FIELDGROUP (FAO FIELDGROUP)</var></li>
<li><var>FOR EACH OCCURRENCE OF FIELDGROUP (FEO FIELDGROUP)</var></li>
</ul>

See [[Operations on multiply occurring fields#Special statements for multiply occurring fields and field groups|Special statements for multiply occurring fields and field groups]] for details.

====Output statements for field groups====

The following SOUL statements provide display output for Model 204 field groups:
AUDIT ALL FIELDGROUP INFORMATION (AAFGI)
PRINT ALL FIELDGROUP INFORMATION (PAFGI)


See [[Basic SOUL statements and commands#Output statements|Output statements]] for details.

====Field group SORT support====
You can use field groups in [[Sorting#Field group SORT support|sorted sets]]. <var>SORT</var> statement support for field groups lets you sort records with field groups as well as reference field groups in the sorted sets. For example, you can issue a <code>FAO FIELDGROUP</code> statement or <code>FEO FIELDGROUP</code> statement against the sorted set.

===EQ VALUE retrieval condition===

SOUL now provides the <var>EQ VALUE</var> clause to support expressions in <var>FIND</var> statements.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] for details.

===EQ WITH retrieval condition for concatenated fields===
SOUL now provides the <var>EQ WITH</var> clause for retrieving <var>CONCATENATION-OF</var> fields. Model 204 automatically builds the concatenated value.

See [[Record retrievals#Using expressions in FIND statements|Using expressions in FIND statements]] and [[Record retrievals#EQ WITH retrieval condition for concatenated fields|EQ with retrieval condition for concatenated fields]] for details.

===External Call Facility (ECF)===
<var>EXTERNAL CALL</var> statements can now pass more parameters.
The maximum number of parameters that can be passed in an <var>EXTERNAL CALL</var> statement has been increased from 40 to 60.
The maximum value setting for <var>[[ECPSIZE parameter|ECPSIZE]]<var> is increased from 1310680 to 1966020 to accommodate the extra parameters.

ECF is available only on z/OS systems. For more information about the External Call Facility and the <var>EXTERNAL CALL</var> statement, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

===REPEAT statement UNTIL option===
The <var>REPEAT</var> statement now supports the <var>UNTIL</var> option. In previous releases, only <var>REPEAT WHILE</var> was supported.

A <var>[[Flow of control in User Language#REPEAT UNTIL statement|REPEAT UNTIL]]</var> statement enters the loop body prior to checking the condition.

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

====New HttpRequest TranslateTable property====
The <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property makes it possible to set the translate table to be used for EBCDIC to ASCII translation of data in an <var>HttpRequest</var> object.

====New InvalidTranslateTable class====
Objects of the [[InvalidTranslateTable class|InvalidTranslateTable exception class]] are thrown when a requested system translate table cannot be found. It is currently thrown only by the <var>[[TranslateTable (HttpRequest property)|TranslateTable]]</var> <var>HttpRequest</var> property.

====New bit manipulation String functions====
New bit manipulation functions <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitCountString (String function)|BitCountString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, <var>[[BitSetString (String function)|BitSetString]]</var>, and <var>[[BitValueString (String function)|BitValueString]]</var> make it easier to manipulate the bits in a string.

====New InvalidBitNumber class====
Objects of the [[InvalidBitNumber class|InvalidBitNumber exception class]] are thrown when an invalid bit number is requested by a bit manipulation function. It is currently thrown only by the <var>[[BitClearString (String function)|BitClearString]]</var>, <var>[[BitFlipString (String function)|BitFlipString]]</var>, [[BitSetString (String function)|BitSetString]], and <var>[[BitValueString (String function)|BitValueString]]</var> functions.

====Disable base64 encoding in LoadFromRecord and related methods====
The <var>Base64Encode</var>=<var>False</var> argument can be used with the <var>[[LoadFromRecord (XmlDoc/XmlNode subroutine)|LoadFromRecord]]</var> method to disable any base64 encoding of field values.

Alternatively, the <var>CharacterMap</var> argument (with a non-null value) can be used to disable any base64 encoding of field values, and to specify translations, which can avoid request translation due to X'00' and/or untranslatable characters in field values.

These arguments are also added to the <var>[[NewFromRecord (XmlDoc function)|NewFromRecord]]</var> and <var>[[ToXmlDoc (Record function)|ToXmlDoc]]</var> methods.

====New option for AppendJournalData====
The <var>QT</var> option is added to the <var>[[AppendJournalData (Stringlist function)#Options parameter|AppendJournalData]]</var> method, to include QT type audit entries.

====New parameter for AddField====
The <var>Strip</var> option is added to the <var>Screen</var> class method <var>[[AddField (Screen function)|AddField]]</var> to allow suppression of leading and trailing blank removal from input fields.

===New and changed $functions===

====Former Sirius $functions====
The $functions referred to by the link below are added to SOUL as a result of the acquisition of Sirius Software:
:[[List of $functions|Sirius $functions]]

====$SNDMAIL attachment ASCII translation====
The <var>$SNDMAIL</var> function can now translate an attachment to ASCII before sending it.
This translation is useful if the <var>$SNDMAIL</var> attachment is a <var>CLOB</var> (<var>CHARACTER-LARGE-OBJECT</var>) such as a text document.

The <var>$SNDMAIL</var> function now accepts an optional parameter after the name of the attached object. If this parameter is set to 'C' (or to a percent variable with the value 'C'), the object in the buffer is translated to ASCII before being attached to the email.

If this parameter is not specified, the object in the buffer is sent as a binary object.

In this example:
%RC = $SNDMAIL(%SUBJECT,,%BODY,%FROM,%TO,,,,'CLOB.TXT','C')

the <code>CLOB.TXT</code> attachment will be translated to ASCII before being attached to the email.

====New function calls for field groups====
When a field group is added, a [[Data maintenance#Updating field groups|field group ID]] is assigned to the field group.
<ul>
<li><var>[[$FIELDGROUPID]]</var> returns the ID of the current field group.</li>
<li><var>[[$FIELDGROUPOCCURRENCE]]</var> returns the current occurrence number of the field group.</li>
</ul>

==Sirius products and product enhancements==
[[Sirius Software product list|The former-Sirius products]] are now available to Model 204 customers as separately purchased items as a result of the acquisition of Sirius Software.

===Changes to Janus SSL support===
Under Model 204 version 7.5, Janus products:

<ul>
<li>Drop support for version 2 of the Secure Sockets Layer encryption protocol (SSL V2)

You can use the <var>[[SSLPROT parameter|SSLPROT]]</var> parameter on the <var>JANUS DEFINE</var> command for a port to explicitly specify, or limit, the SSL protocols available for a connection. The <var>SSLPROT</var> documentation describes the SSL protocols that Janus supports. 

Janus support for SSL V2 also included an option to specify a larger than "legal" input buffer for connections not strictly conforming to the V2 standard. You specify that buffer size with the <var>JANUS DEFINE</var> <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter, and the <var>SSLIBSIZE</var> maximum value as of Model 204 V7.5 is reduced (from 32767 bytes) to the SSL maximum allowed size of 16384. </li>

<li>Add support for new ciphers and TLS levels

You can use the <var>[[SSLCIPH parameter|SSLCIPH]]</var> <var>JANUS DEFINE</var> parameter to specify the SSL ciphers available for a connection. The <var>SSLCIPH</var> documentation describes the SSL ciphers that Janus supports. </li>
</ul>

===WEBOPT parameter change===
The <var>[[WEBOPT parameter|WEBOPT]]</var> parameter default value is changed to X'03' from 0. <var>WEBOPT</var> affects the interaction of Model 204 and RACF security.

==File-related enhancements==

===Support for physical field groups===
Model 204 supports non-relational, de-normalized data structures. Many Model 204 sites have enjoyed significant cost and performance benefits from efficiently processing multiply occurring fields. This concept has been enhanced to introduce physical field groups that let you view and process groups of fields as a logical entity.

You can define a physical field group only for files with the [[#FILEORG (new settings)|FILEORG X'100' setting]]. To take advantage of field groups in files defined before Model 204 version 7.5, you must reorganize the files with a <var>FILEORG</var> setting that includes the X'100' bit.

Files with <var>FILEORG</var> X'100' can have up to 32,000 fields.

For more information, see [[Field group design (File management)|field group design]].

===Increased Table B record number capacity===
[[Table B (File architecture)|Table B]] can now contain up to 48M possible record numbers. (The previous limit was 16M.)

Set the [[#FILEORG (new settings)|FILEORG X'200' bit]] at file creation time to allow for the increased record numbers.
<blockquote class="note">
Notes: 
<ul>
<li>The limit for <var>BSIZE</var> remains at 16M.

<code>BSIZE * BRECPPG</code> must be less than or equal to 48M (actually decimal 50,331,648 to be exact). 

For example, if <var>BSIZE</var> is 16M, <var>BRECPPG</var> cannot be more than 3. </li>

<li>The <var>FILEORG</var> X'200' bit cannot be set for files with hash key or sorted file organization.</li>
</ul>
</blockquote>

===Automatic fields===
Model 204 now lets you define a field whose value is [[Field design (File management)#Automatic fields|automatically maintained]]. A field can count occurrences of another field so that every store or delete of the field occurrence changes the count in the automatic field. Automatic fields are defined with the following attributes:
<ul>
<li><var>COUNT-OCCURRENCES-OF</var></li>
<li><var>CREATE-TIME</var></li>
<li><var>CREATE-TIMEUTC</var></li>
<li><var>CREATE-USER</var></li>
<li><var>UPDATE-TIME</var></li>
<li><var>UPDATE-TIMEUTC</var></li>
<li><var>UPDATE-USER</var></li>
</ul>

The value of an automatic field is updated at the start of a transaction by Model 204 and you cannot set it explicitly by a program. Any valid update statement causes the appropriate time and user stamps to be updated. For example, the time and user stamps will be undated when <code>DELETE FOO(8)</code> is processed, even if there are no occurrences of FOO in the record and an actual update does not take place.

Once you define an automatic value for a field, you cannot redefine the automatic value.

===Concatenated fields===
Model 204 now lets you define [[Field design (File management)#Concatenated fields|concatenated fields]].

Fields that make up concatenated field values must be <var>AT-MOST-ONE</var>, <var>EXACTLY-ONE</var>, or <var>OCCURS</var> 1 and must all be in the same field group context (or not in a field group). Fields that occur in all field groups (<var>FIELDGROUP *</var>) cannot be used in a concatenation.

If a concatenated field becomes longer than 255 bytes after adding separator and escape characters, the update request is cancelled.

===New field attributes===
Model 204 version 7.5 introduces the new <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> attributes described in this section. These attributes apply to all fields in Model 204. 

Note: These attributes all require that the <var>[[FILEORG parameter|FILEORG]]</var> parameter X'100' bit must be set on the file containing the fields.

Changes in the new field attributes are detected during the redefinition of an existing field. When such a change is detected, the following messages might be issued:
M204.1260: [FIELD | FIELDGROUP] WAS PREVIOUSLY DEFINED WITH DIFFERENT ATTRIBUTES,
NEW [FIELD | FIELDGROUP] OPTIONS IGNORED

or
M204.2884: [FIELD WAS PREVIOUSLY DEFINED AS A FIELDGROUP | FIELDGROUP WAS PREVIOUSLY
DEFINED AS A FIELD], NEW DEFINITION IGNORED


The table below lists the new field attributes. 
<table>
<tr class="head">
<th>Attribute</th><th>Abbreviation</th><th>Description</th>
</tr>

<tr>
<td>[[DEFINE_FIELD_command#Ordered_index_CHUNK_attribute|CHUNK]]</td>
<td>CNK</td>
<td>Defines "OI chunks" of data in Ordered Index numeric range fields to enable more efficient searching.</td>
</tr>

<tr>
<td>[[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF]]</td>
<td>(CAT)</td>
<td>Lists the fields that make up a concatenated field</td>
</tr>

<tr>
<td nowrap>[[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF]]</td>
<td>(CTO)</td>
<td>Automatically maintains a count of the number of occurrences of the specified field.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIME]]</td>
<td>(CRTM)</td>
<td>Captures the time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-TIMEUTC]]</td>
<td>(CRTMU)</td>
<td>Captures the Coordinated Universal Time when the field was created, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|CREATE-USER]]</td>
<td>(CRUS)</td>
<td>Captures the user ID of the user who created the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME]]</td>
<td>(DT)</td>
<td>Specifies the format of the date and time data stored in Table B. The default is YYYYMMDDHHMISSXXXXXX.</td>
</tr>

<tr><td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GE]]</td>
<td>(DTGE)</td>
<td>With DATETIME-GT, DATETIME-LE, and DATETIME-LT, used to establish a range for date/time values. Specifies that the date/time value must be later than or the same as the date/time value that follows. </td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-GT]]</td>
<td>(DTGT)</td>
<td>Specifies that the date/time value must be later than the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LE]]</td>
<td>(DTLE)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DATETIME-GE .28DTGE.29.2C DATETIME-GT .28DTGT.29.2C DATETIME-LE .28DTLE.29.2C and DATETIME-LT .28DTLT.29 attributes|DATETIME-LT]]</td>
<td>(DELT)</td>
<td>Specifies that the date/time value must be earlier than or the same as the date/time value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#DEFAULT-VALUE .28DV.29 attribute|DEFAULT-VALUE]]</td>
<td>(DV)</td>
<td>Specifies the value to use for the field when the record is created and no value has been assigned to the field.

(The value of the STORE-DEFAULT setting determines whether the DEFAULT-VALUE is physically stored on the record or if it is just used as the default value when the field is missing.)</td>
</tr>

<tr>
<td>[[Field design (File management)#ESCAPE .28ESC.29 attribute|ESCAPE]]</td>
<td>(ESC)</td>
<td>Specifies an escape character to insert before separator and escape characters in a concatenated field, differentiating those characters from real data. The default value is X’01’.</td>
</tr>

<tr>
<td>[[Field design (File management)#AT-MOST-ONE.2C REPEATABLE and EXACTLY-ONE attributes|EXACTLY-ONE]]</td>
<td>(EXONE)</td>
<td>Specifies that a field always has exactly one occurrence in its record or field group context. The default value is 1.</td>
</tr>

<tr><td>[[Field design (File management)#FIELDGROUP attribute|FIELDGROUP]]</td>
<td>(FG)</td>
<td>Specifies the name of the field group that the defined field is associated with (contained in).</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GE]]</td>
<td>(FLTGE)</td>
<td>With FLOAT-GT, FLOAT-LE, and FLOAT-LT, used to establish a range for float values when defining a field. Specifies that the float value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-GT]]</td>
<td>(FLTGT)</td>
<td>Specifies that the float value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LE]]</td>
<td>(FLTLE)</td>
<td>Specifies that the float value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#FLOAT-GE .28FLTGE.29.2C FLOAT-GT .28FLTGT.29.2C FLOAT-LE .28FLTLE.29 and FLOAT-LT .28FLTLT.29 attributes|FLOAT-LT]]</td>
<td>(FLTLT)</td>
<td>Specifies that the float value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GE]]</td>
<td>(INTGE)</td>
<td>With INTEGER-GT, INTEGER-LE, and INTEGER-LT, used to establish a range for integer values when defining a field. Specifies that the integer value must be greater than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-GT]]</td>
<td>(INTGT)</td>
<td>Specifies that the integer value must be greater than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LE]]</td>
<td>(INTLE)</td>
<td>Specifies that the integer value must be less than or equal to the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#INTEGER-GE .28INTGE.29.2C INTEGER-GT .28INTGT.29.2C INTEGER-LE .28INTLE.29 and INTEGER-LT .28INTLT.29 attributes|INTEGER-LT]]</td>
<td>(INTLT)</td>
<td>Specifies that the integer value must be less than the value that follows.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-EQ .28LEQ.29 attribute|LENGTH-EQ]]</td>
<td>(LEQ)</td>
<td>Used to set a length constraint when defining a field. Specifies the required length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-GE .28LGE.29 attribute|LENGTH-GE]]</td>
<td>(LGE)</td>
<td>Specifies the minimum length of a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#LENGTH-LE .28LLE.29 attribute|LENGTH-LE]]</td>
<td>(LLE)</td>
<td>Specifies the maximum length of a field.</td>
</tr>

<tr><td>[[Field design (File management)#Setting a pattern for a field value: the LIKE attribute|LIKE]]</td>
<td>(LK)</td>
<td>Sets a pattern that a field value must conform to.</td>
</tr>

<tr>
<td>[[Field design (File management)#BLOB.2C CLOB.2C and MINLOBE attributes|MINLOBE]]</td>
<td>(MLBE)</td>
<td>Defines the minimum size of a BLOB or CLOB field value that will be stored in Table E. This avoids wasting Table E pages on small values that could be stored in Table B (or Table X). The default is 0.</td>
</tr>

<tr>
<td>NO-DOMAIN-CONSTRAINTS</td>
<td/>
<td>Specifies that the field has no [[Field design (File management)#Content constraints|content constraint]] attributes. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove existing constraints on a field.</td>
</tr>

<tr>
<td>NO-DEFAULT-VALUE</td>
<td>(NDV)</td>
<td>Specifies that the field has no default value. Useful with <var>[[REDEFINE command|REDEFINE]]</var> to remove an existing default value on a field.</td>
</tr>

<tr>
<td>[[Field design (File management)#SEPARATOR .28SEP.29 attribute|SEPARATOR]]</td>
<td>(SEP)</td>
<td>Specifies a separator character used between field values in concatenated fields. The default is X’00’.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-DEFAULT]]</td>
<td>(SD)</td>
<td>Specifies whether to physically store the default value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#STORE-DEFAULT .28SD.29 and STORE-NULL .28SN.29 attributes|STORE-NULL]]</td>
<td>(SN)</td>
<td>Specifies whether to physically store the null value for the field in each record. The default option is LITERAL (LIT), which stores a literal string.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIME]]</td>
<td>(UPTM)</td>
<td>Captures the time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-TIMEUTC]]</td>
<td>(UPTMU)</td>
<td>Captures the Coordinated Universal Time when the field was updated, as of the start of the transaction.</td>
</tr>

<tr>
<td>[[Field design (File management)#Automatic Fields|UPDATE-USER]]</td>
<td>(UPUS)</td>
<td>Captures the user ID of the user who updated the field.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-8]]</td>
<td>(UTF8)</td>
<td>Data is stored in UTF-8 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>

<tr>
<td>[[Field design (File management)#UTF-8 and UTF-16 attributes|UTF-16]]</td>
<td>(UTF16)</td>
<td>Data is stored in UTF-16 format and is treated as unicode data inside SOUL programs. The default is EBCDIC.</td>
</tr>
</table>

==System management enhancements==

===Writing records to the SMF data set===
Having Model 204 write records to the SMF data set no longer requires the installation of an SVC.

Therefore, the <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is no longer required and, if present, will be ignored and flagged with the following informational message:
M204.0204: PARAMETER SMFSVC OBSOLETE AND NOT RESET
However, the <var>[[SMFLORN parameter|SMFLORN]]</var> and <var>[[SMFSLRN parameter|SMFSLRN]]</var> parameters must still be present in CCAIN if SMF records are required.

==Performance enhancements==

===64-bit addressing and Above The Bar (ATB) storage===
Model 204 moves above the (2G) 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.

In addition to the ATB support for FTBL released with Model 204 version 7.4, version 7.5 adds ATB support for GTBL, NTBL, and QTBL, using the same <var>[[SERVNSA parameter|SERVNSA]]</var> and <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameters used for FTBL.

When using non-swappable ATB server space, each user will get SERVNSSZ bytes of ATB space, even if the thread is logged out or running resident requests. For greater efficiency, Model 204 version 7.5 also provides swappable ATB server areas that can supplement or replace the non-swappable areas. These swappable ATB server areas are controlled by the <var>[[SERVGA parameter|SERVGA]]</var> and <var>[[SERVGSZ parameter|SERVGSZ]]</var> parameters.

====GTBL, NTBL, QTBL in above the bar storage====
GTBL, NTBL and QTBL can now be placed into non-swappable server storage area above the bar.
In order to store a table in ATB storage:
<ul>
<li>Increase the <var>[[SERVNSSZ parameter|SERVNSSZ]]</var> parameter by the corresponding table size.
<li>Set the proper bit in <var>[[SERVNSA parameter|SERVNSA]]</var> : for GTBL set second byte to <code>X’80’</code>, so the value of <var>SERVNSA</var> is <code>X'00800000'</code>, for NTBL set third byte to <code>X’40’</code>, so the value of <var>SERVNSA</var> is <code>X'00004000'</code>, for QTBL set the third byte to <code>X’80’</code>, so the value of <var>SERVNSA</var> is <code>X'00002000'</code>. </ul>
'''Note:'''
The settings for each server table above the bar are independent of each other.
So if FTBL, GTBL, NTBL , and, QTBL are all placed above the bar, then <var>SERVNSA</var> should be set to <code>X'02806000'</code>.

====NTBL and QTBL in above the bar storage====
Needs details . . .

====XmlDoc pages in above the bar buffer pool====
With this release, the CCATEMP pages used for <var>XmlDoc</var> objects use the above the bar buffer pool, which may allow the below the bar buffer pool to be reduced, perhaps providing more storage for server areas. It also may provide a reduction in CPU utilization, especially when the <var>[[TEMPPAGE parameter|TEMPPAGE]]</var> parameter is used to allocate CCATEMP in memory.

===Improved range searching by Ordered Index (OI) chunk===
The new <var>[[DEFINE FIELD command#Ordered index CHUNK attribute|CHUNK]]</var> attribute for the <var>DEFINE FIELD</var> command enables more efficient range searching on Ordered Index numeric (<var>ORDERED NUMERIC</var>) fields. <var>CHUNK</var> improves performance of the <var>FIND</var> statement <var>RANGE</var> and <var>BETWEEN</var> terms. The <var>CHUNK</var> field attribute defines a subrange ("OI chunk") of the data range. Searching by OI chunks on a range of data requires fewer scans of the ordered index entries to find the desired data. Once OI chunk fields are defined, they are automatically used by FIND processing, so no application code needs to be changed.

After defining an <var>ORDERED NUMERIC</var> field, you define one or more related OI chunk fields containing data from the original base field rounded down by a specified <var>CHUNK</var> size.

Example:
DEFINE FIELD YYYYMMDD WITH ORDERED NUMERIC
DEFINE FIELD YYYYMM WITH ORDERED NUMERIC INVISIBLE CHUNK 100 FOR YYYYMMDD
DEFINE FIELD YYYY WITH ORDERED NUMERIC INVISIBLE CHUNK 10000 FOR YYYYMMDD


<var>CHUNK</var> requires the <var>[[#FILEORG (new settings)|FILEORG]]</var> X'100' bit setting and the <var>INVISIBLE</var> and <var>ORDERED NUMERIC</var> field attributes.

==Debugging and testing enhancements==
The SoftSpy debugging, testing, and performance tuning product is now included as part of the Model 204 core product. For more information on SoftSpy release 7.5, see the [[SoftSpy 7.5 release notes]].

==MQ/204 enhancements==

===Freeing MQ/204 subtasks and associated storage===
The new <var>MQDELDTP</var> PST (pseudo subtask) checks for MQ/204 subtasks that are in a delayed detach state. <var>MQDELDTP</var> detaches MQ/204 subtasks that have finished their work and releases their associated storage areas.

==Other features==
===AT-MOST-ONE and field groups===

The <var>AT-MOST-ONE</var> attribute is now applicable to a field group definition.

===Storing and updating LOBs===

All large object data (LOBs) in a <var>FILEORG</var> X'100' file are chained. There are four bytes per Table E page overhead for chained LOBs. The pages used by a chained LOB are not contiguous.


Handling LOBs in <var>FILEORG</var> X'100' files also has the following effects:
<ul>
<li>LOBs can be changed as needed. The <var>RESERVE</var> clause is ignored in a LOB field <var>ADD</var> statement processing, as well as the <var>STORE RECORD</var> statement processing of fieldname=value pairs. Consequently, the <var>CHANGE</var> statement does not fail because of insufficient reserved space. If the <var>CHANGE</var> statement requires that a LOB field be extended, it is.</li>

<li>The value of the <var>[[EHIGHPG parameter|EHIGHPG]]</var> parameter is always one less than the high water mark of the number of pages used to hold LOBs. (Unless none were ever added, in which case it is zero, not -1).</li>

<li>The value of the <var>[[EPGSUSED parameter|EPGSUSED]]</var> parameter is always the number of pages currently being used to hold LOBs.</li>

<li>The <var>COMPACTE</var> command does not process <var>FILEORG</var> X'100' files, just as it does not process a file created in V6R1 or earlier. Thus, issuing a <var>COMPACTE</var> command for a <var>FILEORG</var> X'100' file produces an error message.</li>

<li>The <var>TABLEE</var> command is effectively executinga <code>VIEW ESIZE EHIGHPG EPGSUSED</code> command for a <var>FILEORG</var> X'100' file. Consequently there are no <var>TABLEE</var> overhead pages in a <var>FILEORG</var> X'100' file.</li>
</ul>

===Constraint attributes===
You can set range constraints on fields using the constraint attributes. Each set of range attributes is comprised of four attributes (<var>GE</var>, <var>GT</var>, <var>LE</var>, <var>LT</var>) that you can use to establish a range for integer values, float values, or date-time stamp values. The types of range attributes are mutually exclusive. For example, you cannot define a field with the <var>FLOAT-GE</var> and <var>INTEGER-LE</var> attributes.

If a range constraint is redefined, it replaces the existing field constraint.

 Note: 
The range constraints do not have to match the data type of the stored field. That is, you could have a date-time constraint for a <var>STRING</var> field or an integer constraint for a <var>FLOAT</var> field, and so on.

You can set the following constraint attributes:
<ul>
<li>date-time value</li>
<li>pattern for a field value</li>
<li>length</li>
<li>integer value</li>
</ul>

See [[Field design (File management)#Content constraints|Content constraints]] for details.

===Changes to journal record layouts===
Four bytes have been added to the journal record header for user statistic entries:
1 byte to hold the <var>IODEV</var> number and 3 bytes for future use.

All user since-last statistics (LAST=) lines will now show the <var>IODEV</var> value:
ST $$$ USERID='<var class="term">userid</var>' ACCOUNT='<var class="term">accountname</var>' IODEV='<var class="term">devicetype</var>' LAST='<var class="term">acty</var>'

For more information on journal records and user statistics, see the <var class="book">Rocket Model 204 System Manager's Guide</var>.

==Compatibility issues==
This section describes any compatibility issues between V7.5 and prior versions of Model 204.
An incompatibility arises if an operation that was previously performed without any indication of error, now operates (given the same inputs and conditions) in a different manner.

A normal bug fix resolving behavior that, although not indicating an error, was "clearly and obviously" incorrect, also introduces an incompatibility, but it might not be included below.

===Change to the Ordered Index layout===
Formerly all ORDERED NUMERIC fields came after all ORDERED CHARACTER fields in the Ordered Index. Now, the fields are interspersed in field code order.

===ZFIELD Image===
The [[ZFIELD image detail as of Model 204 V7.5|ZFIELD image]] has been updated for this release. The image is used with $LSTFLD and $FDEF function calls. One change is that FDEF is now longer (to accommodate FDEF1, LOOPVAR, and FDEF2).

===INTERCOMM is no longer supported===
The INTERCOMM interface supports the use of Teletype and 3270 terminals in line-at-a-time mode, using the Model 204 IODEV=29 thread type.

INTERCOMM is no longer supported as of Model 204 version 7.5.

See the <var class="book">Rocket Model 204 Terminal User's Guide</var> for a discussion of terminal interfaces.

===User PDL overflow===
The new <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter might require you to increase the size of the user Push Down List (using UTABLE LPDLST) by up to 3072 bytes, or more if you specify a value for SEQPDL that is larger than the 4096 default value.

===LPDLST parameter maximum value===
The maximum value for the <var>[[LPDLST parameter|LPDLST]]</var> parameter has been increased from 32760 to 65536.

===SSLIBSIZE parameter maximum value===
The maximum value for the <var>JANUS DEFINE</var> command <var>[[SSLIBSIZE (JANUS DEFINE parameter)|SSLIBSIZE]]</var> parameter has been decreased from 32767 to 16384.

==New and changed commands==

===DECREASE (new option: DYNAMIC)===
The DYNAMIC option on the <var>[[DECREASE command|DECREASE]]</var> command lets you decrease Table B dynamically, even if the file is open by others or has requests compiled against it.

===DEFINE DATASET (new parameter: GDGRECNT)===
The GDGRECNT parameter for the <var>[[DEFINE DATASET command|DEFINE DATASET]]</var> command causes Model 204 to check the catalog information for the latest relative GDG generation number whenever allocating a GDG data set.

===DEFINE FIELD (new or changed attributes)===
In Model 204 version 7.5, the <var>[[DEFINE FIELD command|DEFINE FIELD]]</var> command has new attributes information:
<ul>
<li>the new <var>[[#Improved range searching by Ordered Index .28OI.29 chunk|CHUNK]]</var> attribute, which improves the efficiency of range finds using ordered index processing</li>
<li>many other <var>[[FILEORG parameter|FILEORG=x'100']]</var> related new or changed [[Release notes for Model 204 version 7.5 (DRAFT)#New field attributes|field attributes]]</li>
</ul>

===DEFINE FIELDGROUP (new in V7.5)===
The <var>[[DEFINE FIELDGROUP command|DEFINE FIELDGROUP]]</var> command establishes the contents of a field group, including the fields and field groups associated with the field group being defined.

===DELETE FIELD (changed to handle CAT and CTO fields)===
The <var>[[DELETE FIELD command|DELETE FIELD]]</var> command has been changed to take [[Field design (File management)#CONCATENATION-OF .28CAT.29 attribute|CONCATENATION-OF (CAT)]] and [[Field design (File management)#Counting occurrences of a field|COUNT-OCCURRENCES-OF (CTO)]] fields into account. DELETE FIELD does not allow deletion of fields referred to by an existing CAT or CTO field.

===DELETE FIELDGROUP (new in V7.5)===
The <var>[[DELETE FIELDGROUP command|DELETE FIELDGROUP]]</var> command deletes a field group from a Model 204 file.

===DISPLAY FIELD (new option: COMMA)===
In Model 204 version 7.5, the <var>[[DISPLAY FIELD command|DISPLAY FIELD]]</var> command has added
the <var>COMMA</var> option, which uses commas to separate displayed field attributes.

===DISPLAY MODMAP (new in V7.5)===
<var>[[DISPLAY MODMAP command|DISPLAY MODMAP]]</var> displays the Model 204 link map in address order. System manager privileges are required.

===REGENERATE and REGENERATE ONEPASS (improved TO UPDATE option)===
The TO UPDATE option of the <var>[[REGENERATE command|REGENERATE]]</var> and <var>[[REGENERATE ONEPASS command|REGENERATE ONEPASS]]</var> commands can now handle multiple files.
If TO UPDATE <var class="term">nn</var> OF <var class="term">id</var> is specified, it must appear only on the first FILE statement, and no other ‘TO’ options are allowed on subsequent files.
All additional files will be recovered as though they each specified the same 'TO UPDATE' option. Once the 'end of transaction' is reached, further processing will stop and all inflight transactions will be backed out.

===RENAME FIELDGROUP (new in V7.5)===
The <var>[[RENAME FIELDGROUP command|RENAME FIELDGROUP]]</var> command changes the name of a field group.

===UNICODE (new codepage: 1154)===
The <var>[[UNICODE command|UNICODE]]</var> command now accepts 1154 as a codepage name. This codepage has 92 Unicode characters in the range U+0400 through U+045F, representing the Basic Russian alphabet and all of the Cyrillic extensions excepting the four which have grave accents.


==Reliability enhancements==
===SEQPDL parameter===
The new <var>[[SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List (PDL) in order for the SOUL sequencer to proceed with the next quad code. The minimum and default value is 4096 bytes. The maximum value is 8192 bytes. SEQPDL is a user resettable parameter and can be set on the user's parameter line or reset with the UTABLE command.

Formerly 1024 bytes of PDL free space were hardcoded internally in the Model 204 core. With 1024 bytes there were edge cases where abends would break files, resulting in ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED. SEQPDL is provided to allow enough PDL space so that all of the lower level journaling routines can process error conditions without breaking files.

If your applications are using close to the amount of PDL space currently set by the LPDLST value, you might need to increase LPDLST to reflect SEQPDL's increase in free space.

==New and changed parameters==
In addition to the following specific parameter changes, <var class="product">Model 204</var> parameter descriptions, for example as displayed by the <var>VIEW</var> command, are now in mixed case (unless translated to uppercase due to <var>[[#UPCASMSG (new in V7.5)|UPCASMSG]]</var>.)

Note: The [[Sirius Mods]] parameters are merged with the <var class="product">Model 204</var> base as of <var class="product">Model 204</var> version 7.5, and they are available to all version 7.5 customers. The combined set of parameters is displayed on the [[List of Model 204 parameters]] page. The former Sirius parameters in that listing are marked with an (S). 


===DEFCNTX and APDFCNTX (for $View function only, new in V7.5)===
The string
<code>DEFCNTX</code> or <code>APDFCNTX</code> can be used as an
argument to the <var>[[$VIEW|$View]]</var> function to
get the default file or group context. Using these strings is better than using <code>$View('CURFILE')</code> because:
<ul>
<li><code>CURFILE</code> returns a null string if the default context is a group.

<li><code>CURFILE</code> is affected by the <var>IN</var> clause prior to a <var>Begin</var> command and
can be affected by the <var>In</var> clause prior to many SOUL statements.
</ul>

If there is no default context, <code>$View('DEFCNTX')</code> returns a null
string.

Otherwise <code>$View('DEFCNTX')</code> returns the type of context (<code>FILE</code>, <code>TEMP GROUP</code>, or
<code>PERM GROUP</code>) followed by the file or group name, with trailing blanks
removed.

<code>$View('APDFCNTX')</code> returns the same information based on the default
context when the APSY was entered.

Note: These <code>$View</code> arguments were implemented as part of
maintenance to version 7.5 (via zap number 54). They are not available as ordinary parameters on the <var>VIEW</var> command.
In version 7.6 of Model 204,
they will also be available with the <var>VIEW</var> command.


===DSPOPT (change to default setting)===
The default setting for [[DSPOPT parameter|DSPOPT]] has been changed from X'00' to X'01'. The X'01' setting allocates space for servers in memory in chunks of 4K pages, not as a permanent contiguous area. This allocation lets you move fewer 4K pages, keeping the virtual storage allocated for servers in memory less fragmented and possibly using fewer paging tables.

===ECPSIZE (change to max value)===
The maximum value setting for [[ECPSIZE parameter|ECPSIZE]] has been increased from 1310680 to 1966020 to accommodate more [[Release notes for Model 204 version 7.5 (DRAFT)#External Call Facility .28ECF.29|External Call Facility]] parameters.

===FILEORG (new settings)===
<ul>
<li>
The <var>[[FILEORG parameter|FILEORG]] X'100'</var> setting for enhanced data handling files is now available.

X'100' enables a number of enhancements to the file structure, including: 
<ul>
<li>[[Release notes for Model 204 version 7.5 (DRAFT)#Support for physical field groups|Support for physical field groups]] </li>

<li>The definition of as many as 32000 fields in a file </li>

<li>System maintained [[Field design (File management)#Automatic Fields|Automatic fields]] </li>

<li>[[Field design (File management)#Field constraints|Field constraints]] providing content validation </li>

<li>Improved space management of fields containing [[Field design (File management)#BLOB, CLOB, and MINLOBE attributes|Large Objects]] </li>

<li>[[#New field attributes|New DEFINE FIELD attributes]], such as <var>CHUNK</var>
</ul>

If X'100' is selected, the X'80' bit (optimized field extraction files) is automatically set.</li>

<li>The <var>FILEORG X'200'</var> setting for large file support is now available. </li>

X'200' allows files to hold up to 48 million records.
</li>
</ul>

===FISTAT (change to X'08' setting)===
The <var>[[FISTAT parameter|FISTAT]] X'08'</var> (file full) setting is now automatically cleared in a transaction back out file if table D is increased enough so that DSIZE is greater than or equal to DPGSRES+DPGSUSED.

===LRETBL (setting increase may be necessary)===
Because there might be a slight increase in record locking table usage in V7.5, an increase in the value of the <var>[[LRETBL parameter|LRETBL]]</var> parameter is advised. The amount of the increase is best estimated by multiplying by 16 the <code>HWM HEADERS</code> value (from a <var>[[MONITOR ENQ command|MONITOR ENQ]]</var> report), then dividing by the value of the <var>NUSERS</var> parameter. For example, if <code>HWM HEADERS = 100000</code> and <code>NUSERS=2000</code>, the recommended <var>LRETBL</var> increase is <code>16*100000/2000</code>, or 800.

===MISCOPT (obsolete)===
The <var>[[MISCOPT parameter|MISCOPT]]</var> parameter is now obsolete. In Model 204 version 7.5, MISCOPT is still viewable but is not resettable.

===MODTIM (new in V7.5)===
The <var>[[MODTIM parameter|MODTIM]]</var> system parameter displays the most recent assembly date and time of the Model 204 load module.

===OUTPUT (change to allow OUTPUT=DUMMY)===
IODEV=3 threads definitions now allow OUTPUT=DUMMY.
When defining IODEV=3 threads, if output is not required, the OUTPUT parameter can be coded as OUTPUT=DUMMY.
For example:
IODEV=3,INPUT=IOD3IN1,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN2,OUTPUT=DUMMY
IODEV=3,INPUT=IOD3IN3,OUTPUT=DUMMY
and so on.

This means that no DD statement is required for the output data set, and in cases where many
IODEV=3 threads are defined to simulate a large number of users, this enhancement will reduce the number of DD statements required by one half.

===RECLOCKO (X'04' bit now ignored)===
The <var>[[RECLOCKO parameter|RECLOCKO]]</var> X'04' bit is now ignored, and the extra information of the conflicting user number and lock time are now always available.

===RESPAGE (new in V7.5)===
The <var>[[RESPAGE parameter|RESPAGE]]</var> parameter activates the APSY Precompiled Procedures in storage feature using above the bar pages by specifying a number of 4K operating system pages.

===RETRVKEY (change to allow forward retrieve PF key)===
New in this release, if you specify a non-zero setting of <var>[[RETRVKEY parameter|RETRVKEY]]</var>:
<ul>
<li>If you have set the <code>X'01'</code> or <code>X'10'</code> bits of the <var>[[RETRVOPT parameter|RETRVOPT]]</var> parameter, you can use a
forward retrieve PF key, in addition to the backward retrieve PF key specified by <var>RETRVKEY</var>.
'''Note:'''
If either of these bits is set, the <code>X'02'</code> bit is strongly recommended as well.
<li>The size of the allocated storage area, and hence the number and length of input lines available for retrieval, is specified
by the value of the <var>[[RETRVBUF parameter|RETRVBUF]]</var> parameter.</ul>

===SEQPDL (new in V7.5)===
The <var>[[Release notes for Model 204 version 7.5 (DRAFT)#SEQPDL parameter|SEQPDL]]</var> parameter controls the amount of free space that must be present in the user's Push Down List in order for the SOUL sequencer to proceed with the next quad code. SEQPDL allows enough PDL space for the lower level journaling routines to handle error conditions properly without breaking files and causing ERROR 2126 USER'S PUSHDOWN LIST OVERFLOWED.

===SESMAXTO (new in V7.5)===
The <var>[[SESMAXTO parameter|SESMAXTO]]</var> parameter can be used limit the maximum [[Sessions|session]] timeout value or to cause all current closed sessions to be immediately discarded.

===SMFSVC (obsolete)===
The <var>[[SMFSVC parameter|SMFSVC]]</var> parameter is [[Release notes for Model 204 version 7.5 (DRAFT)#Writing records to the SMF data set|obsolete]] as of Model 204 version 7.5.

===UPCASMSG (new in V7.5)===
The <var>[[UPCASMSG parameter|UPCASMSG]]</var> parameter can be used to translate messages issued by <var class="product">Model 204</var> to uppercase; otherwise (depending on the message being issued) they are displayed in mixed (upper and lower) case.




==Documentation conversion==
Rocket Model 204 documentation is being converted from individual manuals in PDF format to a set of cross-linked HTML articles in this integrated wiki, M204wiki.

As of Model 204 release 7.5, several manuals are now in wiki format and the rest remain in PDF format, available from the [http://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm Rocket Software Documentation Library].

For details, see [[Model 204 and Sirius documentation]].

==New and updated messages==

Many messages have been updated and added in this release. See [[New and updated messages in Model 204 version 7.5]] for details.

[[Category: Release notes]]