HLI: Model 204 fields and variables - Revision history

ELowell: /* Using %variables in EDIT and LIST specifications */

2016-07-15T23:56:08Z

Using %variables in EDIT and LIST specifications

← Older revision		Revision as of 23:56, 15 July 2016
Line 693:		Line 693:
	===Using %variables in EDIT and LIST specifications===		===Using %variables in EDIT and LIST specifications===
	<p>		<p>
	You can use a %variable in the field name list of an EDIT or LIST specification for the IFFTCH, IFGET, IFGETX, IFMORE, IFMOREX, IFPUT, IFSTOR, and IFUPDT calls. See the specific ~~calls~~ in ~~the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for more details.</p>		You can use a %variable in the field name list of an EDIT or LIST specification for the IFFTCH, IFGET, IFGETX, IFMORE, IFMOREX, IFPUT, IFSTOR, and IFUPDT calls. See the specific description of each function in [[:Category:HLI functions\|HLI functions]] for more details.</p>

	===Example of using a %variable===		===Example of using a %variable===

ELowell: /* Storage characteristics of a field */

2016-07-15T23:53:57Z

Storage characteristics of a field

← Older revision		Revision as of 23:53, 15 July 2016
Line 356:		Line 356:
	<td>Model 204 stores FLOAT fields in floating-point form using IBM hardware floating-point representation. You must supply a LENGTH value with FLOAT to indicate the precision of the floating-point field being defined.		<td>Model 204 stores FLOAT fields in floating-point form using IBM hardware floating-point representation. You must supply a LENGTH value with FLOAT to indicate the precision of the floating-point field being defined.
	<p>		<p>
	Model 204 cancels a request to store invalid floating point data in a file that has the NUMERIC VALIDATION file model option set. See [[#NUMERIC VALIDATION violations\|NUMERIC VALIDATION violations]] for information about FLOAT violations. ~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for~~ a description of floating-point format for IFFTCH, IFUPDT, IFGET, and IFPUT. </p>		Model 204 cancels a request to store invalid floating point data in a file that has the NUMERIC VALIDATION file model option set. See [[#NUMERIC VALIDATION violations\|NUMERIC VALIDATION violations]] for information about FLOAT violations.
	</td>		For a description of floating-point format for IFFTCH, IFUPDT, IFGET, and IFPUT, see [[HLI: Field formatting options for HLI calls#Using EDIT format codes for a retrieval call\|Using EDIT format codes for a retrieval call]] and [[HLI: Field formatting options for HLI calls#Using EDIT format codes for an updating call\|Using EDIT format codes for an updating call]].</p></td>
	</tr>		</tr>
	<tr>		<tr>

ELowell: /* AT-MOST-ONE violations */

2016-07-15T23:39:24Z

AT-MOST-ONE violations

← Older revision		Revision as of 23:39, 15 July 2016
Line 554:		Line 554:
	If a field is defined as AT-MOST-ONE, only one occurrence of that field can be stored in a particular record. </p>		If a field is defined as AT-MOST-ONE, only one occurrence of that field can be stored in a particular record. </p>

	<p class="note"><b>Note:</b>If the HLI program issues a call to IFSTOR, IFUPDT, or IFPUT, and attempts to store more than one (that is, a second) occurrence of the field within a particular record, Model 204 cancels the call and returns a completion code of 202 to the HLI program. </p>		<p class="note"><b>Note:</b> If the HLI program issues a call to IFSTOR, IFUPDT, or IFPUT, and attempts to store more than one (that is, a second) occurrence of the field within a particular record, Model 204 cancels the call and returns a completion code of 202 to the HLI program. </p>
	<p>		<p>
	If a completion code of 202 is returned, use the IFEFCC call to determine which records are creating the AT-MOST-ONE violation~~. See the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for information about IFEFCC~~.</p>		If a completion code of 202 is returned, use the <var>[[IFEFCC (HLI function)\|IFEFCC]]</var> call to determine which records are creating the AT-MOST-ONE violation.</p>

	==Using %variables==		==Using %variables==

ELowell: /* Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT */

2016-07-15T23:37:27Z

Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT

← Older revision		Revision as of 23:37, 15 July 2016
Line 505:		Line 505:
	<li>If a violation occurs during IFUPDT or IFPUT processing, Model 204 stops processing the call and returns a completion code of 4 to the HLI program. </li>		<li>If a violation occurs during IFUPDT or IFPUT processing, Model 204 stops processing the call and returns a completion code of 4 to the HLI program. </li>
	</ul>		</ul>
	~~<p>~~
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for a description of IFFTCH, IFUPDT, IFGET, IFMORE, and IFPUT calls. </p>~~

	===LENGTH violations===		===LENGTH violations===

ELowell: /* Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT */

2016-07-15T23:36:34Z

Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT

← Older revision		Revision as of 23:36, 15 July 2016
Line 495:		Line 495:
	===Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT===		===Field-level violations for IFFTCH, IFUPDT, IFGET, and IFPUT===
	<p>		<p>
	Model 204 treats HLI calls that compile IFGET (or IFMORE) and IFPUT specifications in a special way, because a specification compiled by IFGET (or IFMORE) can be executed by IFPUT, and vice versa. The same is true for IFFTCH and IFUPDT specifications on a multiple cursor IFSTRT thread. </p>		Model 204 treats HLI calls that compile <var>[[IFGET (HLI function)\|IFGET]]</var> (or <var>[[IFMORE (HLI function)\|IFMORE]]</var>) and <var>[[IFPUT (HLI function)\|IFPUT]]</var> specifications in a special way, because a specification compiled by IFGET (or IFMORE) can be executed by IFPUT, and vice versa. The same is true for <var>[[IFFTCH (HLI function)\|IFFTCH]]</var> and <var>[[IFUPDT (HLI function)\|IFUPDT]]</var> specifications on a multiple cursor IFSTRT thread. </p>
	<p>		<p>
	If an HLI thread has READ, UPDATE, or ADD access to a field, you can reference the field using IFFTCH or IFUPDT on a multiple cursor IFSTRT thread, or IFGET or IFPUT on a single cursor IFSTRT thread. </p>		If an HLI thread has READ, UPDATE, or ADD access to a field, you can reference the field using IFFTCH or IFUPDT on a multiple cursor IFSTRT thread, or IFGET or IFPUT on a single cursor IFSTRT thread. </p>

ELowell: /* Specifying the %variable parameters */

2016-07-15T23:33:30Z

Specifying the %variable parameters

← Older revision		Revision as of 23:33, 15 July 2016
Line 685:		Line 685:
	You assign one or more %variables in an HLI call by specifying the %variable input parameters, that is, %variable buffer and %variable specification, in the parameter list. </p>		You assign one or more %variables in an HLI call by specifying the %variable input parameters, that is, %variable buffer and %variable specification, in the parameter list. </p>
	<p>		<p>
	Note that if you specify one, you must specify the other. Specify each of the %variable parameters as a character string, whose maximum length is the input buffer size. Refer to the ~~<var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for a description of~~ HLI ~~calls and their~~ parameter ~~lists~~. </p>		Note that if you specify one, you must specify the other. Specify each of the %variable parameters as a character string, whose maximum length is the input buffer size. Refer to the functions in [[:Category:HLI functions\|HLI functions]] to see each function's parameter list. </p>
	<p>		<p>
	The %variable buffer parameter (%VARBUF in the parameter list descriptions) contains the values to be assigned to the %variables that are used by the call. </p>		The %variable buffer parameter (%VARBUF in the parameter list descriptions) contains the values to be assigned to the %variables that are used by the call. </p>
	<p>		<p>
	The %variable specification (%VARSPEC in the parameter list descriptions) describes the format of the data contained in the %variable buffer and, in some cases, the list of %variables to be assigned. The %variable specification follows the syntax of the LIST, DATA, or EDIT specifications used with IFUPDT or IFPUT. </p>		The %variable specification (%VARSPEC in the parameter list descriptions) describes the format of the data contained in the %variable buffer and, in some cases, the list of %variables to be assigned. The %variable specification follows the syntax of the LIST, DATA, or EDIT specifications used with <var>[[IFUPDT (HLI function)\|IFUPDT]]</var> or <var>[[IFPUT (HLI function)\|IFPUT]]</var>. </p>
	<p>		<p>
	See [[#Assignment of %variables\|Assignment of %variables]] for more information about the %variable specification~~. Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for a description of IFUPDT and IFPUT~~. </p>		See [[#Assignment of %variables\|Assignment of %variables]] for more information about the %variable specification.</p>

	===Using %variables in EDIT and LIST specifications===		===Using %variables in EDIT and LIST specifications===

ELowell: /* UNIQUE violations */

2016-07-15T23:27:16Z

UNIQUE violations

← Older revision		Revision as of 23:27, 15 July 2016
Line 546:		Line 546:
	<p class="note"><b>Note:</b> If you use IFUPDT, IFSTOR, IFPUT, or IFBREC and attempt to store the same value of a UNIQUE field in another record, Model 204 cancels the call and returns a completion code of 200 to the HLI program. </p>		<p class="note"><b>Note:</b> If you use IFUPDT, IFSTOR, IFPUT, or IFBREC and attempt to store the same value of a UNIQUE field in another record, Model 204 cancels the call and returns a completion code of 200 to the HLI program. </p>
	<p>		<p>
	If a completion code of 200 is returned, use the IFEFCC call to determine which records are creating the uniqueness violation~~. See the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for more information about IFEFCC~~.</p>		If a completion code of 200 is returned, use the <var>[[IFEFCC (HLI function)\|IFEFCC]]</var> call to determine which records are creating the uniqueness violation.</p>

	===NUMERIC VALIDATION violations===		===NUMERIC VALIDATION violations===

ELowell at 23:25, 15 July 2016

2016-07-15T23:25:40Z

← Older revision		Revision as of 23:25, 15 July 2016
Line 210:		Line 210:
	Initially load a file </li>		Initially load a file </li>
	<li>		<li>
	Add a new field name to an established file (IFDFLD) </li>		Add a new field name to an established file (<var>[[IFDFLD (HLI function)\|IFDFLD]]</var>) </li>
	<li>		<li>
	Redefine a field description (IFRFLD)		Redefine a field description (<var>[[IFRFLD (HLI function)\|IFRFLD]]</var>)

	<p class="note"><b>Note:</b> If you define a field but do not specify field attributes, Model 204 assigns default attributes~~. Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for a description of the IFDFLD call~~. </p>		<p class="note"><b>Note:</b> If you define a field but do not specify field attributes, Model 204 assigns default attributes.</p>
	</li>		</li>
	</ul>		</ul>

ELowell: /* Overview */

2016-07-15T23:23:18Z

Overview

← Older revision		Revision as of 23:23, 15 July 2016
Line 4:		Line 4:
	This topic describes two basic Model 204 database constructs, fields and variables, for application programmers who are using the Host Language Interface facility. </p>		This topic describes two basic Model 204 database constructs, fields and variables, for application programmers who are using the Host Language Interface facility. </p>

	See the ~~<var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for more information about HLI calls.		See the [[HLI: Function summary\|HLI function summary]] for more information about HLI function calls.

	See [[Field design]] and [[Using variables and values in computation]] for more information about Model 204 fields and variables.		See [[Field design]] and [[Using variables and values in computation]] for more information about Model 204 fields and variables.

ELowell at 16:33, 29 April 2016

2016-04-29T16:33:59Z

← Older revision		Revision as of 16:33, 29 April 2016
Line 890:		Line 890:

	==See also==		==See also==
	{{Template: HLI topic list}}		{{Template: HLI programming topic list}}

	[[Category: Host Language Interface]]		[[Category: Host Language Interface]]