Those are Unicode fields. The options that Jerry is referring to is when
the list of fields from the "Scan worksheet" you can double-click on them
and change it to "Character" instead of Unicode...OR when you get to the
"Customize Data Transfer" screen click on "Properties" then the "Scan
data" tab change the "Default character data type" to CHARACTER and then
you'll never have to worry about it again.



From: thomas burrows <thomas.burrows.1957@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 04/02/2012 01:00 PM
Subject: More Information on G type fields in PF
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Here is some screen shots. Excuse the data but I have to overwrite
original data per security issues.

This is my file that was created by the Excel function looking at it using
DBU.

F1 C F2 4XXXX XXXXXXXXXXX
F3 113251931 F4 40787 F5
F6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

F7 XXXXXXXXXXXXXXXXXXXXX

F8 XXXXXXXXXXXXXXXXXX

F9 XXXXXXXXXXXXXXXXXXXXXXX
F10 XXXXXXXXXXXXXXXX
F11 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX F12 XXX
F13 11111 F14 XXXXXXXXXXX
F15 111-111-1111 F16 11111111

Field names are F1 to actually F19

Doing an F9 DBU function to change to HEX.


F1 C F2 4XXXX XXXXXXXXXXX
C FEEEE4EEEEEEEEEEE
3 47777077777777777
F3 113251931 F4 40787 F5
FFFFFFFFF FFFFF FFFFF
113251931 40787 00000
F6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE4444444444444444444444444444
77777777777777777777777777777777777770000000000000000000000000000
F6
4444444
0000000


Then my F4 field definitions.

Display New New Auto Upper Allow Field
Seq# Select Only Line Page Dup Case Null Name Type Length Dec
Loc
10 F1 F1 G 2 1
20 F2 F2 G 34 3
30 F3 F3 S 9 0
37
40 F4 F4 S 5 0
46
50 F5 F5 S 5 0
51
60 F6 F6 G 144 56
70 F7 F7 G 262 200
80 F8 F8 G 138 462
90 F9 F9 G 94 600
100 F10 F10 G 100 694
110 F11 F11 G
64 794
120 F12 F12 G 12 858
130 F13 F13 S 5 0
870
140 F14 F14 G 56 875
150 F15 F15 G 24 931
160 F16 F16 S 8 0
955
170 F17 F17 G 40 963
180 F18 F18 G 68 1003

Doing a DSPFFD on the file here is what I get

Data Field Buffer Buffer Field Column
Field Type Length Length Position Usage Heading
F1 GRAPHIC 1 2 1 Both F1
Coded Character Set Identifier . . . . . : 13488
UCS2 or Unicode conversion . . . . . . . : *CONVERT
F2 GRAPHIC 17 34 3 Both F2
Coded Character Set Identifier . . . . . : 13488
UCS2 or Unicode conversion . . . . . . . : *CONVERT
F3 ZONED 9 0 9 37 Both F3
F4 ZONED 5 0 5 46 Both F4
F5 ZONED 5 0 5 51 Both F5
F6 GRAPHIC 72 144 56 Both F6
Coded Character Set Identifier . . . . . : 13488
UCS2 or Unicode conversion . . . . . . . : *CONVERT
F7 GRAPHIC 131 262 200 Both F7
Coded Character Set Identifier . . . . . : 13488
UCS2 or Unicode conversion . . . . . . . : *CONVERT
F8 GRAPHIC 69 138 462 Both F8
Coded Character Set Identifier . . . . . : 13488


DBU can read this file. Edit it, etc. Have a tech request into DBU to
what secret they are using.

I am just not that knowledgable about the "Coded Character Set
Identifier" stuff.

Thomas

On 4/2/12, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
I think you're on the right list.

Methinks it's some sort of CCSID issue. For instance, on a DSPFFD I may
see:
Data Field Buffer Buffer Field Column
Field Type Length Length Position Usage Heading
IID CHAR 2 2 1 Both Rec
ID
IM/IZ
Field text . . . . . . . . . . . . . . . : Record ID (IM/IZ)
Coded Character Set Identifier . . . . . : 37
IPROD Open 35 35 3 Both Item
Number
Field text . . . . . . . . . . . . . . . : Item Number
Coded Character Set Identifier . . . . . : 937
IDESC Open 50 50 38 Both Item
Description
Field text . . . . . . . . . . . . . . . : Item Description
Coded Character Set Identifier . . . . . : 937

Here, I think "Open" would be your type "G", as in graphical. Notice
how
they are CCSID 937 where the CHAR field is 37?

I wonder if there is a setting in Excel or the data transfer option to
handle the CCSID.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: thomas burrows <thomas.burrows.1957@xxxxxxxxx>
To: MIDRANGE-L@xxxxxxxxxxxx,
Date: 04/02/2012 01:36 PM
Subject: Physical File "G" fields - Hope I have the correct list
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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.


--
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.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].