Special considerations for REXX applications
If you have REXX application programs you should be aware of how CICSPlex SM behaves in the case where you apply a PTF to some members of a CICSplex but not others, you modify a REXX API program to put a value in a new table field introduced by the PTF and the REXX program then connects to a CMAS which has not had the PTF applied, and which therefore has no definition for the new field.
In this case:
- The CMAS does not transmit the value of the new field to the maintenance point CMAS.
- The maintenance point CMAS (which is at the highest level) transforms the record area to give a default value to the new field. The new value may be different from that originally specified by the REXX program.
- The maintenance point CMAS then broadcasts the record back to the originating CMAS, but transforms the record back to remove the new field. At this point, the maintenance point repository will not contain the intended value, (it will contain the default value) and when it has broadcast the record back to the originating CMAS, this repository will have had the intended value removed.
- If the same REXX program issues a TPARSE of the record, the value of the field is still the same as it was at the time it was created, and is not changed by the TPARSE. This might cause the program to indicate, wrongly, that the field contains the intended value, whereas, in the maintenance point repository, the field has the default value, and in the back-level CMAS repository, the field does not exist.
- If a REXX API program subsequently connects to the back-level CMAS and issues a TPARSE of the record, the new field will not be populated by the TPARSE. In this case the field will have the normal REXX default value - the field value will be the same as the field name.