> If this is an issue that had minor impact when real memory was much
> smaller, perhaps an INFO categorization was appropriate then. If with
> typical memory configurations of today it is now causing the appearance
> to end users of an outage of several minutes, the impact is no longer
> minor and it would be equally appropriate that its status should be
> re-visited and changed to a Defect APAR worthy of some resolution.
As was already mentioned, D M=STOR processing was redesigned in
z/OS 2.2 in order to scale better for large memory sizes.
For comparison, on a z13 machine (full speed, not subcapacity):
z/OS 2.2 with 512GB
16:32:04.71 -RO S5D,D M=STOR
16:32:04.71 IEE174I 16.32.04 DISPLAY M 402
REAL STORAGE STATUS
ONLINE-NOT RECONFIGURABLE
0M-524288M
ONLINE-RECONFIGURABLE
NONE
PENDING OFFLINE
NONE
0M IN OFFLINE STORAGE ELEMENT(S)
0M UNASSIGNED STORAGE
z/OS 2.1 with 101GB
16:39:01.21 -RO S5H,D M=STOR
16:39:03.87 IEE174I 16.39.01 DISPLAY M 100
REAL STORAGE STATUS
ONLINE-NOT RECONFIGURABLE
0M-88064M
103424M-153600M
ONLINE-RECONFIGURABLE
88064M-103424M
PENDING OFFLINE
NONE
0M IN OFFLINE STORAGE ELEMENT(S)
0M UNASSIGNED STORAGE
STORAGE INCREMENT SIZE IS 512M
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
