Fast/Reload V7.8 changes - Revision history

Admin: Content removed to M2o4int page of same name

2013-10-17T21:42:46Z

Content removed to M2o4int page of same name

Dme at 19:49, 19 September 2011

2011-09-19T19:49:27Z

← Older revision		Revision as of 19:49, 19 September 2011
Line 132:		Line 132:

	===REPT -> ONE STORE-x NONE===		===REPT -> ONE STORE-x NONE===
	Case: Changing a field that was <var>REPEATABLE</var> in the <var>UAI</var> to <var>AT-MOST-ONE</var>.		Case: Changing a field that was <var>REPEATABLE</var> in the <var>UAI</var> to <var>AT-MOST-ONE</var>,
			with either <var>STORE-DEFAULT NONE</var> or <var>STORE-NULL NONE</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:

Dme at 19:27, 19 September 2011

2011-09-19T19:27:17Z

← Older revision		Revision as of 19:27, 19 September 2011
Line 1:		Line 1:

	The following sections contain new or changed features in <var class="product">[[Fast/Reload]]</var>.		The following sections contain new or changed features in <var class="product">[[Fast/Reload]]</var>.

Line 27:		Line 26:
	<ul>		<ul>
	<li>The value returned when referencing a physically absent field		<li>The value returned when referencing a physically absent field
	occurrence that was AT-MOST-ONE prior to the reorganization		occurrence that was <var>AT-MOST-ONE</var> prior to the reorganization
	</ul>		</ul>
	This is shown in the examples using the <var>Print</var> statement,		This is shown in the examples using the <var>Print</var> statement,
Line 44:		Line 43:
	<li>Other changes in these field attributes do not cause the kinds of		<li>Other changes in these field attributes do not cause the kinds of
	problems discussed here.		problems discussed here.
	For example, you can change the DEFAULT-VALUE, STORE-DEFAULT, and		For example, you can change the <var>DEFAULT-VALUE</var>, <var>STORE-DEFAULT</var>, and
	STORE-NONE attributes of an EXACTLY-ONE field without any consequences		<var>STORE-NONE</var> attributes of an <var>EXACTLY-ONE</var> field without any consequences
	for <var class="product">User Language</var> application behavior.		for <var class="product">User Language</var> application behavior.
	<li>Although the examples below all involve fields defined within		<li>Although the examples below all involve fields defined within
Line 86:		Line 85:
	The conditions are shown in the following subsections.		The conditions are shown in the following subsections.
	===EXONE -> non-EXONE with STORE-x NONE===		===EXONE -> non-EXONE with STORE-x NONE===
	Case: Changing a field that was EXACTLY-ONE in the <var>UAI</var> to AT-MOST-ONE or		Case: Changing a field that was <var>EXACTLY-ONE</var> in the <var>UAI</var> to <var>AT-MOST-ONE</var> or
	REPEATABLE, with either STORE-DEFAULT NONE or STORE-NULL NONE.		<var>REPEATABLE</var>, with either <var>STORE-DEFAULT NONE</var> or <var>STORE-NULL NONE</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 106:		Line 105:
	</nowiki></p>		</nowiki></p>
	===REPT -> EXONE===		===REPT -> EXONE===
	Case: Changing a field that was REPEATABLE in the <var>UAI</var> to EXACTLY-ONE.		Case: Changing a field that was <var>REPEATABLE</var> in the <var>UAI</var> to <var>EXACTLY-ONE</var>.

	There is one exception to this, which does not produce a warning:		There is one exception to this, which does not produce a warning:
Line 133:		Line 132:

	===REPT -> ONE STORE-x NONE===		===REPT -> ONE STORE-x NONE===
	Case: Changing a field that was REPEATABLE in the <var>UAI</var> to AT-MOST-ONE.		Case: Changing a field that was <var>REPEATABLE</var> in the <var>UAI</var> to <var>AT-MOST-ONE</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 151:		Line 150:
	<p class="output"><nowiki>Not Present		<p class="output"><nowiki>Not Present
	</nowiki></p>		</nowiki></p>

	===ONE -> ONE with changed DV===		===ONE -> ONE with changed DV===
	Case: Changing a field that was AT-MOST-ONE in the <var>UAI</var> to a		Case: Changing a field that was <var>AT-MOST-ONE</var> in the <var>UAI</var> to a
	different DEFAULT-VALUE in the <var>LAI</var>.		different <var>DEFAULT-VALUE</var> in the <var>LAI</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 173:		Line 172:

	===ONE -> EXONE===		===ONE -> EXONE===
	Case: Changing a field that was AT-MOST-ONE in the <var>UAI</var> to EXACTLY-ONE		Case: Changing a field that was <var>AT-MOST-ONE</var> in the <var>UAI</var> to <var>EXACTLY-ONE</var>
	in the <var>LAI</var>.		in the <var>LAI</var>.

Line 193:		Line 192:
	</nowiki></p>		</nowiki></p>
	===ONE with DV -> REPT===		===ONE with DV -> REPT===
	Case: Changing a field that was AT-MOST-ONE with DEFAULT-VALUE in the <var>UAI</var> to REPEATABLE in the <var>LAI</var>.		Case: Changing a field that was <var>AT-MOST-ONE</var> with <var>DEFAULT-VALUE</var> in the <var>UAI</var> to <var>REPEATABLE</var> in the <var>LAI</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 211:		Line 210:
	</nowiki></p>		</nowiki></p>
	===ONE SD LIT/ALL -> SD NONE===		===ONE SD LIT/ALL -> SD NONE===
	Case: Changing a field that was AT-MOST-ONE with STORE-DEFAULT LIT or ALL in		Case: Changing a field that was <var>AT-MOST-ONE</var> with <var>STORE-DEFAULT</var> <code>LIT</code> or <code>ALL</code> in
	the <var>UAI</var> to STORE-DEFAULT NONE in the <var>LAI</var>.		the <var>UAI</var> to <var>STORE-DEFAULT NONE</var> in the <var>LAI</var>.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 231:		Line 230:
	</nowiki></p>		</nowiki></p>
	===Non-EXONE SN LIT/ALL -> SN NONE===		===Non-EXONE SN LIT/ALL -> SN NONE===
	Case: Changing a field that was AT-MOST-ONE or REPEATABLE with STORE-NULL		Case: Changing a field that was <var>AT-MOST-ONE</var> or <var>REPEATABLE</var> with <var>STORE-NULL</var>
	LIT or ALL in the <var>UAI</var>, to STORE-NULL NONE in the <var>LAI</var>.		<code>LIT</code> or <code>ALL</code> in the <var>UAI</var>, to <var>STORE-NULL NONE</var> in the <var>LAI</var>.

	There is one exception to this, which does not produce a warning:		There is one exception to this, which does not produce a warning:
Line 258:		Line 257:
	</nowiki></p>		</nowiki></p>


	{{Template:Content index: V7.8 Release Notes}}		{{Template:Content index: V7.8 Release Notes}}

Dme: /* REPT -> ONE STORE-x NONE */

2011-09-08T15:21:30Z

REPT -> ONE STORE-x NONE

← Older revision		Revision as of 15:21, 8 September 2011
Line 133:		Line 133:

	===REPT -> ONE STORE-x NONE===		===REPT -> ONE STORE-x NONE===
	Case: Changing a field that was REPEATABLE in the <var>UAI</var> to ~~EXACTLY~~-ONE.		Case: Changing a field that was REPEATABLE in the <var>UAI</var> to AT-MOST-ONE.

	Changed definition in <var>LAI</var>:		Changed definition in <var>LAI</var>:
Line 151:		Line 151:
	<p class="output"><nowiki>Not Present		<p class="output"><nowiki>Not Present
	</nowiki></p>		</nowiki></p>

	===ONE -> ONE with changed DV===		===ONE -> ONE with changed DV===
	Case: Changing a field that was AT-MOST-ONE in the <var>UAI</var> to a		Case: Changing a field that was AT-MOST-ONE in the <var>UAI</var> to a

JAL2 at 19:14, 16 May 2011

2011-05-16T19:14:31Z

← Older revision		Revision as of 19:14, 16 May 2011
Line 1:		Line 1:
	~~{{Hierarchy header}}~~
	The following sections contain new or changed features in <var class="product">[[Fast/Reload]]</var>.		The following sections contain new or changed features in <var class="product">[[Fast/Reload]]</var>.

Line 257:		Line 257:
	</nowiki></p>		</nowiki></p>

	{{~~Hierarchy footer~~}}
			{{Template:Content index: V7.8 Release Notes}}

JAL at 20:13, 11 March 2011

2011-03-11T20:13:58Z

← Older revision		Revision as of 20:13, 11 March 2011
Line 1:		Line 1:
	{{Hierarchy header}}		{{Hierarchy header}}
	The following sections contain new or changed features in [[Fast/Reload]].		The following sections contain new or changed features in <var class="product">[[Fast/Reload]]</var>.

	==Warning messages for some DV, STORE-x, and repeatibility changes==		==Warning messages for some DV, STORE-x, and repeatibility changes==
Line 7:		Line 7:
	create differences in field processing which may not be		create differences in field processing which may not be
	obvious at first glance.		obvious at first glance.

	To highlight this, <var class="product">Fast/Reload</var> will issue a warning		To highlight this, <var class="product">Fast/Reload</var> will issue a warning
	message (MSIR.1037) for each attribute change that may have some		message (MSIR.1037) for each attribute change that may have some
	of these subtle effects.		of these subtle effects.

	For the most part, applications using the reorganized file		For the most part, applications using the reorganized file
	will continue to work as before.		will continue to work as before.
Line 37:		Line 35:
	When changing field attributes as part of reorganizing a file,		When changing field attributes as part of reorganizing a file,
	you should understand the		you should understand the
	impact of the change. To ~~help in~~ this,		impact of the change. To aid this understanding,
	the conditions that cause warning messages are listed in the following		the conditions that cause warning messages are listed in the following
	subsections,		subsections,
Line 48:		Line 46:
	For example, you can change the DEFAULT-VALUE, STORE-DEFAULT, and		For example, you can change the DEFAULT-VALUE, STORE-DEFAULT, and
	STORE-NONE attributes of an EXACTLY-ONE field without any consequences		STORE-NONE attributes of an EXACTLY-ONE field without any consequences
	~~about~~ <var class="product">User Language</var> application behavior.		for <var class="product">User Language</var> application behavior.
	<li>Although the examples below all involve fields defined within		<li>Although the examples below all involve fields defined within
	fieldgroups, the potential problems, and the warning messages issued		fieldgroups, the potential problems, and the warning messages issued

JAL at 20:13, 11 March 2011

2011-03-11T20:13:04Z

Show changes

JAL: Created page with "{{Hierarchy header}} The following sections contain new or changed features in Fast/Reload. ==Warning messages for some DV, STORE-x, and repeatibility changes== V7R2 of ''Mo..."

2010-12-03T20:30:47Z

Created page with "{{Hierarchy header}} The following sections contain new or changed features in Fast/Reload. ==Warning messages for some DV, STORE-x, and repeatibility changes== V7R2 of ''Mo..."

New page

{{Hierarchy header}}
The following sections contain new or changed features in [[Fast/Reload]].

==Warning messages for some DV, STORE-x, and repeatibility changes==
V7R2 of ''Model 204'' introduced several new field attributes.
Reorganizing a file and changing some of these attributes may
create differences in field processing which may not be
obvious at first glance.

To highlight this, ''Fast/Reload'' will issue a warning
message (MSIR.1037) for each attribute change that may have some
of these subtle effects.

For the most part, applications using the reorganized file
will continue to work as before.

One source of possible change in application behavior
involves use of the following User Language constructs:
<ul>
<li>the <tt>Is Present</tt> test
<li>the count returned by a <tt>Count Occurrences Of</tt> statement
<li>the number of iterations of a <tt>For Each Occurrence Of</tt> loop
</ul>
All three of the above constructs have equivalent exposure to the
changes in field attributes, even though the examples below only use
<tt>Is Present</tt>, for brevity.

The other source of possible change in behavior is:
<ul>
<li>the value returned when referencing a physically absent field
occurrence which was AT-MOST-ONE prior to the reorganization
</ul>
This is shown in the examples using the <tt>Print</tt> statement,
although of course the change could be in any kind of reference to the
field value.

When changing field attributes as part of reorganizing a file,
you should understand the
impact of the change; to help in this,
the conditions that cause warning messages are listed in the following
subsections,
along with a very brief example of a possible change in behavior.

'''Notes:'''
<ul>
<li>Other changes in these field attributes do not cause the kinds of
problems discussed here.
For example, you can change the DEFAULT-VALUE, STORE-DEFAULT, and
STORE-NONE attributes of an EXACTLY-ONE field without any consequences
about User Language application behavior.
<li>Although the examples below all involve fields defined within
fieldgroups, the potential problems, and the warning messages issued
by ''Fast/Reload'', apply equally to fields defined outside fieldgroups.
</ul>

In these examples, assume you are reorganizing with UAI/LAI a
file with the following “old” definitions:
<pre>
DEFINE FIELD KEY WITH ORDERED
DEFINE FIELDGROUP GRP
DEFINE FIELD EXO.OLD (FG GRP)
DEFINE FIELD REPT.OLD.MISS (REPT FG GRP)
DEFINE FIELD REPT.OLD.XX (REPT FG GRP)
DEFINE FIELD REPT.OLD.NUL (REPT FG GRP)
DEFINE FIELD AMO.OLD.DF_YY (ONE DV 'YY' FG GRP)
DEFINE FIELD AMO.OLD.SD_LIT (ONE DV 'AA' SD LIT FG GRP)
</pre>
And assume that a record has been stored as follows:
<pre>
Store Record
KEY = 'Some unique value'
Then Continue
Add Fieldgroup GRP
REPT.OLD.XX = 'xx'
REPT.OLD.NUL = ''
AMO.OLD.SD_LIT = 'AA'
End Add
End Store
</pre>
Each example contains a field definition, used in the LAI step,
to highlight one condition, and contains a User Language fragment which
is assumed to be contained within the following:
<pre>
FR Where KEY = 'Some unique value'
For Fieldgroup GRP
... example fragment
End For
End For
</pre>

The conditions are shown in the following subsections.
===EXONE -> non-EXONE with STORE-x NONE===
Case: Changing a field that was EXACTLY-ONE in the UAI to AT-MOST-ONE or
REPEATABLE, with either STORE-DEFAULT NONE or STORE-NULL NONE.

Changed definition in LAI:
<pre>
DEFINE FIELD EXO.OLD (REPT SN NONE FG GRP)
</pre>

User Language fragment:
<pre>
If EXO.OLD Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Present
</pre>

Result after reorg:
<pre>
Not Present
</pre>
===REPT -> EXONE===
Case: Changing a field that was REPEATABLE in the UAI to EXACTLY-ONE.

There is one exception to this, which does not produce a warning:
if the field was not a member of a
fieldgroup in the UAI, and is a member of a fielgroup in the LAI.
Note that the "out of synch" check of this "collecting
loose fields" LAI feature ensures there is no exposure
to a change in User Language behavior when using such a field.

Changed definition in LAI:
<pre>
DEFINE FIELD REPT.OLD.MISS (EXONE FG GRP)
</pre>

User Language fragment:
<pre>
If REPT.OLD.MISS Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Not Present
</pre>

Result after reorg:
<pre>
Present
</pre>

===REPT -> ONE STORE-x NONE===
Case: Changing a field that was REPEATABLE in the UAI to EXACTLY-ONE.

Changed definition in LAI:
<pre>
DEFINE FIELD REPT.OLD.XX (ONE DV 'xx' SD NONE FG GRP)
</pre>

User Language fragment:
<pre>
If REPT.OLD.XX Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Present
</pre>

Result after reorg:
<pre>
Not Present
</pre>
===ONE -> ONE with changed DV===
Case: Changing a field that was AT-MOST-ONE in the UAI to a different DEFAULT-VALUE in the LAI.

Changed definition in LAI:
<pre>
DEFINE FIELD AMO.OLD.DF_YY (ONE DV 'ZZ' FG GRP)
</pre>

User Language fragment:
<pre>
Print AMO.OLD.DF_YY
</pre>

Result prior to reorg:
<pre>
YY
</pre>

Result after reorg:
<pre>
ZZ
</pre>

===ONE -> EXONE===
Case: Changing a field that was AT-MOST-ONE in the UAI to EXACTLY-ONE in the LAI.

Changed definition in LAI:
<pre>
DEFINE FIELD AMO.OLD.DF_YY (EXONE FG GRP)
</pre>

User Language fragment:
<pre>
If AMO.OLD.DF_YY Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Not Present
</pre>

Result after reorg:
<pre>
Present
</pre>
===ONE with DV -> REPT===
Case: Changing a field that was AT-MOST-ONE with DEFAULT-VALUE in the UAI to REPEATABLE in the LAI.

Changed definition in LAI:
<pre>
DEFINE FIELD AMO.OLD.DF_YY (REPT FG GRP)
</pre>

User Language fragment:
<pre>
Print '>' With AMO.OLD.DF_YY With '<'
</pre>

Result prior to reorg:
<pre>
>YY<
</pre>

Result after reorg:
<pre>
><
</pre>
===ONE SD LIT/ALL -> SD NONE===
Case: Changing a field that was AT-MOST-ONE with STORE-DEFAULT LIT or ALL in
the UAI to STORE-DEFAULT NONE in the LAI.

Changed definition in LAI:
<pre>
DEFINE FIELD AMO.OLD.SD_LIT (ONE DV 'AA' SD NONE FG GRP)
</pre>

User Language fragment:
<pre>
If AMO.OLD.SD_LIT Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Present
</pre>

Result after reorg:
<pre>
Not present
</pre>
===Non-EXONE SN LIT/ALL -> SN NONE===
Case: Changing a field that was AT-MOST-ONE or REPEATABLE, with STORE-NULL
LIT or ALL, in the UAI to STORE-NULL NONE in the LAI.

There is one exception to this, which does not produce a warning:
if the field was not a member of a
fieldgroup in the UAI, and it is a member of a fielgroup in the LAI.
Note that the "out of synch" check of this "collecting
loose fields" LAI feature ensures there is no exposure
to a change in User Language behavior when using such a field.

Changed definition in LAI:
<pre>
DEFINE FIELD REPT.OLD.NUL (REPT SN NONE FG GRP)
</pre>

User Language fragment:
<pre>
If REPT.OLD.NUL Is Present Then Print 'Present'
Else Print 'Not Present'; End If
</pre>

Result prior to reorg:
<pre>
Present
</pre>

Result after reorg:
<pre>
Not Present
</pre>

{{Hierarchy footer}}