I've installed Enterprise addtion on a standalone machine to test NLS support. From Administrator, I first ADDED several more codepages and then rebootoed the machine. After that, I was able to add several codepages Under NLS / SERVER Maps. But the INSTALL button is dimmed for NLS / PARALLEL Maps (and Parallel locales). Can parallel not have multiple codepages?
I have a mix of English and French EBCDIC characters to process and these must go BACK to the same charcters on output as well. The codepages that match my needs most closely are EBCDIC 037 or IBM 047.
NLS, codepages and locales on Parallel jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I'm using a workaround :
1) use a utility on the mainframe (DFSORT, SYNCSORT or FILEAID) to UNPACK the packed and binary data to display numerics.
2) edit the file layout to match the data record with the unpacked numbers
3) transmit the datafile (FTP, Universal Command, IND$FILE) WITH translation to ASCII (with CR/LF) -- STDIN -MODE TEXT or -TRAILINGSPACES YES -- its easier to use codepages with transmit products, so here is where you specify the correct codepage, or use the product default.
4) Now datastage doesn't have to deal with translation OR packed/binary data. Best to use Sequential Stage to read the file (for PX, anyway), since CFF seems to use only 7-bit ASCII instead of 8-bit (UTF-8 ?).
1) use a utility on the mainframe (DFSORT, SYNCSORT or FILEAID) to UNPACK the packed and binary data to display numerics.
2) edit the file layout to match the data record with the unpacked numbers
3) transmit the datafile (FTP, Universal Command, IND$FILE) WITH translation to ASCII (with CR/LF) -- STDIN -MODE TEXT or -TRAILINGSPACES YES -- its easier to use codepages with transmit products, so here is where you specify the correct codepage, or use the product default.
4) Now datastage doesn't have to deal with translation OR packed/binary data. Best to use Sequential Stage to read the file (for PX, anyway), since CFF seems to use only 7-bit ASCII instead of 8-bit (UTF-8 ?).