Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Back to discussions
Expand all | Collapse all

zPDT z/OS 2.1 to 2.2 Gotchas

  • 1.  zPDT z/OS 2.1 to 2.2 Gotchas

    Posted Wed March 29, 2017 08:03 AM

    Just wanted to start a topic on some of the changes encountered when going from z/OS 2.1 to 2.2 using zPDT and the ADCD distributions.

    In running 2.1 I made a change to the system name, SYSNAME, symbol in the IEASYM00 member.  The IEASYSxx members, in 2.2, now have the SYSNAME symbol as part of the LOGREC, PAGE and VIODNS variables.  In copying my customizations over to version 2.2, these changes didn't work since these datasets based on my 2.1 install were not found.  This caused errors/messages during the IPL.  My solution was to hardcode the default system name S0W1 as part of the dataset names in my customized IEASYSxx members.

    Still working on getting 2.2 up and running, but this was the initial issue I came across.

     

     

     

     

    jmal


Related Content