How to find patch history for IBM InfoSphere DataStage and Information Server

-

Question

Where can I find the history of patches applied to my DataStage or Information Server installation?

Answer

Customers often need to know the history of patches that have been applied to their DataStage or Information Server installations.

For 7.5.x versions of DataStage, there is not a required place where patch history is kept. However, there is a customary default location, namely $DSHOME/../../patches that is referenced in the patch installation notes for most 7.5 patches. So this is the first place to look for the patch history of your 7.5.x system. You should be aware that this is not guaranteed to have all of the patches that have been applied to your system. You should confirm this with your DataStage administrator.

For 8.x versions of DataStage / Information Server, patch history is retained in the <History> section of the Version.xml file. Every 8.x version maintains a Version.xml file that includes information about what modules have been installed and other relevant information including what patches and fix packs have been applied. This file exists on any machine where DataStage / Information Server is installed, including servers and clients. There is one case where you may not have a Version.xml file, and that is any 8.0 system where no patches or fix packs have been applied. Then there will not be a Version.xml file, and that will tell you that no patches or fix packs have been applied. In all other cases, the Version.xml file will exist and will have a history of patches and fix packs applied, and will also indicate whether the patch was successfully applied.

The default locations for IS 8.x versions are:

Unix/Linux:

/opt/IBM/InformationServer/Version.xml

Windows (including clients):

C:\IBM\Information Server\version.xml





Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more