COBOL DB2 Compiler options



IBM's flagship relational database management system

Re: COBOL DB2 Compiler options

Postby NicC » Thu Apr 24, 2014 11:35 pm

If by SE you mean the line command in SDSF then use SET HEX ON to display the output in hex - and put the field boundaries (><) into your DISPLAY statement so that you can see the full extent of the value.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: Re: COBOL DB2 Compiler options

 

Re: COBOL DB2 Compiler options

Postby dick scherrer » Fri Apr 25, 2014 12:30 am

Hello,

I suspect this depends on local definitions. . .
Neither of those hex values shows anything "printable" on my system . . .
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: COBOL DB2 Compiler options

Postby Terry Heinze » Fri Apr 25, 2014 1:54 am

ß is not printable in Reflection either but ALT+225 (using the numeric keypad will display it in Word or Notepad or here. I'm looking at the Extended ASCII Chart.
.... Terry
Terry Heinze
 
Posts: 193
Joined: Wed Dec 04, 2013 11:08 pm
Location: Richfield, MN, USA
Has thanked: 10 times
Been thanked: 11 times

Re: COBOL DB2 Compiler options

Postby SMRAO123 » Fri Apr 25, 2014 7:32 am

the problem is the - while going the data in the cobol host variables to sql query ( insert/update) data is converting ( to EBCIDIC I think ). And in the same way while retrieving the data from sql query to host variables data is converting.

So for the above sql select query value Y is displayed ( in spool edit mode) as ß

DEC HEX EBCDIC ASCII
089 59 ß Y

I would like to know why the data is converting?
SMRAO123
 
Posts: 9
Joined: Thu Oct 28, 2010 12:00 pm
Has thanked: 0 time
Been thanked: 0 time

Re: COBOL DB2 Compiler options

Postby SMRAO123 » Fri Apr 25, 2014 11:35 am

Seems problem is with CCSID's. Any idea what values need to be used to avoid conversion?
SMRAO123
 
Posts: 9
Joined: Thu Oct 28, 2010 12:00 pm
Has thanked: 0 time
Been thanked: 0 time

Re: COBOL DB2 Compiler options

Postby NicC » Fri Apr 25, 2014 1:38 pm

Only your support can tell that as it is country specific and may even depend on company if processing for clients in other countries.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: COBOL DB2 Compiler options

Postby SMRAO123 » Fri Apr 25, 2014 6:52 pm

In my precompile, CCSID(500) was used, but in bind I can see 'ENCODING UNICODE(01208)'. I overrided CCSID in bind with - ENCODING#500# now data is populating during & retrieving in select statements correctly.

Thanks
SMRAO123
 
Posts: 9
Joined: Thu Oct 28, 2010 12:00 pm
Has thanked: 0 time
Been thanked: 0 time

Re: COBOL DB2 Compiler options

Postby seenaiah » Tue Jul 15, 2014 11:28 pm

Can somebody please explain what ill happend if there is no plan and package?
seenaiah
 
Posts: 2
Joined: Thu Jul 10, 2014 9:53 pm
Has thanked: 0 time
Been thanked: 0 time

Re: COBOL DB2 Compiler options

Postby seenaiah » Sat Oct 25, 2014 1:05 am

Hai,
[deleted as not relevant to the topic and answers could be found using the search facility]
seenaiah
 
Posts: 2
Joined: Thu Jul 10, 2014 9:53 pm
Has thanked: 0 time
Been thanked: 0 time

Re: COBOL DB2 Compiler options

Postby Terry Heinze » Sat Oct 25, 2014 2:50 am

Please start a new topic instead of adding onto an unrelated one.
.... Terry
Terry Heinze
 
Posts: 193
Joined: Wed Dec 04, 2013 11:08 pm
Location: Richfield, MN, USA
Has thanked: 10 times
Been thanked: 11 times

Previous

Return to DB2

 


  • Related topics
    Replies
    Views
    Last post