Don't know exactly, what is the problem
I've just tested the following program.
It works.
Why not to make a good old type cast between two different numeric types?
Of course :-) I use v4R5.
I feel, that the guys from IBM made C-compiler free and mostly unusable at the 
same time with 5.1....

int main(int argc, char *argv[])
{
  int a ;
  decimal (5,0) b ;

  a = -1 ;
  b = (decimal (5,0)) a ;
  printf ("a = %d ; b = %D(5,0)\n", a, b) ;
  return(1) ;
}

> -----Original Message-----
> From: Peter.Daransky@ambos.at [mailto:Peter.Daransky@ambos.at]
> Sent: 13. detsember 2002. A. 19:27
> To: c400-l@midrange.com
> Subject: RE: [C400-L] Decimal Problem
>
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> i'm trying to use QRCVDTAQ and this API need decimal(5,0) also
>
> int wait = -1;
> decimal(5,0) dec5 = wait;
>
> QRCVDTAQ(... ,  ... , wait);
>
> and here is my problem, cause compiled for V4R5 no problem but if'll
> compile it for V5R1 is it falling down ?!
>
> Regards
>
> Peter Daransky
> AMBOS EDV-Beratungs GesmbH
> Dauphinestr. 44
> A-4020 LINZ               Austria
> Tel:         +43-732-312919-0
> Fax:        +43-732-312919-20
> e-mail:  Peter.Daransky@ambos.at
> Homepage: http://www.ambos.at
> _______________________________________________
> This is the C programming iSeries / AS400 (C400-L) mailing list
> To post a message email: C400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/c400-l
> or email: C400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/c400-l.
>
>



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].