This note is just to inform other of a problem we found in the V4R3 to V4R4 upgrade. We had a couple of subsystems running in shared memory pools (SHRPOOL1 and SHRPOOL2). When we did the upgrade, these pools were changed to private pools. The difference is that shared pools can be dynamically adjusted by QPFRADJ and share memory, whereas private pools are fixed in size (unless you have carefully set them I believe). The result was that these subsystems now ran with 5MB of memory max. We discovered it because our backup of the IFS, DLO and configuration data occurred through this subsystem, and the time to do these increased dramatically. Had it not been for that, we wouldn't have found it. We haven't had confirmatoin from IBM that it was the upgrade process that caused the change from shared pool to private pool, but it occurred during that process and wasn't done by the person running the upgrade so ..... Don't get me wrong, I am not blaming or complaining, I am just warning others that there appears to be a problem and they should be careful. (I wouldn't like to write the upgrade process, because it has to account for every possible variant of OS setup - what a nightmare! The fact that it rarely has a problem is an amazing feat.) Russell