Hi Everyone, We are evaluating whether to convert/update the VTAM/SNA NETID for existing LPARs in our GDPS environment and would appreciate guidance from anyone who has gone through a similar exercise.
Current situation: - Existing production and DR LPARs are already operational under the current NETID. - We are not fully certain whether there are still active dependencies on SNA connections, especially from older CICS or IMS applications/systems. - We want to understand the operational and application impact before making any changes. Our main questions are: 1. What is considered the best approach for changing NETIDs for existing LPARs in a GDPS setup? 2. How do you typically identify hidden or legacy SNA dependencies from CICS, IMS, LU6.2/APPC, ISC, or external partner systems? 3. Is it generally acceptable/recommended to keep the same NETIDs across GDPS-managed environments (Prod/DR), assuming they are never active simultaneously? 4. What are the risks or common issues encountered when changing NETIDs on established systems? 5. Are there specific VTAM, CICS, IMS, RACF, or automation definitions that are commonly overlooked during such a migration? 6. Did anyone perform this with phased coexistence/testing before cutover? If yes, what worked well? We are especially interested in: - Lessons learned - Discovery techniques for active SNA usage - GDPS implications - Any IBM recommendations or field experience Thanks in advance for any advice or war stories you can share. Steve ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
