Db2 Tools

Expand all | Collapse all

r16 to r18 upgrade help

Jump to Best Answer
  • 1.  r16 to r18 upgrade help

    Posted 06-03-2015 12:26 PM

    Hi,

     

    I'm upgrading our CA for DB2 z/OS tools from r16 to r18. I've already completed the SMP/E steps and have completed most of the post-installation configuration.

     

    I've changed the PTXMAN task to point to the new r18 datasets. However, when I start PTXMAN, it still points to r16 version. What am I doing wrong? This is the message I see:

     

    PXM0100 CA/XMANAGER 16.0 INIT IN PROGRESS ID=1600

     

    Thanks,

    Kumaresh



  • 2.  Re: r16 to r18 upgrade help

    Posted 06-03-2015 12:42 PM
      |   view attached

    Look to see what proclib the started task is starting from – perhaps the started task you updated is not the one that is being pulled in at start-up time

     

    Look for IEFC001I PROCEDURE PDTT01DB WAS EXPANDED USING SYSTEM LIBRARY (the library name would be here)

     

    Chris hoelscher

    Technology Architect

    Database Infrastructure Services

    Technology Solution Services

     

    123 East Main Street

    Louisville, KY 40202

    choelscher@humana.com<mailto:choelscher@humana.com>

    Humana.com

    (502) 714-8615

    (502) 476-2538



  • 3.  Re: r16 to r18 upgrade help

    Posted 06-03-2015 01:02 PM

    Yes, I did check that and it is pulling the PROC from the correct dataset.



  • 4.  Re: r16 to r18 upgrade help

    Posted 06-03-2015 01:59 PM

    Make sure you have to correct XMANID in your PROC.  It sounds like you are still pointing to R16 somewhere.

     

    Also check your PTILIB and PTIPARM DDs to make sure they are for your R18 install.

     

    Thanks

    Daniel Brown



  • 5.  Re: r16 to r18 upgrade help

    Posted 06-03-2015 01:59 PM

    When you say you changed the R16 Xman proc to point to R18 I wouldn't suggest you do that.

    Keep the R16 proc as R16 and create a new R18 proc make sure you the 4 important DD's point to R18 libraries

    they are

    STEPLIB, PTILIB, PTIPARM and PXMPARM

     

    Rather than let the XMANID default update your R18 proc XMANID parm to something like 1800

     

    e.g

     

    PTXDV180 PROC XMANID=1800,

    XSYS=Y,

     

    Thanks Keith



  • 6.  Re: r16 to r18 upgrade help
    Best Answer

    Posted 06-03-2015 05:05 PM

    A support case was opened, and Kumaresh contacted.  r16 version rel files inadvertently populated the r18 target libraries.  The r18 platform was scratched, and the install restarted from the top..



  • 7.  Re: r16 to r18 upgrade help

    Posted 06-03-2015 05:36 PM
      |   view attached

    Just as an alternative approach – we NEVER use release-dependent dataset names for any product I support (idms, db2, plati – oops, – CA-DB2; we have had the same sandbox/staging/test/qa/training/prod runtime dataset names for 20+ years – when it comes time to upgrade -= we empty and populate the sandbox from the SMP/E target libs – then as each environment is updated, we copy the libraries from the previous level up (to make sure we do not introduce any untested modules anywhere else other than the sandbox area

     

    Chris hoelscher

    Technology Architect

    Database Infrastructure Services

    Technology Solution Services

     

    123 East Main Street

    Louisville, KY 40202

    choelscher@humana.com<mailto:choelscher@humana.com>

    Humana.com

    (502) 714-8615

    (502) 476-2538

     

    The information transmitted is intended only for the person or entity to which it is addressed

    and may contain CONFIDENTIAL material.  If you receive this material/information in error,

    please contact the sender and delete or destroy the material/information.



  • 8.  Re: r16 to r18 upgrade help

    Posted 06-11-2015 02:41 PM

    James - Thanks for your help !!