|
Actually I we use several environments. We used the blank only in our infancy. Now we always use a selected environment LIVE, TST, DEV, PTF -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Lemon, Mike Sent: Tuesday, February 15, 2005 11:03 AM To: 'System 21 Users' Subject: RE: [SYSTEM21] The "standard" environment Fred, It sounds like you advocate using the blank environment, but with care. I don't agree with that approach and here is why: What if you have modified library lists to add a MOD library or because you needed to do some library consolidation? Or modified a task to run in another jobq? Or changed a menu to add an option for a custom report? That *could* get wiped out too, and we ALL have done that. I don't touch blank at all. I recommend that you do the same. It is the easiest and safest approach. Also, if you leave blank alone, you will always be able to see how the baseline version of System/21 works compared to your modified version. -Mike -----Original Message----- From: Santos, Fred [mailto:Fred.Santos@xxxxxxxxxxxxxxx] Sent: Tuesday, February 15, 2005 10:51 AM To: System 21 Users Subject: RE: [SYSTEM21] The "standard" environment All, we have been using S/21 since 1996. I've always know that you can use the Tasks in the 9000 range for your use. You would need to use a standard Library List for the selected application. But you are asking for trouble is you use any task less than 9000. it "could" get wiped out by a PTF. -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Rose Clarke Sent: Tuesday, February 15, 2005 9:31 AM To: System 21 Users Subject: RE: [SYSTEM21] The "standard" environment Chris, I would have to agree with everything you say. I too have always been insistent that std environment should be left completely vanilla and any changes added to our own environment. This means that when ptf's/upgrades are done there is a clear and easy way to reconcile the two and see where changes have been made. I would be very suprised if anyone can definitely say that they have adequate/easy to access documentation that could replace that. What do Geac say are the benefits of moving away from this sort of setup? User profiles are the only one I can think of and that isn't exactly a great time saving. I will be very interested to hear what other people think about this. ________________________________ From: system21-bounces@xxxxxxxxxxxx on behalf of Chris Tringham Sent: Tue 15/02/2005 14:22 To: System 21 Users Subject: [SYSTEM21] The "standard" environment Long ago, I was persuaded that the correct way to set up S21 was to leave the blank environment totally alone. Any changes (to library lists, tasks, menus) would go into the appropriate environments. This advice is repeated in the "redbook" that came out 3-4 years ago. Now, Geac are saying that this is not the way to go. Instead, any new tasks should be created in the blank environment and library lists should be amended in the blank environment. They say that as long as you use library mapping and follow their standards for customised tasks everything will be fine, and that this setup is easier to maintain and understand. No need to define the applications in your "standard" environment because you don't need them - you can use the blank environment. There are some obvious benefits such as not needing to authorize users to both the blank and standard environments. However, I still have some doubts, but I am not sure whether I have just been thoroughly indoctrinated in the old way of thinking and just can't think straight. For example, if I want to change certain jobs to run in different job queues, I can change the task definition in the live and/or test environment and it works fine, but I haven't touched the standard definition. If I make changes like that in the blank environment they may get overwritten by a PTF or new release. Or is there some smarter way to achieve the same thing? Any thoughts? And have Geac announced this change in thinking somewhere that I haven't noticed? _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
