× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: IFS API problem
  • From: "Mike Silvers" <msilvers@xxxxxxxxxxx>
  • Date: Fri, 29 Jun 2001 13:54:16 -0400
  • Organization: Hainey Business Systems

Scott,

It was a simple problem.  I did not qualify the file to the root
directory...so when it was looking for the file, it started in the current
directory (apparently the current directory is changed by the HTTP server).

Thanks for the info about the access().  I am going to change to that API.

Mike



----- Original Message -----
From: "Scott Klement" <klemscot@klements.com>
To: "RPG400-L" <RPG400-L@midrange.com>
Sent: Friday, June 29, 2001 1:15 PM
Subject: Re: IFS API problem


>
> A few ideas:
>
>    1) The proper way to check for the existance of a file in the IFS
>         is using the access() API, not open().   This probably won't solve
>         your problem, but I thought it should be mentioned...
>
>    2) Have you tried watching the program run (using STRDBG) when
>         it runs via the HTTP server?  When it's running, have you
>         checked all of the variables to make sure they make sense?
>
>    3) Have you tried making a "simplified" version of your program?
>         maybe one that ignores any parms or data passed to it, and
>         simply opens a file in the IFS, then does a SNDMSG to you
>         to give you the result?  Try running THAT both interactively
>         and via the HTTP server...
>
>    4) If your simplified code exhibits this same behavior, post the
>         simplified code to this mailing list, maybe we'll be able to
>         help from there.
>
>
> On Fri, 29 Jun 2001, Mike Silvers wrote:
>
> > Hi all.  I posted this on the Ignite/400 list and this list as well.
This
> > problem has to do with both RPG programming and internet problems.  I am
> > having some problems with an RPG program initiated from the
> > HTTP server using an IFS API.  Here is the problem:
> >
> > I have an RPG program that uses the IFS API open to check for the
existence
> > of a file.  I am attempting to open the file using read the read only
code.
> > If the file is there, I then close it and send a message saying that the
> > file exists.
> >
> > I tested the procedure using an RPG program that I call on the green
screen.
> > All works well.
> >
> > Here is the problem.  When the procedure is called from the HTTP server,
I
> > receive an error that the directory or file does not exist.
> >
> > The first thing I checked is the authorities of the directory,
> > subdirectories, and the file itself.  They all have *public authority
for
> > everything.  I also specifically added the users QTMHHTTP and QTMHHTP1.
> > Still no luck!
> >
> > Does anyone have any ideas?
> >
> > Thanks
> >
> > Mike
> >
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.