scottklement.com

Hi there!

I was able to get libhttp installed and it was a tremendous help to integrate my companies 3PL integration however I might have something a bit weird setting wise because I have to use my IFS Home Src file be the holder of my LIBHTTP files otherwise it can't find things.

I'm wondering if its because something in my export keeps pulling the git pull request into that home directory. But to be honest this is my first time using git (Well technically second now that I'm trying to grab the update) in my standard LIBHTTP the qsrc files are empty.

I did try to use FTP and they still came across as empty when I checked on things. So I'm at a loss. Thank you for any assistance.

I don't understand.

What does 'IFS Home Src' mean exactly?

You refer to 'standard qsrc files'. I have no clue what you mean!!

You say "something in my export keeps pulling the git pull request into that home directory". What do you mean by 'export'? why would it be running git commands?

No problem! Let me explain a bit better. I apologize for the confusion. I'm using the PASE client and doing a git pull request from your GitHub

(As an Aside: Its probably a user error but I figured I'd ask the question)

So I do a GIT pull request following this:

export PATH=/QOpenSys/pkgs/bin:$PATH
https://github.com/ScottKlement/httpapi.git

However my files never seem to get to the PATH. It always seems like the libhttp files go into my /home/user folder structure under LIBHTTP (so /home/user/libhttp)

So inside that folder is src and unless I add a new source file there, the program can't compile.

Thank you for the response!

cdougherty wrote: Sat Feb 21, 2026 1:13 pm So I do a GIT pull request following this:

export PATH=/QOpenSys/pkgs/bin:$PATH
https://github.com/ScottKlement/httpapi.git

It's unclear what you mean by a "git pull request following this". And you aren't explaining what IFS directory you want the files to be placed in, or what you are doing to put them there. So I will tell you what I would do, and you can figure out from there what you're doing differently.

1. I'm assuming you want to download the HTTPAPI tool into the IFS folder /home/cdougherty/code/httpapi and that you want to compile it into a library named LIBHTTP153. If this is incorrect, then substitute the IFS folder you want to use and the library you want to use in the following example.
2. First go to a PASE shell. (recommended way is to use SSH, but you can also do it from green screen with CALL QP2TERM) I assume you are already doing this part.
3. Based on what you've said so far, your PATH within PASE is not set up correctly system-wide, so you have to manually add the yum packages directory... that's unfortunate, but to add it only for your session, type:

   Code: Select all

   export PATH=/QOpenSys/pkgs/bin:$PATH

4. Only if you haven't already installed git, you can install it via

   Code: Select all

   yum install git

5. Only if you haven't already installed GNU make you can install it via

   Code: Select all

   yum install make-gnu

6. Switch to the IFS Directory that will contain the directory for HTTPAPI.

   Code: Select all

   cd /home/cdougherty/code

7. When you pull from git, by default, it will create a new directory named httpapi within the directory you selected with 'cd' in the last step. You can override that behavior by adding more options to the git command line, but I assume you don't need to. Since you are in the /home/cdougherty/code folder when you run git it will put the code into /home/cdougherty/code/httpapi. Here's the command to pull with git:

   Code: Select all

   git pull https://github.com/ScottKlement/httpapi.git

8. Now switch to the folder you just created and downloaded stuff into.

   Code: Select all

   cd httpapi

9. Compile and install HTTPAPI into library LIBHTTP153 with:

   Code: Select all

   make LIBRARY=libhttp153

10. If all goes well, you'll see it compiling all of the parts of HTTPAPI and placing them into a library named LIBHTTP153. Once this is done everything should be in that library.

cdougherty wrote: Sat Feb 21, 2026 1:13 pm However my files never seem to get to the PATH. It always seems like the libhttp files go into my /home/user folder structure under LIBHTTP (so /home/user/libhttp)

So inside that folder is src and unless I add a new source file there, the program can't compile.

I have no idea what you're talking about. The PATH has nothing to do with where files are placed. Yes there is a folder under 'src', that is where it finds the source code to compile from. But it will create any source files it needs when you run make, there's no need for you to create them manually.

NOTE: There is no need to use the Git method of installation unless that's your preference. For a traditional IBM i progammer or administrator, i would use the save file method instead. (Unless you plan to make modifications to HTTPAPI, or unless you are comfortable and familiar with PASE and Git that is.) The traditional installation instructions can be found here: https://www.scottklement.com/httpapi/