Re: Converting minutes to hours/minutes

[rob@xxxxxxxxx]

And that's as high as you can simply go.  Because months and years vary. 
At that point I say use the select statement I previously presented using 
real date functions.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Booth Martin" <booth@xxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
01/31/2005 04:51 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Converting minutes to hours/minutes






If one wanted to, one could divide first by 7x24X60, then divide the
remainder by 24x60, then divide the remainder by 24, giving weeks, days, 
and
hours. 

 

---------------------------------

Booth Martin

http://www.martinvt.com

---------------------------------

-------Original Message-------

 

From: RPG programming on the AS400 / iSeries

Date: 01/31/05 15:43:30

To: RPG programming on the AS400 / iSeries

Subject: Re: Converting minutes to hours/minutes

 

 

> I like my solution better.  What happens if the duration exceeds an 
hour?

 

If the duration exceeds an hour?  HUH?  Why would it matter if the

duration exceeded an hour?  The whole point of dividing by 60 was to get

the number of hours.

 

The problem with your solution is that a time data type is designed to

hold the time of day, NOT a duration.

 

If you had a duration of 14 hours and 20 minutes, and you stored it in a

TIME operation, then displayed it with *USA format, it would show as 2:20

PM instead of 14 hours.  (Of course, you can easily avoid this by

hard-coding the time format)

 

However, if your "number of hours" field exceeds 24 hours, kaboom, your

program will blow up.  A time field cannot store a value higher than

23:59:59 because, again, it's designed to represent a time of day, not a

duration.  (Of course, if you know ahead of time that it'll never be that

high, you could still use your method.)

 

If you switch it to use a timestamp instead of a time field, you'd

eliminate the 24 hour problem, but then it would show a year value that

would inevitably be wrong.  Plus it would do odd things like handle leap

years and other things that you don't want when you're expressing a

duration rather than a specific point in time.

 

My solution would never have these problems.

 

For example, our company makes sausage.  When fresh (uncooked) sausage

comes out of the department where it's stuffed and packaged, it needs to

go into a blast freezer to freeze it solid.  It has to remain in that

blast freezer for around 100 hours.

 

So, I have a database record that contains the time that the product went

into the freezer.  They have a screen to view, at any given moment, how

long the sausage has been in the freezer.

 

If I used your solution, it would never work.  I'd either have to show

them a duration under 24 hours, or I'd have to show them

0001-01-03-00:05:06.000000 (or something like that) which really wouldn't

help them determine how long the product had been in there.

 

Using my solution, I can do this:

 

      C     CurrentTime   subdur    TimePutIn     mins:*mn

      C                   eval      hoursin  = %div(mins: 60)

      C                   eval      minsin   = %rem(mins: 60)

      C                   eval      duration = %editc(hoursin:'Z') + ':'

                                             + %editc(minsin:'X')

 

Assuming that 'hoursin' is at least 3,0, I have no problem showing 100

hours or more on the screen.  When they see it on the screen, it shows

something like ' 99:45' and they say "cool, I can take that one out in 15

minutes".

 

I've used solutions like yours in the past.  I've even posted them here as

suggestions. But whenever I've done something like that in a production

program, it always came back to bite me.  There's always some obscure

"exception to the rule" where they had more than 24 hours on something,

and the program crashes with a date/time/timestamp error.

 

And the user has NO CLUE whats going on when that happens. No matter what

you say, he just can't understand why the program didn't work.

 

And, all that to save me, what? Two lines of code?  maybe 45 seconds of

typing?

 

--

This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list

To post a message email: RPG400-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/rpg400-l

or email: RPG400-L-request@xxxxxxxxxxxx

Before posting, please take a moment to review the archives

at http://archive.midrange.com/rpg400-l.

 

 

.
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.