[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

comm_connect call comming to grief - ever seen this condition?

To: <ftpapi@xxxxxxxxxxxxx>
Subject: comm_connect call comming to grief - ever seen this condition?
From: "Peter Myers" <pjmyers@xxxxxxxxxxxxx>
Date: Mon, 2 May 2005 19:32:37 -0700
Importance: Normal
Reply-to: ftpapi@xxxxxxxxxxxxx
Sender: owner-ftpapi@xxxxxxxxxxxxx

Running a version of EXAMPLE4 of Scott’s HTTPAPI (just downloaded), the comm_connect call at line 3266 in proc http_persist_open in Srvgm HTTPAPIR4 comes back with *ON, so a *NULL pointer is returned.

Anyone know what this means: something not configured, or not started in the QHTTPSVR sbs – or what? Any help much appreciated,

Thanks,

Peter Myers

Follow-Ups:
- Re: comm_connect call comming to grief - ever seen this condition?
  - From: Scott Klement

Prev by Date: Re: Files not received unless already created (long)
Next by Date: Re: comm_connect call comming to grief - ever seen this condition?
Previous by thread: Re: Files not received unless already created (long)
Next by thread: Re: comm_connect call comming to grief - ever seen this condition?
Index(es):
- Date
- Thread