1 / 23

Migrating to Hydstra V10

Migrating to Hydstra V10. Peter Heweston - August 2009. Introduction. Migrating to V10 might be simple or complex Simple No external links to Hydstra except data import Single data system No data sets Few programs developed for you by Kisters Complex Many external links to other systems

myrna
Download Presentation

Migrating to Hydstra V10

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Migrating to Hydstra V10 Peter Heweston - August 2009

  2. Introduction • Migrating to V10 might be simple or complex • Simple • No external links to Hydstra except data import • Single data system • No data sets • Few programs developed for you by Kisters • Complex • Many external links to other systems • Multiple data systems • Use of data sets • Lots of Perl code and batch jobs

  3. Upgrading to V10 • Simple • Insert V10 CD, run SETUP.EXE • Complex • Copy production system to test system • Upgrade test system • Run HYFIND jobs and fix problems in scripts and INI files • Maybe pay Kisters to help • Test everything • Upgrade main system • Migrate new scripts and INI files across • Use Beyond Compare V3

  4. HYCONFIG • You MUST remove PERLLIB statement from HYCONFIG.INI • Do it for all HYCONFIG instances you can find

  5. HYFIND • HYFIND.HSC is a script for identifying potential upgrade issues in your V9.6 system prior to upgrading to V10 • You can download a V9 version from http://hydstra.kisters.com.au/index.htm • You can also download the V10 Help file from the same place to read about the issues and what to do about them. • If you're game you can run HYFIND after upgrading to V10

  6. Variable Domains • V10 UPGRADE will guess at variable domains • It will probably get many of them wrong • You will need to review the domain of every variable • HYCLIPIN Database Export to Excel • Fix up in Excel • HYCLIPIN Database Import to work area • HYDBUTIL UPDATE VARIABLE [PRIV.HYCLIPIN] DOMAIN S

  7. Utility Tool Upgrade • Many obsolete tools removed • Many upgraded to 32 bit • Some have slightly different parameters • gnuegrep -i junk >found.txt • becomes • gnuegrep -iU junk>found.txt • Need to run HYFIND [V10_OBSOLETE_TOOLS] • Examine the output carefully • Help file topic2007 Cleanup of 16 Bit Tools in UTEPATHdetails what to do

  8. All Tables in DBFPATH • Scripts that rely on RATEPATH, GAUGPATH etc need reworking • HYFIND [V10_Bad_Paths] will find them • You may need to consider using public work areas instead of relying on tables being in a specific directory • You should reconsider scripts that copy tables around • How will they work under Oracle or PostgreSQL • Use HYDBUTIL COPY whenever possible • There are no tables in MISCPATH - all system tables are now in DBFPATH • No tables are delivered with Hydstra • Only XML content • Tables are created by install job

  9. Warning re Foxpro Tables • All Foxpro tables have .DBF and .CDX files • Tables with memo fields have .FPT files as well • Must copy all components together or tables will be broken • We often add memo fields between versions • Check all table copying to see if you now need to copy the .FPT • INSTREPR, PROJECT now have memos • Use HYDBUTIL and copy between work areas if possible

  10. Data Sets are No More • As mentioned already, datasets are gone • If you used data sets you need to rework usage to become data sources • First make minor revisions to DATASRC.INI • Use HYDSWIZ • Consider whether to show in WB • User level required to read and write • Job that used to change datasets now need to write to a different datasource instead • SVRIMP.INI should write to TE • Wont need a different HYCONFIG setting for WORKPATH • Remove dataset from HYXPLORE command lines

  11. Data Sets are No More • If you were using datasets to use a different RATEPATH you will need to use a different technique • Move your tables to a public or private work area • Use HYCONFIG variable DBSEARCH to point to them • Be sure you have a consistent set of tables there • RATEPER • RATEHED • PATEPTS • RATEEQN • SSHIFT • TSHIFT • TTABHED • TTABPTS

  12. Upgrade to Strawberry Perl 5.10 • Hydstra V10 comes with Strawberry Perl 5.10 • Perl 5.10 has many new features for the Perl enthusiast • New PERLPATH hyconfig variable \hyd\sys\perl defined • Path needs to include \hyd\sys\perl\bin • PERL5LIB should only contain \hyd\sys\run • HYFIND [V10_Perl_Jobs] will find problems • These changes only apply to jobs run outside of HYXPLORE or SVRRUN • \hyd\sys\perl\bin needs to be in the path • PERLLIB not needed • PERL5LIB should point to RUNPATH only • no refs to \perl\lib or \perl\site\lib • perl32.exe no longer exists, use perl.exe

  13. Upgrade Assistance from Kisters Pty Ltd • Ki$ter$ Pty Ltd can a$$i$t you to upgrade at our $tandard con$ulting rate$ • If HYFIND doesn't identify any issues and you don't use datasets you should be OK to go ahead • V10_Obsolete_Tools • V10_Perl_Paths • V10_Bad_Paths • Send us HYFIND outputs if you have any queries

  14. During The Life of V10

  15. Register All Subvars During V10 • Every subvariable must be correctly registered in VARSUB • specific site and variable • site 0 means all sites • variable 0 means all variables • Fix up VARSUB and VARTRACE • A rule for every subvar • The right rule • Don't map different subvar meanings to same VARTRACE • HYVARCHK will check that you have done it • You will not be allowed to upgrade to V11 until you have

  16. Variables During V10 • During the life of V10 you will need to populate the ALPHAVAR field in VARIABLE • Any variables not populated will remain numeric • You may choose to do nothing except fix VARSUB • V11 will have alpha sorting • In V10 20 sorts before 100 • in V11 20 sorts after 100 • V11 upgrade will be huge, as all TS files will need to be re-written

  17. Re-zip Old Logger Files • Historically all logger files under \HYD\LOG have been compressed • Various compression tools were used • PKZIP made .ARC files • LHA made .LZH files • 7ZA made .ZIP files • Should re-compress all files to .ZIP • HYZIPLOG.HSC will re-zip all files • Must be run while you can still run 16 bit tools • No 64 bit windows • No long filenames

  18. Consider Using TSPATH • New HYCONFIG variable TSPATH is defined as \hyd\dat\ts • We encourage datasources be stored under TSPATH • For example TELEM datasource should be stored under TSPATH\TELEM • \hyd\dat\ts\telem • Get rid of HYDPATH and WORKPATH • \hyd\dat\ts\archive • \hyd\dat\ts\work • Can still use Windows permissions to control access and visibility

  19. Rework HYSTNS Expressions • You should rework HYSTNS expressions that do directory listings to use new HYSTNS facilities • DSOURCES returns list of datasource of a specific type • TSFILES returns list of sites of specific datasource • instead of • DIR(CONFIG(WORKPATH)*.A) • use • TSFILES(A) • or better • TSFILES(DSOURCES(ARCHIVE))

  20. Eliminate Unnecessary HYSETENV calls • A program run from the Hydstra menus will have many environment variables predefined • DBFPATH, JUNKPATH, MISCPATH, PRMPATH, PRMPATH, PRMEXT, PTMPPATH, RUNPATH, TEMPPATH, TSPATH, UTEPATH • No need to set them again in batch jobs with HYSETENV • HYFIND [V10_Unnecessary_Paths] will find them • Note that HYDPATH and WORKPATH are not set by default

  21. Rotsa Ruck!

  22. Questions and Discussion

  23. Migrating to Hydstra V10 Peter Heweston - August 2009

More Related