This question assumes importance if a customer wants to get a one-off for resolving a newly discovered bug. This in turns requires identifying the one-offs present in the current environment so that the code fixes in the new one-offs take into account the existing one-offs. Another reason is, the customer may want to create an identical environment (with respect to binaries only) and downloading the SharePlex build may not be enough as it needs to be updated with the one-off binaries, if they are present in the existing environment. Yet another reason may be, the customer has encountered a bug and we need to identify the current one-offs that are supposed to have addressed the bug but there are other manifestations of the bug which are not addressed in the present one-off. There can be many other reasons. The script sp-bininfo located in /proddir/.app-modules (where proddir refers to Product Directory of SharePlex) is run to get the details of the binaries present in one’s environment and these details also include the one-offs.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.