The change described in this topic was implemented through APARs for the following versions of CICSPlex® SM:
If the version of CICSPlex SM to which you are migrating has the PTF for that APAR applied, but the version of CICSPlex SM from which you are migrating does not have the PTF for that APAR applied, then changes could occur in the way PROGDEFs and TRANDEFs are installed through RASGNDEFs (resource assignment definitions).
If a PROGDEF or TRANDEF is automatically installed through a RASGNDEF that specifies a USAGE of REMOTE and a MODE of STAT, then with CICSPlex SM Version 3.1 and the PTF for APAR PK17787, the REMOTESYSTEM used when the PROGDEF or TRANDEF is installed in the target system will be the CICS system ID (SYSIDNT) of the related system. In previous versions of CICSPlex SM which did not have the equivalent PTF applied, if the PROGDEF or TRANDEF specified a REMOTESYSTEM, or the RASGNDEF override specified a REMOTESYSTEM, this would be used.
You need to ensure that all BAS definitions are updated to tolerate this change before migrating to CICSPlex SM Version 3.1 with the PTF for APAR PK17787.
Table 35 illustrates the differences in processing from previous versions of CICSPlex SM where the PTF for the APAR is not applied. CICA is the actual SYSIDNT of the target system. CICB is the actual SYSIDNT of the related system.
PROGDEF or TRANDEF REMOTE- SYSTEM | RASGNDEF USAGE | RASGNDEF MODE | RASGNDEF REMOTE- SYSTEM OVERRIDE | Target REMOTE- SYSTEM without PTF applied | Target REMOTE- SYSTEM with PTF applied |
---|---|---|---|---|---|
none | REMOTE | STAT | none | CICB | CICB |
none | REMOTE | STAT | CICX | CICX | CICB (1) |
CICZ | REMOTE | STAT | none | CICZ | CICB (1) |
CICZ | REMOTE | STAT | CICX | CICX | CICB (1) |
none | REMOTE | DYNAM | none | CICA | CICA (2) |
none | REMOTE | DYNAM | CICX | CICX | CICX |
CICZ | REMOTE | DYNAM | none | CICZ | CICZ |
CICZ | REMOTE | DYNAM | CICX | CICX | CICX |
Notes:
|