gtpm1m2q | TPF V4R1 Migration Guide: 3.1 to 4.1 |
Even if you do not plan to use the TPF/APPC support, you must be aware
of the following changes to the TPF 4.1 system that were made to
support 3-byte resource identifiers (RIDs).
Area that Changed | Description of the Change |
---|---|
Routing Control Parameter List (RCPL) | System recovery table (SRT) reference numbers were retired to make space
available in the current RCPL. The major effect of this change is that
the TPF 4.1 system no longer supports message recovery for 3600
multithread LUs. However, the TPF 4.1 system still supports
message recovery for other device types already supported.
The labels RCPLDESS and RCPLORGS are no longer supported, and these locations are now the start of the 3-byte RID, called RCPLDES3 and RCPLORG3. If you have 2-byte RIDs you can continue to reference the fields RCPLDESR and RCPLORGR to pick up the 2-byte RID value. |
INQRC | The input and output parameter area to INQRC was modified to support 3-byte RIDs. When RIDs are specified as input to INQRC, the 3-byte RID starts at offset 1 in the parameter area, and the 2-byte RID starts at offset 2 in the parameter area. On output from INQRC, the 3-byte RID is at offset 1 in the parameter area (label INQRID3), and the 2-byte RID is at offset 2 in the parameter area (label INQRID). |
GET_SPA/NCB | Segment CSNB now supports 3-byte RIDs; however, 2-RIDs are the
default.
If you have 2-byte RID support, you do not need to make changes in this area. If you have 3-byte RID support, you must turn on bit X'08' in the parameter byte (offset 4 bytes from the beginning of the input parameter area). This causes the RID to be returned in bytes 0 through 2 of the output parameter instead of bytes 0 through 1. |
RIDCC | RIDCC now returns a 3-byte RID at offset 1 in the output parameter area (RIDRID3). The 2-byte RID (RIDRID) is still located at offset 2 in the output parameter area. |
RVTCC | RVTCC now returns a 3-byte RID in the specified return register. This change does not affect you if you have 2-byte RIDs. |
ECB Work Area Changes | The SNA ECB work areas were changed to make room for 3-byte RIDs. The 2-byte RID, which was stored in EBW026-EBW027 and EBW038-EBW039, is now a 3-byte RID stored in EBW041- EBW043. EBW040 and EBW044 no longer contain copies of the RVT addresses. The 3-byte RID stored in EBW041 is the RID for the RVT containing the session information of the LU-LU session. The session partner field in the session RVT contains the RID of the partner LU. |
PIU Trace Facility and ZNPIU | The PIU trace facility and ZNPIU were updated to display the full 3 bytes of the origin and destination RIDs. |
In addition, these changes have occurred:
The RID is no longer a direct index into the resource vector table (RVT). In previous releases of the TPF system, programs could convert a RID to an RVT address through direct multiplication or by issuing the RIDCC macro to do the conversion. Now all programs must use the RIDCC macro to perform the RID-to-RVT conversion. In the TPF system, all TPF system code was changed to use the RIDCC macro but you will need to modify your own code, if any, that performs RID-to-RVT conversions.