On Tue, Sep 8, 2020 at 10:13 AM Mark Post <[email protected]> wrote: > > Gregory, > > In short, no. When a z/VM guest is logged on, it is created using what > is in the currently active CP directory. Any and all limitations, such > as the maximum amount of virtual storage, number of virtual CPUs, are > encoded in the control blocks for that guest. Any attempt to exceed > those limits will be denied. The only way to get the new, "larger," > limits will be to log the guest off and back on again. > > There are likely tools out there that run from a privileged account that > will go into the control blocks for the target guest and change things. > As you might expect, that sort of thing can be dangerous. Still, if > getting this done is important enough, you could ask on the IBMVM > mailing list to see if such a thing is out there, and where to get it. > > > Thank Mark for confirmation. For now I will stick to the "safe" way. Well reboot it is. Fortunately I might have an opportunity to do it today. I am planning to do "Machine esa 16" (which is the total number of cpus we have in the box) and then just put CPU statements 00-07 >From what I just tested this should give me initial 8 cpus and, and define cpu will work up to 16 thank you Gregory
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
