Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref

Author Message
sivasaras

New User

Joined: 29 Sep 2007
Posts: 90
Location: chenna/i-

 Posted: Tue Jan 06, 2015 9:33 pm    Post subject: Computing statement truncation Hi, I have a compute statement in my cobol code. A PIC X(02) MOVE 32 TO A. C PIC 9(2) COMPUTE C = 16 * A value is 512 but it is storing the value as 12 not 51. please help me how to store the first 2 numbers. Thanks

David Robinson

Active User

Joined: 21 Dec 2011
Posts: 184
Location: UK

 Posted: Tue Jan 06, 2015 9:54 pm    Post subject: So you just want the 51 to be stored, ignoring the 2 ???
Robert Sample

Global Moderator

Joined: 06 Jun 2008
Posts: 8417
Location: Dubuque, Iowa, USA

 Posted: Tue Jan 06, 2015 9:56 pm    Post subject: If the PIC clause is too small to hold the result, COBOL aligns to the decimal point (whether explicit or implicit). Your C variable has an implicit decimal point after the second digit, hence the 12 will be stored and the 5 dropped. The easiest way to capture the 51 would be to define C as PIC 9(03) and then REDEFINE a variable on C that is PIC X(02).
Terry Heinze

JCL Moderator

Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

 Posted: Tue Jan 06, 2015 10:42 pm    Post subject: It can be dangerous using a PIC X (alphanumeric) field in a calculation. I'd either redefine it as numeric, or better yet, define A as numeric. Also, read very carefully the section in the Programming Language Manual about the precision of intermediate results when using the COMPUTE statement. COBOL doesn't do what you might expect it to.
Bill Woodger

DFSORT Moderator

Joined: 09 Mar 2011
Posts: 7314

 Posted: Tue Jan 06, 2015 11:02 pm    Post subject: Reply to: Computing statement How did you use a PIC X(2) as a source field in a COMPUTE? Why would you expect 51 to be the answer? I'm not sure I know of any programming language which right-truncates results to fit in a field. For an answer, you can also truncate your result by dividing by 10. Not normally something I recommend, but since you are multiplying by 16 already, why don't you multiply instead by 1.6? Terry, It obviously took me 20 minutes to type that amongst other things. The PIC X definition for A will cause the compiler to upchuck and refuse to even attempt the COMPUTE. COMPUTE works exactly how it should work. The problem people have with COMPUTE is that they don't read the intermediate results section that you suggested. They tend to think of a computer as a big calculator, or something which uses numbers-of-unlimited-size-and-unlimited-decimal-places-even-though-it-can't-do-decimal-calculations-accurately-in-all-cases.
Rohit Umarjikar

Senior Member

Joined: 21 Sep 2010
Posts: 2105
Location: NY,USA

Posted: Thu Jan 08, 2015 3:42 am    Post subject:

 Quote: value is 512 but it is storing the value as 12 not 51

Red Alram--> Is it a bug or a requirement? if bug then simply increase the size of C otherwise use the above methods as suggested.
 All times are GMT + 6 Hours
 Page 1 of 1

Search our Forum:

 Topic Author Forum Replies Posted Similar Topics Create view statement from SYSIBM.SYS... andrea DB2 7 Thu Aug 02, 2018 9:30 pm Compute statement with Cobol Z/os 5.2 Chetan Kumar COBOL Programming 2 Fri May 11, 2018 8:02 pm COBOL - EXIT statement weird behavior anthony.pangestu COBOL Programming 0 Fri Oct 27, 2017 9:57 am WER268A OUTREC STATEMENT : SYNTAX E... frozenblood87 SYNCSORT 12 Sat Aug 26, 2017 9:45 pm Suppress value reported by BREAK in D... Learncoholic DFSORT/ICETOOL 3 Wed Aug 16, 2017 6:03 pm

 © 2003-2017 IBM MAINFRAME Software Support Division
 Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us