Re: Testing 1.31

[Charles Wilt <charles.wilt@xxxxxxxxx>]

   One other thing to be aware of is how you build your apps that use
   HTTPAPI..
   Use a DSPPGM and/or DSPSRVPGM and look at the imports screen...
   Service � � � � � �   Program � � Library
   QRNXIE � � �QSYS ��   QRNXUTIL � �QSYS ��   HTTPAPIR4 � *LIBL �   QLEAWI � � �QSYS ��   QP0LLIB1 � �QSYS ��   In the above example, the library list will be used to find
   HTTPAPIR4.� But I could have compiled my app to always look in
   LIBHTTP.
   Charles

   On Wed, Feb 24, 2016 at 5:40 PM, Scott Klement <[1]sk@xxxxxxxxxxxxxxxx>
   wrote:

     Hi Todd,
     The only thing that's installed outside of the library you install
     HTTPAPI into (it does not have to be LIBHTTP, that is just the
     default name) is a symbolic link in the IFS from /usr/bin/httpapi to
     the HTTPQSHR4 program in whatever library you pick.
     If you do not use the QShell interface to HTTPAPI, this symbolic
     link probably doesn't matter to you at all, in that case, no need to
     worry about it.� (This is the case for most HTTPAPI users, very few
     use the QShell interface.)
     If you do use the QShell interface, you probably want to delete that
     symlink, and create separate ones in different directories for each
     version of HTTPAPI, and have users adjust their PATH accordingly.
     Everything else is done in the install library.
     -SK
     On 2/23/2016 9:04 PM, Todd Settimo wrote:

     We are currently on 1.24 and are going to 1.31.� We want to test
     1.31 against the applications we have using HTTPAPI before we
     install and, looking for the easiest route to doing this, our
     thought is to install a secondary LIBHTTP lib at 1.31 and layer a
     project library under it with the apps in question. It seems pretty
     basic on the surface. I guess what we're wanting to know is if there
     are any objects installed outside of the LIBHTTP library that are
     created/affected when a new installation of the software is
     installed. Obviously we don't want to inadvertently step on the
     existing 1.24 functionality.
     Thanks for your time.

   -----------------------------------------------------------------------
   This is the FTPAPI mailing list.� To unsubscribe, please go to:
   [2]http://www.scottklement.com/mailman/listinfo/ftpapi
   -----------------------------------------------------------------------

References

   1. mailto:sk@xxxxxxxxxxxxxxxx
   2. http://www.scottklement.com/mailman/listinfo/ftpapi

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------