Viewing a list of activated IBM InfoSphere DataStage editions and feature packs

-
Viewing a list of activated IBM InfoSphere DataStage editions and feature packs
Run the LicensingServiceAdmin command line tool to list the activated IBM® InfoSphere® DataStage® editions and feature packs within your suite.
Before you begin

You must have at least Suite User authority.

Procedure
  1. Log in to the computer on which the LicensingServiceAdmin tool is installed:
    • If you have implemented IBM WebSphere® Application Server clustering within your installation, log in to the computer that hosts the WebSphere Application Server Deployment Manager.
    • If you have not implement clustering, log in to the services tier computer.
In either case, use an account that has execution permission for the tools in the ASBServer/bin directory, as described in the next step.
  1. Change to the ASBServer/bin directory within the directory in which IBM InfoSphere Information Server is installed. For example:
    •  cd /opt/IBM/InformationServer/ASBServer/bin
    •  cd C:\IBM\InformationServer\ASBServer\bin
  2. Run the LicensingServiceAdmin command with the -list_features option.
Instead of the -user and -password options, you can provide a credentials file with the -authfile option. If you do not provide a user, password, or credentials file, you are prompted for a user ID and password.
./LicensingServiceAdmin.sh -user iauser -password iapswd -list_features
LicensingServiceAdmin -user iauser -password iapswd -list_features
In the command,
    • iauser is the name of a user that has suite user authority.
    • iapswd is the user password.
The command lists the features that are activated. Deactivated features are not listed. For example:
DS,DSServer,DSMVS,BalOpt,SAS,QS
Enabled components:
IBM InfoSphere DataStage
IBM InfoSphere DataStage Server
IBM InfoSphere DataStage MVS Edition
IBM InfoSphere DataStage Balanced Optimization
IBM InfoSphere DataStage Pack for SAS
IBM InfoSphere QualityStage
DataStage and QualityStage Administrator
DataStage and QualityStage Director
DataStage and QualityStage Designer
Enabled features:
job-type = DataStage
job-type = QualityStage
licensed-feature = BAL_OPT
licensed-feature = SAS_PACK
canvas = Parallel
canvas = Server
canvas = MVS
Since IBM InfoSphere QualityStage® shares the InfoSphere DataStage components and client applications, it is also listed as one of the activated features if InfoSphere QualityStage is installed. Even though it is listed as one of the features, InfoSphere QualityStage cannot be activated or deactivated with the LicensingServiceAdmin tool. To activate InfoSphere QualityStage, install InfoSphere QualityStage by using the installation program. To deactivateInfoSphere QualityStage, uninstall InfoSphere QualityStage by using the software removal program.
The list of enabled InfoSphere DataStage and InfoSphere QualityStage client applications is also shown. All three applications are enabled when InfoSphere QualityStage or any version of InfoSphere DataStage is installed. If IBM InfoSphere Information Analyzer is installed without InfoSphere DataStage or InfoSphere QualityStage, then only theInfoSphere DataStage and QualityStage client is enabled.



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