Re: 5250 for iPhone

David,

I think this is confusing because the original question was about 5250 for
the iPhone, and it morphed into a CLI vs iNav argument. My attempt to bring
it back to the original question flopped.

As for iPhone, it ~must~ have the web in order to work with your i. You
cannot plug it into a cable direct to your i - or direct to your network. It
connects using wireless technology to the web, then to your network, then to
your i. Without the web, the iPhone cannot see your i... Hence, 5250 for
iPhone is a web app! :-)

Trevor



On 7/25/08 11:23 AM, "David Gibbs" <david@xxxxxxxxxxxx> wrote:

Trevor Perry wrote:

It seems that the majority of servers have an HTTP interface to manage their
systems today. In fact, you can stick an ethernet cable from your pc to the
HMC port on a System i server and get a browser interface.

I don't argue that you can use a web interface to ADMINISTER a system ... but
when it comes down to it, using a command line is far more efficient for
problem determination.

If you want, the iPhone 5250 application can only be
accessed over the web, so is it a web app?

Huh? Where did you get that idea? It's not accessed over the web. It's a
native application running on the iPhone that connects to port 23 on the
remote host. It's no more a web app than CA400 is.

Ultimately, a web systems management tool is great, because I can access it
from outside the building. Using the "I must have a console" can only be
used as an argument inside the server room. Using it to justify iPhone 5250
does not work quite as well.

I don't have a clue what you are talking about.

And when can you NOT have a command line interface in a browser and over the
web? I think there are two different arguments getting wrapped up in each
other.

Again, I really don't understand what you are saying. 5250 access has nothing
to do with web access. Being able to issue a command through the browser is
not the same thing as having 5250 session.

david