Obsolete features - Revision history

JAL: minor formatting

2018-06-05T16:25:53Z

minor formatting

← Older revision		Revision as of 16:25, 5 June 2018
Line 222:		Line 222:

	<tr>		<tr>
	<td~~><var~~>U~~</var>~~</td>		<td>U</td>
	<td~~><var~~>Undefined~~</var>~~</td>		<td>Undefined</td>
	</tr>		</tr>

Line 322:		Line 322:

	<tr>		<tr>
	<td>W</td>		<td>U</td>
	<td>~~AT-MOST-ONE in all~~</td>		<td>Undefined</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>U</td>		<td>W</td>
	<td>~~Undefined~~</td>		<td>AT-MOST-ONE in all</td>
	</tr>		</tr>
	</table>		</table>

Dme: /* $DSCR function */

2018-06-05T16:12:07Z

$DSCR function

← Older revision		Revision as of 16:12, 5 June 2018
Line 133:		Line 133:
	</p>		</p>

	===$DSCR function===		===<b id="$DSCR function"></b>$Dscr function===
	<!-- FLD.DME.006.QA in QASHR test that each of the attribute ~~Characters~~ (column 1) below can be produced by $Dscr using various fields - in the most case the only attribute in the DEFINE FIELD is simply the Attribute column in the table -->		<!-- FLD.DME.006.QA in QASHR test that each of the attribute Letters (column 1) below can be produced by $Dscr using various fields - in the most case the only attribute in the DEFINE FIELD is simply the Attribute column in the table -->
	<p>		<p>
	The <var>$Dscr</var> function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDef#$FDef\|$FDef]] that supplanted the <var>$Dscr</var> function.~~</p>~~		The <var>$Dscr</var> function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field.
	~~<p>~~		</p>
	The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute~~. Attributes are listed in [[#$DSCR function\|$DSCR function]]~~. </p>		<p>New application development should incorporate [[$FDef#$FDef\|$FDef]] that supplanted the <var>$Dscr</var> function. The following discussion is provided to maintain existing code.</p>
			<p>Each letter in the returned string represents a particular field attribute.</p>
	<table>		<table>
	<caption>$Dscr field attribute codes (file context)</caption>		<caption>$Dscr field attribute codes (file context)</caption>
	<tr class="head">		<tr class="head">
	<th>~~Character~~</th>		<th>Letter</th>
	<th>Attribute</th>		<th>Attribute</th>
	</tr>		</tr>
Line 230:		Line 231:
	</tr>		</tr>
	</table>		</table>
	<b>How $~~DSCR~~ works</b>		<b>How $Dscr works</b>
	<p>		<p>
	When <var>$Dscr</var> is invoked in file context, the returned string represents the description of the specified field in the current file. </p>		When <var>$Dscr</var> is invoked in file context, the returned string represents the description of the specified field in the current file. </p>
Line 238:		Line 239:
	If a particular letter does not appear in the result of a <var>$Dscr</var> call, then the corresponding attribute does not apply, or the attribute's opposite is in effect. For example, if <code>M</code> (many-valued) does not appear, the field is <var>NON-CODED</var> and <var>NON-FRV</var>, in which case <code>M</code> does not apply, or it is <var>FEW-VALUED</var>. You can resolve this by looking for <code>C</code> and <code>F</code> in the returned string. </p>		If a particular letter does not appear in the result of a <var>$Dscr</var> call, then the corresponding attribute does not apply, or the attribute's opposite is in effect. For example, if <code>M</code> (many-valued) does not appear, the field is <var>NON-CODED</var> and <var>NON-FRV</var>, in which case <code>M</code> does not apply, or it is <var>FEW-VALUED</var>. You can resolve this by looking for <code>C</code> and <code>F</code> in the returned string. </p>
	<p>		<p>
	When <var>$Dscr</var> is invoked in group context, the returned string represents a composite description of the field in all of the files of the current group. Some of the letters imply that the corresponding field attribute is present in all of the files in the group; others imply that the attribute is present in some (at least one) file in the group. If the field specified as the <var>$Dscr</var> argument is not defined in the current file or group, <var>$Dscr</var> returns the character string <code>U</code> (undefined). ~~[[#$DSCR function\|$DSCR function]]~~ lists the individual letters and their meanings in group context. </p>		When <var>$Dscr</var> is invoked in group context, the returned string represents a composite description of the field in all of the files of the current group. Some of the letters imply that the corresponding field attribute is present in all of the files in the group; others imply that the attribute is present in some (at least one) file in the group. If the field specified as the <var>$Dscr</var> argument is not defined in the current file or group, <var>$Dscr</var> returns the character string <code>U</code> (undefined). The following table lists the individual letters and their meanings in group context. </p>
	<table>		<table>
	<caption>$Dscr field attribute codes <br>(group context)</caption>		<caption>$Dscr field attribute codes <br>(group context)</caption>
	<tr class="head">		<tr class="head">
	<th>~~Character~~</th>		<th>Letter</th>
	<th>Attribute</th>		<th>Attribute</th>
	</tr>		</tr>
Line 310:		Line 311:
	</tr>		</tr>
	<tr>		<tr>

	<td>S</td>		<td>S</td>
	<td>~~STRING~~ in ~~all~~</td>		<td>Not BINARY in any</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>T</td>		<td>T</td>

Dme: /* $DSCR function */

2018-06-05T15:57:39Z

$DSCR function

← Older revision		Revision as of 15:57, 5 June 2018
Line 212:		Line 212:
	<tr>		<tr>
	<td>S</td>		<td>S</td>
	<td>~~STRING~~</td>		<td>Not BINARY</td>
	</tr>		</tr>

JAL: add `s`

2018-06-04T15:07:14Z

add <var>s

Show changes

Dme: /* $DSCR function */

2018-06-02T18:18:19Z

$DSCR function

← Older revision		Revision as of 18:18, 2 June 2018
Line 117:		Line 117:

	===$DSCR function===		===$DSCR function===
			<!-- FLD.DME.006.QA in QASHR test that each of the attribute Characters (column 1) below can be produced by $Dscr using various fields - in the most case the only attribute in the DEFINE FIELD is simply the Attribute column in the table -->
	<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDef#$FDef\|$FDef]] that supplanted the $DSCR function.</p>		<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDef#$FDef\|$FDef]] that supplanted the $DSCR function.</p>
	<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>		<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>

Mlarocca at 13:40, 1 August 2014

2014-08-01T13:40:23Z

← Older revision		Revision as of 13:40, 1 August 2014
Line 117:		Line 117:

	===$DSCR function===		===$DSCR function===
	<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$~~Fdef~~#$~~Fdef~~\|$~~Fdef~~]] that supplanted the $DSCR function.</p>		<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDef#$FDef\|$FDef]] that supplanted the $DSCR function.</p>
	<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>		<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>
	<table>		<table>

Mlarocca: /* $DSCR function */

2014-08-01T13:36:05Z

$DSCR function

← Older revision		Revision as of 13:36, 1 August 2014
Line 117:		Line 117:

	===$DSCR function===		===$DSCR function===
	<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$~~FDEF~~#$~~FDEF~~\|$~~FDEF~~]] that supplanted the $DSCR function.</p>		<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$Fdef#$Fdef\|$Fdef]] that supplanted the $DSCR function.</p>
	<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>		<p>The following discussion is provided to maintain existing code. Each letter in the returned string represents a particular field attribute. Attributes are listed in [[#$DSCR function\|$DSCR function]]. </p>
	<table>		<table>

Mlarocca: /* Rules for using statement numbers */

2014-07-14T19:47:37Z

Rules for using statement numbers

← Older revision		Revision as of 19:47, 14 July 2014
Line 99:		Line 99:
	.		.
	.		.
	50. IF $~~CHKTAG~~('DATA') THEN		50. IF $chktag('DATA') THEN
	REREAD SCREEN DATA		REREAD SCREEN DATA
	JUMP TO 1		JUMP TO 1
Line 115:		Line 115:
	END		END
	</p>		</p>

	===$DSCR function===		===$DSCR function===
	<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDEF#$FDEF\|$FDEF]] that supplanted the $DSCR function.</p>		<p>The $DSCR function interprets its character string argument as a field name. It returns a variable-length character string describing the specified field. New application development should incorporate [[$FDEF#$FDEF\|$FDEF]] that supplanted the $DSCR function.</p>

Admin: Admin moved page Obsolete Features to Obsolete features without leaving a redirect: title caps

2014-01-02T17:54:43Z

Admin moved page Obsolete Features to Obsolete features without leaving a redirect: title caps

← Older revision	Revision as of 17:54, 2 January 2014
(No difference)

JAL at 16:43, 2 January 2014

2014-01-02T16:43:51Z

← Older revision		Revision as of 16:43, 2 January 2014
Line 1:		Line 1:
	===Statement numbers===		===Statement numbers===
	<p>This appendix describes certain features of User Language which, while still supported, are generally considered obsolete. They have been superseded by other, more efficient features or techniques. Rocket Software does not recommend using these features in newly written requests and procedures.</p>		<p>This appendix describes certain features of User Language which, while still supported, are generally considered obsolete. They have been superseded by other, more efficient features or techniques. Rocket Software does not recommend using these features in newly written requests and procedures.</p>
	<p>Rocket Software strongly recommends that you use statement labels (see [[Request ~~Composition Rules~~#Statement labels\|Statement labels]]) rather than statement numbers. Although statement numbers are still supported, this section is included primarily as documentation for applications developed using earlier releases of <var class="product">Model 204</var>.</p>		<p>Rocket Software strongly recommends that you use statement labels (see [[Request composition rules#Statement labels\|Statement labels]]) rather than statement numbers. Although statement numbers are still supported, this section is included primarily as documentation for applications developed using earlier releases of <var class="product">Model 204</var>.</p>
	====FOPT parameter====		====FOPT parameter====
	<p>The setting of the FOPT (File Options) parameter determines whether procedures within a file must be labeled or numbered. For more information on the FOPT parameter, refer to the Rocket <var class="product">Model 204</var> Parameter and Command Reference Manual. </p>		<p>The setting of the FOPT (File Options) parameter determines whether procedures within a file must be labeled or numbered. For more information on the FOPT parameter, refer to the Rocket <var class="product">Model 204</var> Parameter and Command Reference Manual. </p>

Obsolete features - Revision history

JAL: minor formatting

Dme: /* $DSCR function */

Dme: /* $DSCR function */

JAL: add s

Dme: /* $DSCR function */

Mlarocca at 13:40, 1 August 2014

Mlarocca: /* $DSCR function */

Mlarocca: /* Rules for using statement numbers */

Admin: Admin moved page Obsolete Features to Obsolete features without leaving a redirect: title caps

JAL at 16:43, 2 January 2014

JAL: add `s`