ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AllowUserKeyCSA(NO) enforced since z/OS 2.3


Article ID: 144629


Updated On:


Allocate DASD Space and Placement


IBM will be removing the option of AllowUserKeyCSA(YES) in future, enforcing it to be NO..

This may impact clients as below;
When getting the sub-pool (227/228/231/241) of the common area (CSA / ECSA) using each interface of GETMAIN, STORAGE OBTRAIN, and CPOOL BUILD, the protection keys 8 to 15 (User Key) cannot be used.


Release : 12.5

Component : CA Allocate DASD Space and Placement


CA Allocate is not impacted by the z/os 2.4 CSA User Key restriction.