|
View previous topic :: View next topic
|
| Author |
Message |
Priti_S
New User
Joined: 18 Feb 2009
Posts: 8
Location: pune
|
|
|
|
Hi,
I have to transmit a dataset from Mainframe to PC. This dataset has few varaibles which contain hex data. When i transmit the file to PC, the positions are shifted, as some special chars are added in between the data.
Is there any way i can have the file transmitted AS IT IS on mainframe? PLease help. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Use binary rather than text, but then you will have to manually convert the text values to ascii on the pc.
A better choice is to to change the mainframe data so there are no "hex values" and then transmit the file as test. |
|
| Back to top |
|
|
Priti_S
New User
Joined: 18 Feb 2009
Posts: 8
Location: pune
|
|
|
|
| I have to send the file to some user who expects the data AS IS. Is there any other possible way to resolve this issue? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
As i first mentioned - use binary for the transfer and the file will be completely AS IS. . . |
|
| Back to top |
|
|
Priti_S
New User
Joined: 18 Feb 2009
Posts: 8
Location: pune
|
|
|
|
This solution does not work. When I transmit the file, all junk values are coming in the file.
I have tried all possible methods...can you please suggest some method where i dont need to do any conversion. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Priti_S wrote: |
I have tried all possible methods...can you please suggest some method where i dont need to do any conversion.
|
| Dick Scherrer wrote: |
A better choice is to to change the mainframe data so there are no "hex values" and then transmit the file as test.
|
When AS IS won't work, then something needs to change. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| What special characters are added? How many are added to each record? |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
According to the Reference Guide for Connect:Direct processes for Windows, the following options are allowed for the SYSOPTS statement:
- datatype(text|binary)
text indicates it is a text file and that trailing blanks will be stripped unless you specify strip.blanks(no) . Translation of the data is performed unless you also specify xlate(no).
- strip.blanks(yes|no)
determines whether trailing blank characters at the end of each record are removed from a line of text before it is written to the Windows text file. yes removes trailing blank characters. no does not remove trailing blank characters. The default is no for Windows.
- strip.oneable(yes|no)
strips ^Z from the end of old DOS files. If this character is not stripped from old DOS files, Connect:Direct Windows translates ^Z into 3F when files are sent to the snode. yes removes ^Z from the end of old DOS files. no does not remove ^Z from the end of old DOS files. The default is no.
- xlate(no|yes)
indicates whether character translation should be performed using the
default or user-supplied translation table. Typically, this translation is between ASCII and EBCDIC. no specifies the translation should not be performed. The default for Windows is no. yes specifies the translation should be performed.
- xlate.tbl(pathname/filename)
specifies that a different translation table from the
default table used by Connect:Direct is used. pathname/filename should identify a translation table created using the translation table editor of the Connect:Direct Requester for Windows. The path specification is optional. If the path is not provided, the path specified by the xlate.dir initialization parameter is assumed for the filename specified. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| This solution does not work. When I transmit the file, all junk values are coming in the file. |
The solution works perfectly. The user simply does not want the data AS IS. . .
You have basically 2 choices - send the file AS IS and then deal with ebcdic data on the Win-box (not usually any fun). or send usable data (not AS IS).
I have only worked on a couple of migrations that the 3rd party software would handle "AS IS" mainframe data.
You and/or your user need to decide where you will address the conversion. My preference is to do the formatting work on the mainframe and download Office-compatible text data. |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| Are there any fields in the records that you are transmitting that contain packed decimal (COMP-3) or binary fields (COMP or COMP-5)? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Or fields that are pic x(n) but are a collecton of off/on bit settings. . .
Lots of this still around in older systems. . .
d |
|
| Back to top |
|
|
|
|
