View source for HLI: Field formatting options for HLI calls


==Overview==
<p>
This topic describes in detail the field formatting options for specifying data that is passed between Model 204 and an HLI application that uses an IFSTRT thread. </p>
<p>
Use the information in this topic to code the edit specification parameter in an IFFTCH, IFGET, IFGETX, IFGETV, IFMORE, IFMOREX, IFUPDT, IFSTOR, or IFPUT call.</p>
<p>
The following calls retrieve data:</p>
<ul>
<li>IFFTCH</li>
<li>IFGET</li>
<li>IFGETX</li>
<li>IFGETV</li>
<li>IFMORE</li>
<li>IFMOREX</li>
</ul>
<p>The following calls perform updating functions against the database:</p>
<ul>
<li>IFUPDT</li>
<li>iFSTOR</li>
<li>IFPUT</li>
</ul>

<p class="note"><b>Note:</b> [[IFFTCH call|IFFTCH]], [[IFUPDT call|IFUPDT]], and [[IFSTOR call|IFSTOR]] are used on a multiple cursor IFSTRT thread; [[IFGET call|IFGET]], [[IFGETX call|IFGETX]], [[IFGETV call|IFGETV]], [[IFMORE call|IFMORE]], [[IFMOREX call|IFMOREX]], and [[IFPUT call|IFPUT]] are used on a single cursor IFSTRT thread. </p>

==Using a LIST specification for a retrieval call==
<p>
An edit specification parameter specifies a LIST format option for an IFFTCH, IFGET, IFGETX, IFMORE, or IFMOREX (retrieval) call using the following syntax: </p>
<p class="syntax">LIST (<span class="term">field name list</span>); </p>
<p>
An edit specification parameter specifies a LIST format option for an IFFTCH call against a value set cursor or an IFGETV call using the following syntax:</p>
<p class="syntax">LIST;</p>
<p>
The retrieval call returns the value of the fields named in the field name list in the following format: </p>
<p class="syntax">'<span class="term">field value1</span>' '<span class="term">field value2</span>' ... '<span class="term">field value N</span>'; </p>
<p>
where: </p>
<ul>
<li>
Single quotation marks enclose each value and blanks separate the values. </li>
<li>
Single quotation marks in the data itself are converted to two quotes. </li>
<li>
Fields that are not contained in the record are returned as two single quotes (' '), which is the null value. </li>
<li>
You may use a %variable in the field name list in the LIST specification. The value for the %variable is specified in the %VARBUF and %VARSPEC parameters.</li>
</ul>

==Using a DATA specification for a retrieval call==
<p>
An edit specification parameter specifies a DATA format option for an IFFTCH, IFGET, IFGETX, IFMORE, or IFMOREX call using either of the following syntax forms: </p>
<p class="syntax">DATA (<span class="term">field name list</span>); 
DATA;</p>
<p>
The retrieval call returns the value of the fields named in the field name list in the following format: </p>
<p class="syntax"><span class="term">fn1</span>='<span class="term">value1</span>' <span class="term">fn2</span>='<span class="term">value2</span>'... <span class="term">fnN</span>='<span class="term">valueN</span>';</p>
<p>
where fields that are not contained in the record appear as <span class="term">fn</span>=''. </p>

<p class="note"><b>Note:</b> The DATA format option without a field name list retrieves all fields in the record and formats data in the same manner. </p>

==Using an EDIT specification for a retrieval call==
<p>
An edit specification parameter specifies an EDIT format option for an IFFTCH, IFGET, IFGETX, IFMORE, or IFMOREX call using either of the following syntax forms: </p>

<p class="syntax">EDIT (<span class="term">field name list</span>) (<span class="term">edit formats</span>);
EDIT (<span class="term">field name list1</span>) (<span class="term">edit format1</span>) (<span class="term">field name list2</span>)(<span class="term">edit format2</span>);</p>
<p>
An edit specification parameter specifies an EDIT format option for an IFFTCH call against a value set cursor or an IFGETV call using the following syntax:</p>
<p class="syntax">EDIT (<span class="term">edit format</span>);</p>
<p>
The retrieval call returns the value of the field(s) named in the field name list in the format that is specified. See [[#Examples of numeric edit format conversion|Examples of numeric edit format conversion]] for a listing of edit codes that can be used in an EDIT specification for IFFTCH, IFGET, IFGETV, IFGETX, IFMORE, or IFMOREX. </p>

===Guidelines for specifying an EDIT format===
<p>
When specifying an EDIT format, the following guidelines apply: </p>
<ul>
<li>You can insert blanks before and/or after the field name list and edit format entries in the EDIT specification. </li>
<li>Separate individual entries inside the edit format list with a comma. </li>
<li>Repetition factors and parentheses are allowed. Blanks following a repetition factor or surrounding commas and parentheses are optional.

The following examples illustrate repetition factors:
<p class="syntax">2A(10),J(2)</p>
<p>is equivalent to:</p>
<p class="syntax">A(10),A(10),J(2)</p>
<p>And</p>
<p class="syntax">2(A(10),J(2))</p>
<p>is equivalent to:</p>
<p class="syntax">A(10),J(2),A(10),J(2)</p>
</li>
<li>
For each name in the field name list, one edit format is selected. Repetition factors are expanded before the selection occurs. COL, POS, and X are not selected by field names, but are executed as they are encountered in the list of edit formats.</li>
<li>
You can use a %variable in the field name list in the EDIT specification. The value for the %variable is specified in the %VARBUF and %VARSPEC parameters.

<p>If the edit formats are exhausted before the field name list, selection wraps around to the beginning of the list of formats. Model 204 ignores extra items.</p>
</li>
</ul>

===Using the V format===
<p>
When the V format is specified, the edit format specified immediately after the V determines the format of the data values.</p>
<p>
For example, if the EDIT specification contains VA(4), the following hexadecimal data would be stored in the data buffer to represent the three values, ABCD, 1234, and XYZ:</p>
<p class="syntax">00000003C1C2C3C4F1F2F3F4E7E8E940</p>
<p>
Note that the following edit formats cannot be specified after the V: </p>
<ul>
<li>M and V, which describe a collection of values. </li>
<li>COL, POS, and X, which alter the data buffer pointers without manipulating a value. </li>
<li>A left parenthesis (( ), which indicates a group of formats to be repeated.</li>
</ul>
<p>
V processes field occurrences in the same manner as the M function. The field name corresponding to the V format in the field name list is specified as field name(n), the first <var class="term">n</var>-1 occurrences of the field are omitted.</p>
<p>
Note that the VL format is equivalent to the M format, except that the data values are preceded by a 4-byte count rather than by a 1-byte count. </p>

===Handling fields that do not occur in the record===
<p>
Model 204 handles fields that do not occur in the record in the following ways: </p>
<ul>
<li>If the first or <var class="term">n</var>th occurrence of a field is specified and the field is not present in the record or fewer than n occurrences exists, then the appropriate pad characters are supplied for A(<var class="term">n</var>), J(<var class="term">n</var>), L(<var class="term">n</var>), and U(<var class="term">n</var>) formats, or zero length is indicated for L and M formats.

<p>No characters are returned for A and J formats. A numeric zero is returned in the appropriate format for the B, P, E, Z, and F formats.</p>
</li>
<li>If all occurrences are specified and there are no occurrences of the field in the record, no edit formats are used for that field. Place requests for fieldname(*) at the end of a list or in a separate IFFTCH, IFMORE, or IFMOREX call.</li>
<li>Fields with the INVISIBLE attribute are treated as if the field does not occur in the record.</li>
</ul>

===Examples of numeric edit format conversion===
<p>
The following table shows examples of how Model 204 converts data for a numeric edit format specification.</p>
<table>
<caption>Examples of numeric edit format conversion</caption>
<tr class="head">
<th>Edit format <br />specification</th>
<th>Model 204 data <br />(character)</th>
<th>User data <br />(hexadecimal)</th>
</tr>
<tr>
<td>Z(5,2)</td>
<td> 18.21</td>
<td>F0 F1 F8 F2 C1</td>
</tr>
<tr>
<td>Z(5,2)</td>
<td>-18.21</td>
<td>F0 F1 F8 F2 D1</td>
</tr>
<tr>
<td>P(5,2)</td>
<td> 18.21</td>
<td>01 82 1C</td>
</tr>
<tr>
<td>P(3)</td>
<td>-372</td>
<td>37 2D</td>
</tr>
<tr>
<td>B(31,0)</td>
<td> 4095</td>
<td>00000FFF</td>
</tr>
<tr>
<td>B(15,2)</td>
<td> 10.25</td>
<td>0029 (binary 001010.01)</td>
</tr>
<tr>
<td>F(4)</td>
<td> 2</td>
<td>41200000</td>
</tr>
</table>

==Using EDIT format codes for a retrieval call==
<p>
The following table describes the edit format codes that may be specified in the (edit format) with the EDIT option in an IFFTCH, IFGET, IFGETV, IFGETX, IFMORE, or IFMOREX (retrieval) call.</p>
<table>
<caption>EDIT format codes used with a retrieval call</caption>
<tr class="head">
<th>Code</th>
<th>Description</th>
</tr>
<tr>
<td>A</td>
<td>Place an <var class="term">n</var>-character field value into <var class="term">n</var> characters.</td>
</tr>
<tr>
<td>A(<var class="term">n</var>)</td>
<td>
<P CLASS="zcellbody">
Left-justify a field value in an <var class="term">n</var>-character area. This format pads with blanks if the field value is less than <var class="term">n</var> or truncates if the field value is greater than <var class="term">n</var> (the maximum of <var class="term">n</var> is 255).</p>
</td>
</tr>
<tr>
<td>B(<var class="term">precision</var>,<var class="term">scale</var>)</td>
<td>The value is returned in two's complement binary form. <var class="term">precision</var> specifies the number of bits in the numeric value, exclusive of the sign bit. Only two precision types are supported: 15 (halfword) and 31 (fullword). If both <var class="term">precision</var> and <var class="term">scale</var> are omitted, <var class="term">precision</var> defaults to 15.
<p><var class="term">scale</var> specifies the number of digits to the right of an implied binary point. The scale must not exceed the precision. If <var class="term">scale</var> is omitted, it defaults to 0, indicating an integer value. A maximum of 12 significant bits of a fraction are returned. If <var class="term">scale</var> is more than 12, the low-order bits are 0.</p></td>
</tr>
<tr>
<td>COL(<var class="term">n</var>) or COLUMN(<var class="term">n</var>)</td>
<td>Adds blanks to character position <var class="term">n</var> in the data area. Specifying a column that has already been passed over is an error.</td>
</tr>
<tr>
<td rowspan="1" colspan="2">E(<var class="term">total length</var>,<var class="term">significant digits</var>,<var class="term">fractional digits</var>)</td>
</tr>
<tr>
<td rowspan="2" colspan="1">&nbsp;</td>
<td rowspan="2" colspan="1">Convert numeric format (FLOAT, BINARY, CODED, NON-CODED) numbers to exponential format. The total length includes the number of significant digits as well as space for E and the exponent, and space for both any decimal point and for any positive and/or negative signs.
<p>
An insufficient total length results in a truncated representation of the given number. The number of significant digits is the total of whole number digits plus fractional digits. The maximum number of significant digits used in conversions and mathematical operations by Model 204 is 15 (extra digits are rounded to 15).</p>
</td>
</tr>
<tr>
</tr>
<tr>
<td>F(<var class="term">n</var>)</td>
<td>The value is returned as a floating-point number. 
<ul>
<li>If <var class="term">n</var> is 16, the value is truncated or expanded to an extended precision, floating-point number (occupies 16 bytes and holds up to 31 significant digits).</li> 
<li>If <var class="term">n</var> is 8, the character string is truncated or expanded to a long precision, floating-point number (occupies 8 bytes and holds up to 15 significant digits).</li>
<li>If <var class="term">n</var> is 4, the character string is first truncated or expanded to a long precision, floating-point number and is then rounded and truncated to a short precision number (occupies 4 bytes and holds up to 6 significant digits).</li>
</ul>
<p>Decimal floating-point fractions are represented internally as imperfect, base 16, floating-point numbers. To provide exact equality when two floating-point values are compared, the numbers are rounded. Also, when a floating-point value is too large or too small for its field or %variable, the value is truncated or expanded so that it correctly fits.</p>
<p>Rounding, truncation, or expansion occurs in the following cases:</p>
<ul>
<li>Rounding occurs after each arithmetic operation involving floating-point numbers.</li>
<li>If the field is KEY, the value to be indexed is rounded.</li>
<li> If the field is used in a direct Table B search in an IFFIND call, the value to be searched for is rounded to long precision (8 bytes), and each field accessed in Table B is likewise rounded before comparison. </li>
<li>If the field will be used in a sort key, the value is rounded before being concatenated to the key. </li>
<li>If the source number is a floating-point number longer than the field or %variable into which it is stored, the source number is rounded and truncated so that it correctly fits.</li>
<li>If the source number is a floating-point number shorter than the field, the source number is rounded to its maximum significant digits and expanded with zeros to the longer precision. </li>
</ul></td>
</tr>
<tr>
<td>J</td>
<td>Same as A.</td>
</tr>
<tr>
<td>J(<var class="term">n</var>)</td>
<td>Right-justify a field value in an n-character area. Pads with blanks if the field value is less than <var class="term">n</var>, or truncates if the field value is greater than <var class="term">n</var> (the maximum value of <var class="term">n</var> is 255).</td>
</tr>
<tr>
<td>L</td>
<td>The first byte is set to the number of data bytes that follow it. For example, 'ABC' would appear as the four-byte string X'03C1C2C3'.</td>
</tr>
<tr>
<td>L(<var class="term">n</var>)</td>
<td>Same as J(<var class="term">n</var>) except pads with binary zeros instead of blanks.</td>
</tr>
<tr>
<td>M</td>
<td>Collect all the occurrences of a field into a single data area. This area begins with a byte containing the number of occurrences. Each occurrence follows in L format. Specifying fieldname(<var class="term">n</var>) in the field name list causes the first <var class="term">n</var>-1 occurrences of the field to be omitted.</td>
</tr>
<tr>
<td>M(<var class="term">n</var>)</td>
<td>Like M but each occurrence is in L(<var class="term">n</var>) format.</td>
</tr>
<tr>
<td>P(<var class="term">precision</var>,<var class="term">scale</var>)</td>
<td>The value is returned in packed-decimal form. <var class="term">precision</var> specifies the number of digits (not bytes) in the numeric value, exclusive of the sign. The maximum precision for a packed-decimal field is 15. If an even precision is specified, one extra high-order 0 digit is returned. If both <var class="term">precision</var> and <var class="term">scale</var> are omitted, the precision defaults to 5. 
<p><var class="term">scale</var> specifies the number of digits to the right of an implied decimal point. The scale must not exceed the precision. If <var class="term">scale</var> is omitted, it defaults to 0, indicating an integer value. No error is indicated if the fractional portion of a value is truncated.</p></td>
</tr>
<tr>
<td>POS(<var class="term">n</var>)</td>
<td>Skip to character position n in the data area, bypassing the original contents from the application program. Specifying a column which has already been passed over is an error.</td>
</tr>
<tr>
<td>U</td>
<td>Same as A. The U function can be used with unformatted data such as bit strings or floating-point numbers.</td>
</tr>
<tr>
<td>U(<var class="term">n</var>)</td>
<td>Left-justify a field value in an <var class="term">n</var>-character area; pads with binary zeros or truncate on the right as appropriate (<var class="term">n</var>&lt;255).</td>
</tr>
<tr>
<td>V</td>
<td>Collect all occurrences of a field into a single data area. The area begins with a four-byte count of the number of data values in the area. The format of the values is determined by the second edit format, which must be specified immediately after the V. See [[#Using the V format|Using the V format]] for an example and a summary of restrictions.</td>
</tr>
<tr>
<td>X(<var class="term">n</var>)</td>
<td>Add <var class="term">n</var> blanks in the data area.</td>
</tr>
<tr>
<td>Z(<var class="term">precision</var>, <var class="term">scale</var>)</td>
<td>The value is returned in zoned-decimal form. The meaning of <var class="term">precision</var> and <var class="term">scale</var> is identical to that of the P format above except no padding is required for an even precision.</td>
</tr>
</table>

==Using a LIST specification for an updating call==
<p>
An edit specification parameter specifies a LIST format option for an IFUPDT, IFSTOR, or IFPUT call using the following syntax: </p>
<p class="syntax">LIST (<span class="term">field name list</span>);</p>
<p>
The fields and values in the field name list must be specified in the following format: </p>
<p class="syntax">'<span class="term">field value1</span>' '<span class="term">field value2</span>' ... '<span class="term">field value N</span>'; </p>
<p>where:</p>
<ul>
<li>Field values in the data area correspond to the names in the field name list. </li>
<li>Enclose the values in single quotation marks and separate them with blanks. </li>
<li>Two consecutive quotation marks in a field value causes a single quotation mark to be retained in the stored data. </li>
<li>Leading and trailing blanks within the enclosing quotation marks are retained. </li>
<li>A field value specified as &quot; (the null value) causes an existing field to be deleted or, if the field does not exist in the record, no action is taken. </li>
<li>You can use a %variable in the field name list in the LIST specification. The value for the %variable is specified in the %VARBUF and %VARSPEC parameters.</li>
</ul>

==Using a DATA specification for an updating call==
<p>
An edit specification parameter specifies a DATA format option for an IFUPDT, IFPUT, or IFSTOR call using the following syntax: </p>
<p class="syntax">DATA;</p>
<p>
The value of the fields named in the field name list must be specified in the following format: </p>
<p class="syntax"><span class="term">fieldname1</span>='<span class="term">fieldvalue1</span>' <span class="term">fieldname2</span>='<span class="term">fieldvalue2</span>' ...
<span class="term">fieldnameN</span>='<span class="term">fieldvalueN</span>'; </p>
<p>
where the following rules apply: </p>
<ul>
<li>Follow each field name with an equal sign (=) and enclose each new field value in single quotation marks.</li>
<li>Separate field name=value pairs with blanks. </li>
<li>Two consecutive single quotation marks in a field value are stored as a single quotation mark in the record. </li>
<li>The null value, <var class="term">fieldname</var>=&quot;, causes the specified field to be deleted from the record. Or, if the field did not previously exist in the record, no action is taken.</li>
<li>The DATA specification refers to the first occurrence of each field specified.</li>
</ul>

==Using an EDIT specification for an updating call==
<p>
An edit specification parameter specifies an EDIT format option for an IFUPDT, IFSTOR, or IFPUT call using the following syntax: </p>
<p class="syntax">EDIT (<span class="term">field name list</span>) (<span class="term">edit formats</span>);</p>
<p>
The format of the fields named in the field name list must be specified in the edit format. See [[#edit format codes|EDIT format codes used with an updating call]] for a list of the edit codes that are used in an EDIT specification for [[IFUPDT call|IFUPDT]], [[IFSTOR call|IFSTOR]], or [[IFPUT call|IFPUT]].</p>

===Guidelines for specifying an EDIT format===
<p>
When specifying an EDIT format for an IFUPDT, IFPUT, or IFSTOR updating call, the following guidelines apply: </p>
<ul>
<li>The value in the data area used with the EDIT specification does not require a final semicolon. </li>
<li>Each name in the field name list corresponds in sequence to an edit format. Extra edit formats are ignored. </li>
<li>If the list of edit formats is too short, Model 204 wraps around to the beginning of the list. </li>
<li>You can use a %variable in the field name list in the EDIT specification. The value for the %variable is specified in the %VARBUF and %VARSPEC parameters.</li>
</ul>

===Specifying significant digits using A, E, J, L, M, and U formats===
<p>
For numbers passed as parameters in A, E, J, L, M, or U specifications, Model 204 ignores significant digits past 15 and treats them as zeros, regardless of precision. </p>

===Specifying a length for the E format===
<p>
When you specify the E format for an updating function call, Model 204 ignores the significant digits and fractional digits parameters, but the total length specified must be accurate.</p>
<p>
If the updating function call receives a total length that does not convert to a floating-point number, Model 204 displays an error message indicating that data is inconsistent. The number is not stored and the HLI call that produced the message receives a return code of 4. </p>

===Using the G format===
<p>
The G (Generic) format allows you to perform complex updates to specific field values when an HLI program is executed. Through the use of a descriptor byte, you can use the G format to:</p>
<ul>
<li>Change the value of a field=value pair in a record</li>
<li>Delete a specific value of the field in a record</li>
<li>Bypass a specific occurrence of a field</li>
<li>Store a zero-length string value in a field</li>
<li>Select the data type at execution time rather than compile time</li>
</ul>
<p>
If you use the G format, Model 204 expects two items in the buffer for each field; the descriptor byte, and the new or updated field value (there are certain exceptions to this, as described below). The descriptor byte contains the following information: </p>
<ul>
<li>Bits 0 and 1 describe the format of the value to be stored or searched:
<table>
<tr class="head">
<th>Bit</th>
<th>Meaning</th>
</tr>
<tr>
<td>00</td>
<td>DELETE the field specified. If delete is used, Model 204 does not expect a value to follow in the data buffer. If there is another value in the buffer, Model 204 assumes that it belongs to the next edit format.</td>
</tr>
<tr>
<td>01</td>
<td>Update or insert this field as an 8-byte FLOAT value.</td>
</tr>
<tr>
<td>10</td>
<td>Update or insert this field as a counted STRING value. For a counted string value, the first byte contains the length of the string, followed by the string itself. You can insert a zero-length string into a field using this format.</td>
</tr>
<tr>
<td>11</td>
<td>Unused</td>
</tr>
</table></li>
<li>
Bits 2 to 5 are unused.</li>
<li>
Bit 6 indicates that you want to search for a specific value of a field to update or delete.
<p>When set, bit 6 indicates that the data buffer contains two values, a value to search for, and a value to store in its place. Each value must be preceded by a descriptor.</p>
<p>
If the descriptor bit for the second value in the buffer is set to '00' with no data following, the field occurrence is deleted.</p>
</li>
<li>
Bit 7 is the bypass field occurrence indicator. If this bit is set, Model 204 bypasses the specified field entirely.</li>
</ul>

====Exceptions to G format usage====
<p>
Although you can use the G format for all updating calls, there are some circumstances for which searching for specific values (using bit 6) or deleting field values (setting all bits to 0) are incompatible. You cannot use the G format to search by value or delete values for the following types of fields:</p>
<ul>
<li>Sort key field</li>
<li>Hash key field</li>
<li>%variable (%VARBUF and %VARSPEC parameters)</li>
<li>When adding fields using the field value(*) format</li>
</ul>

====Changing a specific value====
<p>
For example, if Joan Darcy is transferred from Portland, OR to Pittsburgh, PA, you can use the G format to change the address in her employment record as follows:</p>
<p class="code"><nowiki>EDIT(G)(G)

'10000010''8PORTLAND''10000000''APITTSBURGH' 
'10000010''2OR''10000000''2PA'</nowiki></p>
<p>
If you change the value of the field to a zero-length string, that value is stored in the field.</p>

====Deleting a specific value====
<p>
If, for example, Hadrian Wall is finally old enough to have his own automobile insurance and can be deleted from his parents' insurance policy, you can delete his field as follows:</p>
<p class="code"><nowiki>EDIT (G)

'10000010''7HADRIAN'' B'00000000'</nowiki></p>
<p class="note"><b>Note:</b> In this case, the first two bits are 0, which indicates a DELETE, the remaining bits are also 0, and there is no second data value in the buffer.</p>

====Bypassing a field occurrence====
<p>
For example, to bypass the third field in the found set of records, use the G format as follows:</p>
<p class="code">EDIT (A)(F)(G)(F)

.
.
.
'00000001'</p>

====Selecting the data type====
<p>
To select the data type at execution time, use just the first two bits in the G format. For example, to select only string data:</p>
<p class="code">EDIT(G)

'10000000'</p>

===Specifying the U format with floating-point values===
<p>
If you specify the U format with floating-point values, Model 204 interprets the values as nonnumeric strings and stores them as such in Table B. </p>
<p>
You cannot access these values as numbers in SOUL; however, retrieval through U EDIT specifications works normally. </p>

===Specifying V and M formats===
<p>
The V format processes field occurrences in the same manner as the M format. </p>
<p>
If the field name corresponding to the format in the field name list is specified as <var class="term">fieldname</var>(<var class="term">n</var>), <var class="term">n</var> indicates the position of the first occurrence to be changed. If <var class="term">n</var> is represented by an asterisk (*), all of the values are added as new field occurrences.</p>
<p class="note"><b>Note:</b> The VL format is equivalent to the M format, except that the data values are preceded by a four-byte count rather than by a one-byte count.</p>

===Updating a FLOAT field using A, J, L, M, or U formats===
<p>
When the updated field is defined as FLOAT, Model 204 converts exponential format numbers to floating point using A, J, L, M, or U formats.</p>
<p>
When the field is not FLOAT, Model 204 leaves exponential format numbers in their original character form. </p>

==Using EDIT format codes for an updating call==
<p>
The following table describes the edit format codes that can be specified in the edit format with the EDIT option in an IFUPDT, IFSTOR, or IFPUT (updating) call.</p>
<div id="edit format codes"></div>
<table>
<caption>EDIT format codes used with an updating call</caption>
<tr class="head">
<th>Code</th>
<th>Description</th>
</tr>
<tr>
<td>A(<var class="term">n</var>) and J(<var class="term">n</var>)</td>
<td>The field value in the data area is <var class="term">n</var> characters long. It is stored with leading and trailing blanks removed. If the final length is 0 after removal of the blanks, the existing field is deleted or is not stored for a new field.</td>
</tr>
<tr>
<td nowrap>B(<var class="term">precision</var>,<var class="term">scale</var>)</td>
<td>The value is in two's complement binary form and is converted to a character string before being stored. <var class="term">precision</var> specifies the number of bits in the numeric value, exclusive of the sign bit. Only two precisions are supported: 15 (halfword) and 31 (fullword). If both <var class="term">precision</var> and <var class="term">scale</var> are omitted, the precision defaults to 15.
<p>
<var class="term">scale</var> specifies the number of digits to the right of an implied binary point. The scale must not exceed the precision. If <var class="term">scale</var> is omitted, it defaults to 0, indicating an integer value. If the scale is more than 12, only the high-order 12 fractional bits are converted. Leading integer zeros and trailing fractional zeros are removed from the converted string. An all-zero string is stored as a single zero.</p></td>
</tr>
<tr>
<td>COL(<var class="term">n</var>) or <br />
COLUMN(<var class="term">n</var>) or <br />
POS(<var class="term">n</var>)
</td>
<td>Skip to character position <var class="term">n</var> of the data area.</td>
</tr>
<tr>
<td>E(<var class="term">total length</var>,<br /><var class="term">significant digits</var>,<br /><var class="term">fractional digits</var>)
</td>
<td>The value is in exponential format and is converted to the appropriate numeric format before being stored. The significant digits and fractional digits specifications are ignored by IFPUT. They are listed so that an application's IFPUT and IFGET edit formats can be shared.</td>
</tr>
<tr>
<td>F(<var class="term">n</var>)</td>
<td>The value is in floating-point form. The F specification must be used with FLOAT fields to make floating-point values accessible as meaningful numbers to Model 204.
<ul>
<li>If <var class="term">n</var> is 16, the value is extended precision (occupies 16 bytes and holds up to 31 significant digits).</li>
<li>If <var class="term">n</var> is 8, the value is long precision (occupies 8 bytes and holds up to 15 significant digits).</li>
<li>If <var class="term">n</var> is 4, the value is short precision (occupies 4 bytes and holds up to 6 significant digits).</li>
</ul>
Values to be stored in FLOAT fields whose lengths differ from the length defined for the FLOAT field are truncated or rounded to the defined length without a cancellation of the call.</td>
</tr>
<tr>
<td>G</td>
<td>Allows you to:
<ul>
<li>Select the data type at execution time</li>
<li>Bypass an occurrence of a specific field at execution time</li>
<li>Change or delete specific field=value pairs</li>
</ul>
The G format requires that the data is preceded by a descriptor byte. The G format is described in detail in [[#Using the G format|Using the G format]].
</td>
</tr>
<tr>
<td>L</td>
<td>The first byte of the data is a hexadecimal number that represents the length of the data bytes that follow. The value is stored without the length byte. Leading binary zeros are eliminated; leading and trailing blanks are not eliminated. If the final length is 0, the field is deleted; if the field is new, it is not stored. 
<p>For example, X'03C1C2C3' is equivalent to 'ABC'; X'04C1C2C340' includes the trailing blank in the stored value.</p></td>
</tr>
<tr>
<td>L(<var class="term">n</var>)</td>
<td>The value is <var class="term">n</var> characters long. Leading binary zeros (X'00') are eliminated; leading and trailing blanks are not eliminated. If the final length is 0, the existing field is deleted. If the field is new, it is not stored.</td>
</tr>
<tr>
<td>M(<var class="term">n</var>)</td>
<td>The first data byte contains the number of value occurrences. The values that follow are each <var class="term">n</var> characters long. Leading binary zeros are eliminated.</td>
</tr>
<tr>
<td nowrap>P(<var class="term">precision</var>,<var class="term">scale</var>)</td>
<td>The value is in packed-decimal form and is converted to a character string before being stored. <var class="term">precision</var> specifies the number of digits (not bytes) in the numeric value, exclusive of the sign. The maximum precision for a packed-decimal field is 15. If both <var class="term">precision</var> and <var class="term">scale</var> are omitted, <var class="term">precision</var> defaults to 5.

<var class="term">scale</var> specifies the number of digits to the right of an implied decimal point. The scale must not exceed the precision. If <var class="term">scale</var> is omitted, it defaults to 0, indicating an integer value.
<p>
Leading integer zeros and trailing fractional zeros are removed from the converted string. An all-zero string is stored as a single zero. No input validation is done, allowing nonnumeric values to be stored.</p>
</td>
</tr>
<tr>
<td>U(<var class="term">n</var>)</td>
<td>The field value in the data area is <var class="term">n</var> characters long (<var class="term">n</var> is less than 255). It is not stripped when it is stored. This format cannot be used to delete an old occurrence of a field.</td>
</tr>
<tr>
<td>V</td>
<td>Collect all occurrences of a field into a single data area. The area begins with a four-byte count of the number of data values in the area. The format of the values is determined by the second edit format, which must be specified immediately after the V. An example and a summary of restrictions is included below.</td>
</tr>
<tr>
<td>X</td>
<td>Same as X(1). See X(<var class="term">n</var>).</td>
</tr>
<tr>
<td>X(<var class="term">n</var>)</td>
<td>Skip <var class="term">n</var> characters in the data area.</td>
</tr>
<tr>
<td nowrap>Z(<var class="term">precision</var>,<var class="term">scale</var>)</td>
<td>The value is in zoned-decimal form. Precision, scale, and conversion rules are identical to the P format.</td>
</tr>
</table>