|
Hello, If you have a new AS/400 you will need a new key. Otherwise, if you are just upgrading the same box to V4R5 using the 'scratch install' method that wipes out the old operating system, and the serial number and model number of your AS/400 are remaining the same, your old key will still work. Just restore your environment libraries. I recommend that when you save the data files for BPCS, that you also save the access paths. This will take longer to save, but is much faster to restore because you avoid rebuilding the access paths. Ensure also that required JOBQs, OUTQs and Subsystems are still in existence for BPCS jobs to run. If not, you will need to recreate them. Sometimes these are configured in QSYS, rather than QGPL and an operating system upgrade will wipe them out. (Research what you are using on your system now, before the upgrade). You can find lots of information on the configuration in the 6.1.00 and 6.1.01 install document for BPCS. This is very important for the ALAUNCH 'fat client' jobs since these jobs generally run in the BPCS install-created jobqs and subsystem. The Install documents should describe the subsystems and job queue entries that are created when BPCS installs, so that you can recreate them manually if need be. You may need to recreate any auto-start, pre-start or automated jobs that started your ALAUNCH daemon(s) used for fat client BPCS jobs. You also need to download the IBM Info APAR for BPCS from the IBM web site. II11293 is the APAR number - this tells you what PTFs are required for running your version of BPCS on that version of the operating system. This document is updated from time to time, so you should also be aware of the need to check this every so often for further recommended PTFs. Also make sure, if you are wiping out user profiles, that you restore them and restore authority so that the BPCS objects are owned by the proper owner and any authorities you granted/took away from BPCS files are retained. The typical Save/Restore guidelines found in the IBM system recovery guides should be followed when you back up your system, and this should work to restore your system properly for the scratch install. Thanks, Genyphyr Novak SSA GT ----- Original Message ----- From: "Roy Smith" <bpcsusergroup0@yahoo.com> To: <bpcs-l@midrange.com> Sent: Monday, April 15, 2002 7:45 AM Subject: BPCS 6.1.01 library restored on As400 > > Hello All!! > > We are using BPCS 6.1.01 mixed mode on AS400 platform > OS/400 V4R3 M0. > > Due to some problem in OS/400, we are unable to > upgrade OS400 from V4R3 to V4R5. IBM technical guy has > recomended to install OS/400 V4R5 from scratch on the > same machine. > > Question 1 > I have taken back up of all libraries of our BPCS > environment. My question is, after installing new > OS400 v4r5, can i simply restore my bpcs environment > on the same machine and start using BPCS with new > operating system ? Or I need to follow the BPCS > installation procedure using bpcs key ???? > > Question 2 > Do i need some ptf for V4R5 for the BPCS running > successfull on that version. > > appreciate your technical support!!! > regards > > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > http://taxes.yahoo.com/ > _______________________________________________ > This is the SSA's BPCS ERP System (BPCS-L) mailing list > To post a message email: BPCS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l > or email: BPCS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/bpcs-l. > >
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.