gtpm2m0n | Migration Guide: Program Update Tapes |
This section discusses the migration considerations for authorized program
analysis reports (APARs) other than the small programming enhancements (SPEs)
discussed previously.
Information Provided | Where to Go For More Information |
---|---|
Critical APARs shipped on Program Update Tape (PUT) 2 | Critical APARs |
APARs that correct incorrect APARs shipped on previous PUTs | APARs that Correct Incorrect APARs Shipped on Previous PUTs |
Table 48 summarizes critical APARs shipped on PUT 2. These critical APARs are valid at the time PUT 2 ships and are subject to change later.
Please see the APAR response information that accompanies each APAR and your IBM service representative for more information about critical APARs.
This information is presented in numeric order based on the APAR
number.
Table 48. Critical APARs Shipped on PUT 2
APAR Number | Description |
---|---|
PJ13765 | Provide Access to Pool Records Through FACE/FACS/FACZC |
PJ14843 | Inefficient Processor Utilization under PR/SM |
PJ15053 | Incorrect Base PSON During Fallback from TPF 4.1 System to TPF 3.1 System |
PJ15070 | Pool Directory Update (PDUs) Rolled in Without Proper Checks |
PJ15071 | Multi-Processor Interconnect Facility (MPIF) May Use Wrong Size Block for Incoming Message |
PJ15074 | Multi-Processor Interconnect Facility (MPIF) Trace may Cause CTL-001 |
PJ15089 | Enhancements to IBM TPF Database Facility (TPFDF) Dump Options |
PJ15112 | Data Reduction Reports Are Not Clear |
PJ15213 | CPSE Stack Corruption Will Occur With TPF 3.1 SNAPCs |
PJ15332 | CTL-001 in CCSONS Caused by Bad Base Register on CLNKC |
PJ15482 | Time-Initiated Keypointing Loops Forever With No Prime Modules |
PJ15486 | Auxiliary Loader (ALDR) Fails When Loading Large System Tables |
PJ15508 | Pool Address is Released Twice By a Release Chain Request |
PJ15542 | IPC OPR-2A3 Dump Does Not Dump Multi-Processor Interconnect Facility (MPIF) Tables |
PJ15668 | The ZPMIF STOP DEVICE Command Does Not Always Work |
PJ15657 | Excessive LOCK Contention on Channel and Device Tables |
PJ15663 | A CTL-572 is Taken During ZOLDR ACCEPT Processing |
PJ15667 | Multi-Processor Interconnect Facility (MPIF) Priming May Get Into an Infinite Loop |
PJ15744 | Working Storage Depletion (CTL-00C) Running Data Collection |
PJ15752 | Continuous CTL-RB Errors Running Exception Recording |
PJ16082 | Catastrophic Low Core Condition from Looping Message |
PJ16175 | CTL-001 Catastrophic Following a CTL-05A Tape I/O Error |
PJ16206 | Inefficient Module Selection Algorithm During Capture |
PJ16589 | Unable to Synchronize to STR Using TSC |
PJ16746 | Potential Loss of Data |
PJ16774 | CTL-001 Can Occur When CPSF Switches from ECB Virtual Memory (EVM) to System Virtual Memory (SVM) |
PJ16978 | Processor Hangs During Concurrency Filter Lock Facility (CFLF) Restart |
PJ17416 | Potential Database Corruption at End of Module Copy |
PJ17568 | Add Support to Allow Shared LU 6.2 Conversations |
PJ18124 | Possible Database Corruption |
Table 49 summarizes APARs contained on PUT 2 that fix incorrect APARs
shipped with the current PUT or previous PUTs. This table is ordered in
ascending numeric order based on the correcting APAR number.
Table 49. APARs Correcting Incorrect APARs Shipped on Previous PUTs -- PUT 2
Correcting APAR Number (PUT 2) | Incorrect APAR Number | PUT That Shipped the Incorrect APAR |
---|---|---|
PJ16331 | PJ14078 | PUT 1 |
PJ16478 | PJ15271 | PUT 2 |
PJ16517 | PJ14605 | PUT 1 |