|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Yup I did not see that, it is reversed! Well consider what I am surrounded by. 8-) -----Original Message----- From: Al Karman [mailto:Alk@ladyremingtonjewelry.com] Sent: Tuesday, December 17, 2002 11:44 AM To: midrange-l@midrange.com Subject: RE: EBCDIC ==> ASCII Howard, I think your subject is reversed.... If the HP you speak of is in fact the venerable 3000, using the :FCOPY function, you'd want ;EBCDICOUT to force output to be EBCDIC. Al Karman Director of Information Technology Lady Remington Jewelry alk@ladyremingtonjewelry.com 630.860.3323 -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com] On Behalf Of Weatherly, Howard (Contractor) (DLIS) Sent: Tuesday, December 17, 2002 9:39 AM To: Midrange Mailing List (E-mail) Subject: EBCDIC ==> ASCII This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Folks, I have a situation where I may need to take ASCII data from an HP and update mainframe data. I believe I know how I need to do this but for piece of mind I want to run it buy the experts. If I declare the host variables where I will stage the data (Select Into from HP) as CCSID 37 will the data in fact be converted by DB2 from ASCII to EBCDIC ? Is there a better way to accomplish this i.e.. a function? ____________________________________________ Howard Weatherly Systems Advisor Computer Task Group, Inc. howard.weatherly@dlis.dla.mil Howard_weatherly@ameritch.net Howard.Weatherly@ctg.com "luck favors those who prepare" _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.