7.1 on both machines.
SF99701 41 on DEV
SF99701 38 on Prod.
I think I have it working
I changed it to UPDATE MYLIB/WTAVGS SET WTOSSHR = round(wtosshr * 1.5,0)
The field I'm updating is 9.0
I'm doing comparisons, but so far every thing is matching.
Thanks
Mike
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Monday, April 03, 2017 11:45 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: sql round conundrum
What Releases are you on? ROUND had always 2 parameters, the expressions and the number of decimal positions.
That you can specify only a single parameter was not introduced before one of the latest TRs.
An other reason could be that the decimal comma (like in Europe) instead of a decimal point is used within your job.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to." (Richard Branson)
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Montag, 3. April 2017 17:34
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx) <midrange-l@xxxxxxxxxxxx>
Subject: sql round conundrum
I have 2 machines both on 7.1, but dev machine is slightly ahead on PTFS.
I have run a SQL round statement
UPDATE MYLIB/WTAVGS SET WTOSSHR = round(wtosshr * 1.5)
It successfully updated 409 records.
However when I run this on my production machine, I get a message that Number of arguments for function ROUND not valid.
Short of getting the PTFs matching on the machines because I need to get this file updated today.
How might I modify the round to match the results from my dev box?
Thanks
Mike
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
As an Amazon Associate we earn from qualifying purchases.