Check the VFIELDSIZE

Before you increase the VFIELDSIZE, confirm that VFIELDSIZE is actually why a field is not displaying. This procedure runs a small test subroutine, TESTIDESC, against the field on a UniData system.

Find the FIELDNAME of the column that is not displaying in a Dataset or Report, and the FILENAME where that field resides.
Telnet to the database server and go to the target account.
Check whether TESTIDESC has already been added:
```
CT VOC TESTIDESC
```
If it has not, add it. If you have a standard file for custom subroutines, use that; otherwise the BP (Binary Programs) file is the usual default:
```
AE BP TESTIDESC
```
Type I for Insert.
Obtain the TESTIDESC subroutine code from Support and paste it into the TCL session. Copy and paste does not work through Java TCL, so use a standard TCL session.
Press ENTER to return to the editor prompt.
Save and compile:
```
FIB
```
Catalog it directly (replace BP with your binary-programs file if different):
```
CATALOG BP TESTIDESC DIRECT
```
Check the Datasource settings page for any initialization subroutines.
Sign in to the Informer web server and open a Java TCL session to the target database.
Run any initialization subroutines explicitly.
Run TESTIDESC on the field, replacing FILENAME and FIELDNAME:
```
TESTIDESC FILENAME FIELDNAME
```

Interpret the output:

Two rows of data, each the same (slightly misaligned): VFIELDSIZE is set correctly, so it is not the cause; the column is failing for another reason.
30 records selected but no output: the field is not compiled, or you did not run the required initialization subroutines. Go back to step 12 and run any missing ones; if it still fails, the field may need to be compiled.
An error: VFIELDSIZE is not set correctly. Increase the VFIELDSIZE.