Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

On 6 Feb 2016 17:30:16 -0800, in bit.listserv.ibm-main you wrote: >Posting this to replace a post I made, by accident only in the >google-something part of the list. Some editing, and additional examples. > >MOVE PICS9-9 TO PICS9-8 >D204 3010 3028 MVC 16(5,3),40(3) PICS9-8 PICS9-9

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

Just commenting on one thing: > It is again there for the case of an overflow which has resulted in a > negative zero > but I can't think why it is not preceded by a branch on condition for the > overflow > value in the Condition Code. Do I interpret what you are saying as "I get the need

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

> "That should be ZAP 3672(5,5),1971(1,5) or you will only get the first byte of the source field." I may be rusty, but surely the ZAP overlapping byte-for-byte with both operands 3672(5,5) will simply work as if processed from right to left, changing nothing apart from perhaps the sign, as

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

In <1322019919168634.wa.dalesmithcolumbus.rr@listserv.ua.edu>, on 12/31/2015 at 10:15 PM, "Dale R. Smith" said: >will sometimes use CLC to compare two Packed fields I hope that's only on tests for equality, not on high/low compares! -- Shmuel (Seymour

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

I wish this question had been stated with greater precision and accuracy, since the precision and accuracy of the answer directly depend on it. Too much guesswork. (1) What *exactly* were the COBOL field definitions and the MOVE statement?? The title just says "MOVE COMP-3 S9(9) to S9(8)". Does

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

On Sun, 13 Dec 2015 14:53:27 -0600, David Speake wrote: >A coworker posed the following question. > >Given a COBOL statement that moves a field defined as S9(9) comp-3 >to a field defined S9(8) comp-3, the generated assembler code looks like this: >

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8) BTW, is there a [E]SPIE in the COBOL/LE runtime environment? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

In <2082084024112365.wa.david.speakebcbssc@listserv.ua.edu>, on 12/13/2015 at 02:53 PM, David Speake said: >So why is IBM generating the ZAP instruction? To force the sign to a standard value? >The only use to this is to abend with S0C7 if the data is garbage.

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

At 17:39 -0400 on 12/13/2015, Clark Morris wrote about Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8): 01A598 D204 5E58 17B3 ZAP 3672(5,5),1971(1) 01A59E 940F 5E58 NI3672(5),X'0F' would be adequate. Clark Morris > That should be ZAP 3672(5,5),1971(

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

Another side effect of the ZAP is that the sign halfbyte will be X'C' or X'D' after the ZAP, no matter what it was before (CAFE or DB); that is, ZAP forces the sign halfbyte to the preferred values. I recall that there are some COBOL compiler options that deal with this. Kind regards Bernd

Re: COBOL Code Gened for MOVE COMP-3 S9(9) to S9(8)

On 13 Dec 2015 12:53:23 -0800, in bit.listserv.ibm-main you wrote: >A coworker posed the following question. > >Given a COBOL statement that moves a field defined as S9(9) comp-3 >to a field defined S9(8) comp-3, the generated assembler code looks like this: > > 01A598