RE: The "*ADMIN" HTTP server configuration itself seems to bemissing?!?

Also, look for the job logs of the failed strtcpsvr *http httpsvr(*ADMIN)
command.  They usually will tell you exactly what the problem is.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert
Sent: Tuesday, May 23, 2006 11:16 AM
To: Midrange Systems Technical Discussion
Subject: Re: The "*ADMIN" HTTP server configuration itself seems to
bemissing?!?

Fritz Hayes <fhayes@xxxxxxxxxxxxx> wrote:
> Have you checked to see if there are no other services 
> running on the admin port? (netstat option 3)

The port is definitely free; generally WRKTCPSTS option 3 
is the first thing I do after trying to start a 
little-used server (even before attempting to access the 
server).

Moreover, a tied-up server port wouldn't explain why I 
can't so much as inspect the configuration.

To coin a phrase from an old movie,
HHHHHELLLLLLLLLLLLPPPPPPPPPP 
 MMMMMEEEEEEEEEEEEEEEEEEEEEE!!!!
--
JHHL