|
In reply to Steve's comment about option 50. This is only available when the PTF's P#PTV10015 and P#PTV10016 have been installed on your system. These PTF's are part of the those that deliver Multiple Application Environments. The details on the above PTF's is in MOP 297. It should also be noted that the PTF's associated with MOPS 230 and 243 must be installed along with the above otherwise you will encounter some problems. Regards, John -----Original Message----- From: Prill, Steve [mailto:sprill@rexairinc.com] Sent: Friday, July 28, 2000 12:23 PM To: JBAUSERS-L@midrange.com Subject: RE: Upgrade to 3.5.2b SP2 You should not have to override the libraries when applying the PTF's. Option 50 then F15 on the PTF menu allows you to set up overrides that will apply to all PTF's. This is a big time saver. If you don't have this option you need PTF's for your PTF system. Also, make sure you regularly check the Geac web site http://jbaworld.com/services/customer/ (you must be registered) for the latest MOP's, Support Alerts and Functional Briefs. We have V3.5.2B SP3 in test and there have been a couple of alerts issued in the last two weeks that we need to investigate. Steve Prill mailto:sprill@RexairInc.com -----Original Message----- From: John McPherson [mailto:JMcPherson@fossil.com] Sent: Friday, July 28, 2000 12:49 PM To: 'JBAUSERS-L@midrange.com' Subject: RE: Upgrade to 3.5.2b SP2 Theresa, We have been involved in doing this in the past and it works OK. However, the biggest pains are: always overriding the library names when applying each PTF; making sure that the Application Manager changes do not effect the live environment; and keeping any changes being made separate (i.e., program changes for the uplift separate from current development to support the live environment during the uplift process). In addition what this does not allow you to encounter is any problems that might arise applying the PTF's over the production database. What we are doing, at Fossil, is implementing what Geac calls a "World". This is a duplicate of your current setup and renaming the libraries to keep them separate from the currently implemented environments (you do this for the IPG*, OSL*, and custom libraries). There is a bunch of steps, which took someone here about 2 days to do. This keeps everything separate and makes the testing process simpler yet more complete. The documentation we got on how to create a new "World" is available from Geac. if you have any more questions, you are welcome to contact me directly. Regards, John McPherson Project Manager Fossil Partners, LP -----Original Message----- From: Gaffney, Theresa [mailto:Theresa.Gaffney@pollak.com] Sent: Friday, July 28, 2000 8:29 AM To: JBAUSERS-L@midrange.com Subject: RE: Upgrade to 3.5.2b SP2 We are just in the planning stage of upgrading to 3.5.2b. Has anyone tried to install to a test environment? We have three environments using the same source code. We were informed by Geac that we could install the upgrade to just one of our environments without disturbing the live one. I would be interesting in hearing from anyone that has the same scenario. Thanks -----Original Message----- From: Jim_Hawkins@tsss.com [SMTP:Jim_Hawkins@tsss.com] Sent: Friday, July 28, 2000 8:04 AM To: JBAUSERS-L@midrange.com Subject: Re: Upgrade to 3.5.2b SP2 We are in the process of upgrading to 3.5.2b sp2 also (we were supposed to upgrade last weekend in fact). We have applied to a test world. Issues we have found..... 1. In test world our MPS and MRP are reporting nothing! Geac support is telling us that this is because of an improper install procedure. We were told (asking several times to be sure) that we could upgrade each application from 3.5.1 to 3.5.2b. When we were completely to 3.5.2b we could apply sp 1 and sp 2 to each application. We are now being told that the entire system must go 3.5.2a. then 3.5.2b, then sp1, then sp2... 2. There are several library list gotchas when applying to a test world (hard coded libraries) 3. This past weekend we applied to live 3.5.2b--sp2. As part of our standard upgrade procedure we do testing of the upgraded system prior to allowing users access. We received an error on PTF PD-V3-0058! I reviewed the job log but did not see anything out of the ordinary from any other PTF job log I ever looked at. Turns out we lost all data in OSLPDF3 library. All data files were empty! We tried running several MPS/MRP related programs and had problems up the wazoo. Numerous file objects did not exist in OSLPDF3 library. We then discovered that the users had not tested the MRP/MPS in the test world like they had told us they had (#1 above). We do not yet have a resolution from GEAC support on what this problem was. We made the decision Sunday afternoon to return to 3.5.1 until we could get some of these issues ironed out. Will keep the group posted on the resolution. Stefan Jansson <sjansson@fossil.co To: "'JBAUSERS-L@midrange.com'" m> <JBAUSERS-L@midrange.com> Sent by: cc: owner-jbausers-l@mi Subject: Upgrade to 3.5.2b SP2 drange.com 07/27/00 06:35 PM Please respond to JBAUSERS-L We're embarking on a project to upgrade our System/21 software to version 3.5.2b, SP2. I wonder if anyone else have gone through this, and if they can relate any particular gotchas or things to watch out for. Any and all feedback would be greatly appreciated. We're doing it in a separate "world" first, so we have some leeway for errors, but I don't want to take too much advantage of this fact. We're a Style shop. Technically Yours, Stefan Jansson Fossil Richardson, Tejas +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +---
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
