Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hi one and all ALL-IN-1 v2.4 or v3.0-1 Customer has found that when scheduling a Housekeeping procedure for example, TRM, that the time they enter can be wrongly converted. To reproduce on v3, SM MSY MHP C {cr} enter TRM as the procedure name. The date doesn't seem relevant, so enter any valid date and TAB to the Time field. If you then type in 2:00 {TAB} it will more than likely convert it to 02:00pm rather than am. However I have found that if on US SWC I set my working day as 00:00am to 05:00pm (rather than 08:00am to 05:00pm as it was before) that the date convert will work correctly. Strangely this problem seems easier to reproduce on v3.0 altho the customer is using v2.4. On v2.4 I have not been able to consistently reproduce but it does occur. The dependence on the working day setting sounds familiar but I cant find anything on it now..... Any input gratefully received cheers Alan Crooks UK CSC.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3126.1 | IOSG::MAURICE | Differently hirsute | Tue Aug 10 1993 20:25 | 10 | |
Hi, Having had a little play suggests that another factor is whether you are using the 12 or 24 hour clock. It seems to default to 2am with the 24 hour clock and 2pm with the 12 hour clock. I'm sure that it must have been designed that way ;^) Cheers Stuart | |||||
3126.2 | Hmmmm..... | WAYOUT::CROOKS | Tue Aug 10 1993 22:33 | 17 | |
Hi Stuart, thanks for the reply, hadn't thought about the type of clock. Needless to say I was totally convinced by your explanation that it was designed that way.....for about a second.....:-) But just to see how creative you can be, I'll have to point out that if you play a bit more you'll find that with a 12 hour clock and a start time of 8am; 1,2,3, 4 + 5am can never be scheduled but 6 + 7am can..... dont tell me the clock in IOSG doesn't have those times on it....:-) Looks like the 24 hour clock is the best workaround. cheers Alan. | |||||
3126.3 | it's a fix, not design | FROIS1::HOFMANN | Stefan Hofmann, LC Frankfurt, ISE | Wed Aug 11 1993 11:58 | 15 |
Stuart, this will be a disappointment for you, but it has NOT been designed that way. In fact it was designed to work the way Alan describes for both, 12 and 24 hour clock. Since this was wrong behaviour at least for the 24 hour clock, it was fixed in an earlier version (V2.3 I think). Since then, the 12 hour clock still has the old think-about-what-user-wants algorithm, while the 24 hours clock has the new take-exact-match mechanism. The personal working hours do not influence this behaviour, so the workaround can only be to select 24 hour mode. Stefan |