Re: Physical File "G" fields - Hope I have the correct list

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

G (or Graphic) fields are used to store DBCS or Unicode data. To determine
which is being used in your case you need to know the CCSID of the data. A
CCSID of 13488 or 1200 indicates Unicode.

Assuming it's Unicode data, COBOL (starting around V5R1) provides support
for this with NATIONAL support. You don't say what type of error you're
encounering when trying to read a record containing NATIONAL data, but it's
supported quite well by the COBOL language. My first thought is that the
programs file definition does not match the database file definition -- but
that's just a wild guess.

I would suggest looking at the NATIONAL support, which is documented in the
COBOL Reference and in the COBOL Programmer's Guide.

Bruce Vining

On Mon, Apr 2, 2012 at 12:36 PM, thomas burrows <
thomas.burrows.1957@xxxxxxxxx> wrote:

> If I have the wrong list please forgive and push to correct one.
>
> When using the Client Access Express Data Transfer Excel add-in I can
> automatically create a physical file on the iSeries. However, most of
> the fields show are created show a "G" data type format.
>
> Questions:
> 1. How does one read such a field. My COBOL program is erroring out.
> 2. When creating the iSeries PF I have attempted to make Character
> fields that are the correct length. Then run a dummy download from the
> iSeries to the PC creating me a FDF file. That FDF file does not work
> when I try to upload from the EXCEL spreadsheet using the Express Data
> Transfer Excel Add-in.
>
> Not sure what I am missing.
>
> Thomas
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.