Sorry for the delay in responding, but 2 IT looking after 400+ users on migration to jbase 5 is challenging.
I understand your 'cataloging on a live system' and smiled at your pedantic comment, but:- We have just installed a new Sun server, everything on it is hot swappable except the cpu's, we do not have to log off or shutdown to change disks, fans, power supplies etc, but we do have to get users to log off to see when we add a new column to a report subroutine? is that going forward or backward? We chose Solaris and jbase because we did not want to have to kick everyone off the system when we made a small change unlike our Windows servers after updates, or our IBM servers with SQL (soon to be disposed of in favour of jbase) We have a number of processes which run 24/7 now we must stop and restart these at least once a day, just to be safe, reduced efficiency greater productivity? I really don't think so. If I remember correctly McDonnell Douglas had a Clear Shared Memory option, does not jbase have the same? Putting aside users, is the log off/on a smart idea when in development? given the number of permutations a main line and subroutine may have testing every single one is not always possible, especially when dealing with 'less critical' programs such as reports. If the concept of holding subroutines in memory for speed is the benefit, why not hold the main lines? Not a good move, Jim, and as a 20 year user of the 'Pick' system who has not considered a move away from jbase since coming from universe many years ago, I am saddened to see that this arbitrary change has been introduced without consideration of the users, sorry, customers. On Oct 16, 7:08 am, "Jim Idle" <[email protected]> wrote: > See many past posts: jbase.markmail.org > > It is because you are using jSHELL in an ordinary prompting mode so the > EXECUTE the jSHELL does is optimized and pre-caches the subroutines, which > is generally what you want. When testing, use the shell in UNIX mode, which > will spark a new process and that will reload your new version. I usually > write a shell script or .bat file in fact so that I don't need to worry > about it. > > Similarly, if you do not wish to create a proper release mechanism for your > application, and feel that cataloging directly into a live system is a good > idea, then the way to do this is to have the program exit and restart itself > at strategic points, such as every 20th return to the main menu etc. > However, cataloging in to a live system is not a good idea, it just means > you have not thought it through properly. > > Also, I think you meant "Is there a way to avoid this", rather than the > negative grammatical phrasing =;p but that is a little pedantic :-) > > Jim > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf > > Of Ken Brown > > Sent: Wednesday, October 13, 2010 4:47 PM > > To: jBASE > > Subject: jBase 5.25 with Solaris 10 > > > In the process of implementing this but becoming very frustrated when > > modifying a subroutine and having to log off and back in to test. > > > Is there no way of avoiding this? > > > -- > > Please read the posting guidelines at: > >http://groups.google.com/group/jBASE/web/Posting%20Guidelines > > > IMPORTANT: Type T24: at the start of the subject line for questions > > specific to Globus/T24 > > > To post, send email to [email protected] To unsubscribe, send > > email to [email protected] > > For more options, visit this group at > >http://groups.google.com/group/jBASE?hl=en -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
