RE: The i and DHCP

Windows is not older. For the first release of OS/400, 90% of CPF from the System/38 was reused, with a little bit from the System/36 thrown in and a lot of new code. OS/400 release 1 was basically a superset of CPF. The System/38 was announced in 1978 and started shipping in 1979, so Windows is less legacy when using that definition, but not by much.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Jones
Sent: Thursday, October 04, 2012 07:23
To: Midrange Systems Technical Discussion
Subject: Re: The i and DHCP

In my experience DHCP has not been an issue. Firewalls, duplicate client IP addresses due to network misconfiguration, running out of DEVDs, etc.
but not DHCP.

What is the resolution for the devices when they can't connect? That should give you an idea as to how/why the problem is happening.

In the mean time, on the i I would suggest making sure QAUTOCFG and QAUTOVRT are set appropriately. On the client side, consider configuring the emulator to generate unique session names (QPADEVnnnn) unless your environment requires static names.

As to the help desk's attitude about the i, their manager should be stressing the platform's relative importance to the help desk staff. The staff needs to care because the company uses it. The debate about legacy v. modern is immaterial. (And FWIW Windows came out in 1984; OS/400 in 1988. Using the definition of legacy = older, Windows is more legacy.)