Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Problem with NDM between Mainframe to PC.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
Priti_S

New User


Joined: 18 Feb 2009
Posts: 8
Location: pune

PostPosted: Mon Apr 26, 2010 1:01 pm    Post subject: Problem with NDM between Mainframe to PC.
Reply with quote

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
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 26, 2010 1:17 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Priti_S

New User


Joined: 18 Feb 2009
Posts: 8
Location: pune

PostPosted: Mon Apr 26, 2010 1:21 pm    Post subject: Reply to: Problem with NDM between Mainframe to PC.
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 26, 2010 1:27 pm    Post subject:
Reply with quote

Hello,

As i first mentioned - use binary for the transfer and the file will be completely AS IS. . .
Back to top
View user's profile Send private message
Priti_S

New User


Joined: 18 Feb 2009
Posts: 8
Location: pune

PostPosted: Mon Apr 26, 2010 3:15 pm    Post subject: Reply to: Problem with NDM between Mainframe to PC.
Reply with quote

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
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Mon Apr 26, 2010 4:01 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Mon Apr 26, 2010 5:06 pm    Post subject:
Reply with quote

What special characters are added? How many are added to each record?
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Mon Apr 26, 2010 6:10 pm    Post subject: Reply to: Problem with NDM between Mainframe to PC.
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Mon Apr 26, 2010 11:57 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Craq Giegerich

Senior Member


Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA

PostPosted: Tue Apr 27, 2010 12:16 am    Post subject:
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Apr 27, 2010 12:51 am    Post subject: Reply to: Problem with NDM between Mainframe to PC.
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts SNMP trap from Mainframe bipinpeter Compuware & Other Tools 6 Wed Apr 26, 2017 3:05 pm
This topic is locked: you cannot edit posts or make replies. Mainframe Opening in Allianz India- T... Rajesh Gopinathan Mainframe Jobs 0 Wed Apr 19, 2017 11:33 am
No new posts Strings with double quotes having pro... raja Arumugam All Other Mainframe Topics 11 Thu Mar 30, 2017 10:34 am
No new posts FTP from Mainframe to Unix - with CRLF vasanthz All Other Mainframe Topics 7 Thu Mar 23, 2017 5:12 am
No new posts Want to pull the job log into a Mainf... Jishu Mukherjee Compuware & Other Tools 9 Tue Mar 21, 2017 4:48 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us