RE: Host Servers startup question

["Evan Harris" <spanner@xxxxxxxxxx>]

Hi James

STRHOSTSVR is the command you require.

> From memory QSERVER has to be started (and possibly QSYSWRK and QUSRWRK) but
the subsystem thing seems to be release dependent.

I find the CWBPING command useful at the client end to determine what is
running and accessible, but that's a client access utility.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, 1 May 2008 11:52 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: Host Servers startup question

I'm not a Host Servers guru (nor do I play one on television), and since 
we're not a Client Access shop, we didn't have Host Servers running 
until we needed it for JDBC and JTOpen.

And I'm not getting very far in the manuals on this, either.

I know how to make Telnet and FTP come up automatically when TCP comes 
up, but what about the Host Servers ports? We've had situations in the 
past where they weren't started automatically, and I'm not entirely sure 
how to make them start automatically, or even to determine whether or 
not they will do so.

Heck, at the moment, I can't even remember how to start Host Servers 
manually.

Can somebody please point me in the right direction?