Accessing resource tables from a previous release
You can continue accessing the resource tables supplied with a previous release of CICSPlex SM.
In order to do this you must:
- Specify the release of CICSPlex SM data that you want to access on the VERSION option of the CONNECT command.
- Use the run-time module (EYU9AB00) supplied with the release you want to access or a subsequent release that supports it.
- Use a version of the stub module (EYU9AxSI) that is less than or equal to the run-time module.
| VERSION value | Stub module (EYU9AxSI) | Run-time module (EYU9AB00) | CMASs available | CMAS used | Data available |
|---|---|---|---|---|---|
| 0220 | V2R2 | V2R2 | V1R2 V1R3 V1R4 V2R1 V2R2 | V2R2 | V2R2 |
| 0120 | V1R2 | V1R2 | V1R2 | V1R2 | V1R2 |
| 0120 | V1R2 | V1R3 | V1R3 | V1R3 | V1R2 |
| 0120 | V1R3 | V1R3 | V1R2 V1R3 | V1R3 | V1R2 |
| 0120 | V1R4 | V1R4 | V1R2 V1R3 V1R4 | V1R2 | V1R2 |
| 0130 | V1R3 | V1R3 | V1R2 V1R3 | V1R3 | V1R3 |
| 0130 | V1R3 | V1R4 | V1R2 V1R3 V1R4 | V1R4 | V1R3 |
| 0130 | V1R4 | V1R4 | V1R2 V1R3 V1R4 | V1R4 | V1R3 |
| 0140 | V1R4 | V1R4 | V1R2 V1R3 V1R4 | V1R4 | V1R4 |
| 0210 | V2R1 | V2R1 | V1R2 V1R3 V1R4 V2R1 | V2R1 | V2R1 |
Table 2 shows some invalid combinations of the VERSION option, run-time module, and stub module and describes why they produce an error.
| VERSION value | Stub module (EYU9AxSI) | Run-time module (EYU9AB00) | CMASs available | Error description |
|---|---|---|---|---|
| 0140 | V2R1 | V1R4 | V1R4 V2R1 | Stub module release level is greater than run-time module. |
| 0210 | V2R1 | V1R4 | V1R4 V2R1 | Stub module release level is greater than run-time module. |
| 0210 | V1R4 | V1R4 | V1R4 | VERSION value is greater than run-time module. |
| 0210 | V2R1 | V2R1 | V1R4 | No CMAS available at the required run-time level. |
Note: For programs written in REXX, the compatibility issues are similar.
The Release 2 function package (which contains the necessary stub module)
can run successfully with either the Release 2 or Release 3 run-time module.
The Release 3 function package, however, cannot run with the Release 2 run-time
module; the Release 3 module is required.