Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Locating non ASCII HEX'es in an EBCDIC file & the positi

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
morpheus007

New User


Joined: 27 Dec 2005
Posts: 58

PostPosted: Mon Mar 19, 2007 11:44 am    Post subject: Locating non ASCII HEX'es in an EBCDIC file & the positi
Reply with quote

We have a requirement to export mainframe data to a windows based system.When the mainframe data is interpreted by the windows system then certain non display or non ASCII(I am assuming) values are causing failures in the insert statements.For example X'FD' is getting rejected.Since the data is large even if we remove one hex value we might miss another.Is there any way to write a cobol program that would scan the mainframe input and generate a list of all the Hex values which are non ASCII and might get rejected by their system and their positions in the data.We could then substitute these with windows legal values.

I am assuming the collating sequence for MF is EBCDIC while that for something like ORACLE is ASCII and hence we are having this problem.So what could be legal in the MF collating sequence is not for ORACLE.Kindly let me know if I am wrong in the assumption.
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 Mar 19, 2007 7:37 pm    Post subject:
Reply with quote

Hello,

"Every" hex value is an ASCII value. One problem is that the hex values on the mainframe do not have the same meaning on ASCII platforms.

In the ASCII world, values "below spaces" are where the ASCII control characters are defined (an ASCII space is an x'20' - values from x'00' to x'1F' are "below spaces". This is not so in the mainframe - mainframe does not use embedded control characters.

I would suggest that when the file is created on the mainframe, all values are converted to delimited text. There should be no binary, packed decimal, or other character that is just a "bit pattern" sent to the target platform. Dealing with these types of fields is much easier on the mainframe (unless you have 3rd part software that will handle this - the products i've seen do not yet do everyting needed).

How did the x'FD' get created on the mainframe?
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 -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Execute JCL step based on the content... sprikitik JCL & VSAM 2 Tue Oct 03, 2017 10:03 am
This topic is locked: you cannot edit posts or make replies. PS file data should be passed as symb... d_sarlie JCL & VSAM 15 Tue Oct 03, 2017 5:18 am
No new posts Garbage on output file Hervey Martinez SYNCSORT 4 Wed Sep 27, 2017 12:50 am
No new posts File Aid tool to compare numeric data balaji81_k Compuware & Other Tools 2 Tue Sep 26, 2017 3:35 am
No new posts Compare yesterday's date to the one o... migusd SYNCSORT 11 Fri Sep 22, 2017 11:35 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us