Original Message:
Sent: Thu March 13, 2025 08:57 AM
From: Will Smith
Subject: NUMTCB
The cost of starting a new address space isn't really about the system resources it takes. It's really more about can the application(s) calling the SPs afford to wait for a new address space to start.
With WLM cycling every 10 seconds, before it decides to start another WLM SP task, that 10 seconds could be costly to you.
I've experienced slowdowns in applications and I could not afford to wait for WLM to react, so I use NUMTCB for certain address spaces to avoid this cost.
------------------------------
Will Smith
------------------------------
Original Message:
Sent: Thu March 13, 2025 03:13 AM
From: Soledad Martinez
Subject: NUMTCB
Good morning James,
they were created on 2011, long ago :-)
I have found others with the MNSPAS parameter, that according to IBM:
"If the environment is one in which the cost of starting new address spaces is very high, set the MNSPAS subsystem parameter to specify the minimum number of address spaces that are to be started and maintained."
This MNSPAS was also added on 2011, and its remark refers the apar PM27097, I don't know if still starting a new address spaces is that costly.
Thank you very much!
------------------------------
Soledad Martinez
Db2 z/OS System Programmer
Volkswagen Group Services
Salinas - Asturias
Original Message:
Sent: Thu March 13, 2025 02:02 AM
From: James Campbell
Subject: NUMTCB
Vague memories of DB2 V6 with 2GB address spaces. When were the SPs that use the environments created?
Perhaps no longer relevant.
------------------------------
James Campbell