Ok we found the issue, and it was pretty stupid. The bos.net.tcp.client pre upgrade check-up script was failing, causing the package to fail the install (or just be skipped). What was the cause of it...
I inherited this environment about 3-4 months ago and I don't believe it was set up using IBM best practices. Also the lppchk -f is something I ran yesterday and it returned nothing. I am going to be...
Yes I understood what you wrote, but installp -acFXYd bos.net.tcp.client.6.1.8.19.U bos.net.tcp.client errored out wherein installp -acFXYd /ibm/patch/src bos.net.tcp.client worked on another...
I recently updated one of our servers from 6100-08-05-1415 to 6100-08-06-1441 and the `oslevel -s` is showing the correct version, but when I run an `lppchk -v` I am hit with:
Thanks for the reply. I did get them involved, and their "solution" is to just manually download all of the fixes myself and perform manual patching. Well, in such a big environment I don't think...
Yeah, I had just noticed that in the man page for suma. Unfortunately configuring the http proxy successfully still hasn't yielded the results I need as IBM is complaining that the serial does not...
I tried removing it already to no avail. What I did find is that SUMA no longer allows you to define the HTTP proxy within SUMA itself. I need to use srv_conn to edit it. I'll go ahead and test that...
I am trying to configure an HTTP_PROXY so that suma can reach out beyond our intranet and pull updates from the IBM website. Currently, our suma config is...