Data Dictionary - Work Fields

Item 5.1

Bug (flagged in V05): In APPX 1.8.4 (thru APPX 3.0.0), if a field with Read Security is defined on an output or inquiry image and a DISPLAY command is given on that field, a user without the required security rights will get APPX system error RMUPD.C.156 ("upd_chr - characteristic doesn't fit on image"). In APPX 3.0.0, if the DISPLAY command is removed, the function works properly. This bug does not affect inputs nor does it affect users with the required security. (See items 4.7 & 10.1).

Item 5.2

Bug (FYI): For work fields with Field Type DOMAIN referencing domains with Type ALPHA, Share Class is non-modifiable under APPX 2.x. Since share class is not accessible on the domain, this means Share Class cannot be changed for such fields. This is inconsistent since Share Class is modifiable if the domain referenced has Type NUMERIC. (Share Class is modifiable at the field level for all domain types in APPX 1.8.4.)

Item 5.3

Bug: The Format column may not properly show Tbl even though a Validation Table exists for fields with Field Type FORMAT (and possibly Type ALPHA). Note that the pg printout of file TOKEN in Portdata lists all fields that should have validation tables. Nothing works to force the display of 'Tbl' but it does not seem to cause a problem.

Conversion Bug (fixed in Version 04): Version 02 of the conversion utility can create TOKEN records with token type '1' in the first byte. Token type must be '0' for validation tables converted from SP2 to work properly.

Item 5.4

Difference (flagged in V05): SP2 allows 79 characters for Default Value and Edit Mask whereas APPX only allows 60 characters. In the case of Edit Mask, this is a critical difference since Edit Mask is used to size the field and must match SP2. Address problem fields (see item 2.16).

Item 5.5

Note (FYI): Be sure to exit and reenter APPX after making any changes that involve Tbl formats (such as validation tables and TOKEN fields); otherwise, the changes will not take effect.

Item 5.6

Bug (fixed in V05): If Conversion Utility 2.00 Version 04 dated 11/10/94 is used to convert to APPX 2.x and higher (at least thru APPX 3.0 Beta), field descriptions, column headings, and default values will be lost for non-domain fields. To avoid this problem, you must use vi (before running convert.sh and before importing) to delete records in file DOMAIN in Portdata that have Generated? flag "Y" in the first byte. Since the Generated flag is part of the key, all records for real domains (with Generated? "N") appear first. You can precede the dd command in vi with the number of lines (records) to delete.

Item 5.7

Action: Check APPX for format missing in Format column and determine cause if not legitimate. The APPX Software, Inc. UTL utilities "APPX DOMAIN File List" and "APPX FIELD File List" provide a warning whenever format is missing in error. (See item 3.5.)

Item 5.8

Bug (FYI): APPX 3.0.0 appears to stop processing work fields after it finds the first error. It only reports the first error found.

Item 5.9

Conversion Bug: The conversion utility does not flag a work field defined as 'Same As' a field in a non-existent file in the same application. APPX gets a "Domain Not Found" error when processing work fields in the data dictionary. The easiest solution is to delete the work field if it has no references on the SP2 X-Ref. (See item 5.8.)

Item 5.10

Conversion Bug (fixed in V05): SP2 fields defined as 'Same As' with 'Copy Doc?'="Y" are converted with 'Use Domain Doc?'="N". It should be "Y". This condition is not practical to correct. (See item 4.23.)

Item 5.11

Bug?/Difference (Pete to fix in 3.1?)(flagged in V05): In SP2 a text work field can have a default value. In APPX 3.0.0, default value cannot be accessed or viewed for a text work field. To view the default value (also called 'Init') which will be used at runtime, run the APPX Software, Inc. UTL CS utility "APPX ELEMENT File Detail List" and enter the field name as the element name. If needed, add code to set these values in Start of Process for any APPX processes referencing these fields. (See item 4.4.)

Item 5.12

Difference: Since APPX may display question marks for unsigned numeric fields with negative values where SP2 would show the negative value, you may want to investigate any critical unsigned numeric field with the potential to go negative. The best way to find such fields is to look at the field format column in the APPX Data Dictionary for formats starting with "9(" or to search APPX File Tech Doc on the screen for "m 9(" (to allow for numeric fields based on domains). Mark these fields on the SP2 File Tech Doc and address as needed. (See items 2.11, 4.24, 9.30, & 10.19.)

However, it is probably not practical to address the question marks since this is supposed to be corrected in a future release of APPX.

Item 5.13

Difference (flagged in V05): Since "PF" terminology is not applicable in APPX, modify "PF" text as appropriate. (See item 2.14.)

Item 5.14

Difference/Conversion Bug (flagged in V05): SP2 allows invalid characters in the Input Mask and APPX does not. (See item 3.8.)