|
I think we have a hybrid. We have Vanilla, a production environment and 2 test environments (1 a duplicate of live & 1 for development). Our test environments have separate libraries, library lists, tasks and menus. With manipulation of libraries you can test most things thoroughly before implementing them into the production environment. The only thing that is shared is the IPG* suite. Regards Helen Duncan Direct line: 0141 307 4887 e-mail: duncanh2@bp.com -----Original Message----- From: Jeff_Klipa/Harvard@harvardind.com [mailto:Jeff_Klipa/Harvard@harvardind.com] Sent: 12 November 2001 15:46 To: jbausers-l@midrange.com Subject: JBA ML - Other-Worldly upgrade OK, I have to get my 2 cents in here... IPG* libraries are the Application Manager System libraries... OSL* are the Application libraries... The PTF system is OSLPT*... Some examples : OSLINP3 is Program Objects for Inventory. OSLGLD3 is combined Program and Display objects for General Ledger (Financial apps dropped the P libs and combined into the D libs to save space in the library list several years ago) OSLD1F3 is Distribution Files objects (Similarly the Files libs were consolidated for Distribution and Manufacturing apps to save space) OSLGLF3 is General Ledger Files objects... We consolidated our libraries here as well... So we have : OSLF3 all files objects OSLD3 all program, display and printfile objects OSLS3 all Source... The PTF system allows you to setup cross reference tables facilitating applying the PTFs to the proper library if you have changed their names or consolidated... You can also override the TO libraries at install time... We have a test WORLD, and a test ENVIRONMENT within our Live World... The difference between a world and an environment is as follows : Let's say that your production Environment lives in your production World, that is to say that you have one set of all libraries for your live production and every library used for live production in that set makes up the production World. Programs libs like IPGAMF4, OSLINP3 and OSLGLD3 etc... You can also have a TST environment within your live production World that consists of TST Files libraries like OSLD1F3TST, OSLGLF3TST, etc... So you now have your default customer code environment (NN9 in the case of Aetna) and the test environment TST all living under one World... There is the blank environment (Vanilla) underneath all of that but we can save that discussion for another time... So you have all environments in this World sharing the following libraries : IPG* - Application Manager libs OSL* (program and display and printfile objects including msgfiles and helptext etc...) The only thing that the live and TST environments do NOT share is the FILES libraries... and library lists... That is the only thing that keeps them distinct... They share EVERYTHING else...!!! Tasks, menus, programs, display files, printerfiles, helptext, etc... If you had a separate TST WORLD you would have a duplicate of EVERY library (not just files) in the entire package with a different prefix... So instead of IPG* it could be XXG* and OSL* would be XXL*, for instance... When you apply PTFs that affect the programs or the IPG* libraries including menu and task changes you can have a dramatic impact on your live World... This is why having a separate WORLD is far preferable to use as a testing ground for applying/testing PTFs and performing your retrofitting project as opposed to a simple TST Environment... If you don't have lots of mods and you aren't that interested in really thorough testing then you can slam those PTFs into your live WORLD and hope nothing blows up in your face... You were looking for a job when you found this one, right...? ;) Get a copy of that Redbook too... SG245967.pdf Do a search at www.redbooks.ibm.com on the top right hand corner enter the search keyword SG245967. Download the PDF... Hope that helps... Good luck...! _______________________________________________ This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list To post a message email: JBAUSERS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l or email: JBAUSERS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/jbausers-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.
midrange.com
