×
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.
That’s one of the big issues when a very big company with (some) very big customers designs a tool:
the forget about the big number of small and medium customers.
Some functionality of HMC enhanced+ interface might be useful if you manage 100+ boxes with 1000+ LPARs
(maybe), but if you’re some smaller with 20 boxes and 200 LPARs and you are used to the classic
interface, you’re lost. And (as written before) if you use some special features of IBM i, you’re lost, too,
because the IBM designers don’t know about IBM i.
For vSCSI/vETH we use a 3 digit numbering scheme to have nice ranges, some spare number ranges,
and even on a 8 LPAR box the numbers go up to 300. Makes documentation much more easy and we
can go with a common standard. I cannot imagine what will happen if we need to accept a
given automatic numbering.
That’s one reason i created RFE 131932 just to push the HMC developers. Have direct contact now
but they are on easter holidays ;-)
-h
Am 18.04.2019 um 01:57 schrieb Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>:
But yes, It seems like it's trying very hard to be a cloud management
system instead of a HMC...
midrange.com
