×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
> In 1988, OS/400 didn't support LPARs at all. I was solely talking
about virtual disks in *OPSYS LPARs within IBM i as hypervisor. Just to
be clear.
True, however the change required would be to the code running in the
IBM i guest, not that of the host. That code would need to be able to
deal with a somgle verylarge volume. That would be the same code used
for ALL IBM i partitions because it is the underlying I/O routines that
support everything IBM i does.
In my mind it would make even less sense to attempt to modify the I/O
code for guest LPARs only because now there are two sets of code to
maintain.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 3/23/2020 11:41 AM, Patrik Schindler wrote:
Hello Larry,
Am 23.03.2020 um 16:30 schrieb DrFranken <midrange@xxxxxxxxxxxx>:
I disagree. It is not 'A Bug' it is a design point that has been in there since 1988 and most likely from the S/38 before that.
In 1988, OS/400 didn't support LPARs at all. I was solely talking about virtual disks in *OPSYS LPARs within IBM i as hypervisor. Just to be clear.
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
