Backwards compatiblity with updates?

[jtaylor]

Are there any known backwards compatibility issues with updating LIBHTTP? I don't see any reference to updating in the docs (https://www.scottklement.com/httpapi/httpapi_savf.html) other than the step to delete the old library.

I don't know how to tell what version I currently have. LIBHTTP/HTTPAPIR4 shows a creation date of 06 Dec 16, if that helps.

Thanks

[Scott Klement]

If you haven't made any customizations in the library, just delete it and restore the new one. (If you have running applications that use HTTPAPI, you'll need to restart those jobs (or at least the activation groups they are running in), otherwise they'll get errors because they're referring to an object that no longer exists.)

If you have made customizations, then restore the new one to a different library, re-make your customizations, and test them. Then use the new library.

There's nothing special about the name 'LIBHTTP', you can call the library whatever you want. That's just a default.

[jtaylor]

Excellent. Thank you

[jtaylor]

I got delayed, and I just now tried the update. I have 1.32 and I'm trying to install 1.45. The install went OK, but I'm getting compile errors trying to recompile existing code (no changes made). The compiles are failing because it can't open a copybook within HTTPAPI.

The issue is line 37 in HTTPAPI_H.RPGLE. 1.32 has the library hard-coded, while 1.45 does not.

1.32 /copy LIBHTTP/qrpglesrc,config_h
1.45 /copy *LIBL/qrpglesrc,config_h


It looks like a simple matter of changing that *LIBL. Any known gotchas with doing that?


Thanks

[Scott Klement]

When you install HTTPAPI, you run a program with CALL INSTALL. One of the screens looks like this:

httplibs.png (5.17 KiB) Viewed 2620 times

The reason it's different for you is not because of any change in the product, but because you answered these questions differently. It appears that when you ran INSTALL for 1.32 you set the library name for source to LIBHTTP, but when you ran it for 1.45, you used *LIBL.

Most people prefer *LIBL rather than a hard-coded library -- but, it's up to you.

[jtaylor]

Perfect! I have 1.45 running now. Thank you