Activating and deactivating IBM InfoSphere DataStage editions and feature packs

-
Activating and deactivating IBM InfoSphere DataStage editions and feature packs
Run the LicensingServiceAdmin command-line tool to change the InfoSphere® DataStage® features that were activated when the services tier was installed. The tool can activate or deactivate InfoSphere DataStage editions and feature packs within your suite if InfoSphere DataStage is installed.

Before you begin
You must have suite administrator authority.
About this task
To activate or deactivate InfoSphere DataStage editions and feature packs in the suite, run the LicensingServiceAdmincommand. Each time you run the command, specify all items that you want to activate. Any editions or feature packs that you do not specify are deactivated by the command. The actual features enabled depend on the combination of editions and features that you specify. For this reason, they must all be provided in a single command.
The tool cannot be used to activate InfoSphere DataStage features if InfoSphere DataStage is not installed. Also the tool cannot be used to deactivate all InfoSphere DataStage features. To remove all InfoSphere DataStage features, removeInfoSphere DataStage by using the IBM® InfoSphere Information Server software removal program.
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 implemented 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 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 -set_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 isadmin -password ispswd -set_features codes
LicensingServiceAdmin -user isadmin -password ispwd -set_features codes
In the command,
    • isadmin is the name of a user that has suite administrator authority.
    • ispwd is the user password.
    • codes is a comma-separated list of codes that specify the editions and feature packs to activate. The following table describes valid feature codes:
      Table 1. Feature codes for LicensingServiceAdmin
      Feature code
      Description
      DS
      Activates IBM InfoSphere DataStage
      DSServer
      Activates IBM InfoSphere DataStage Server
      DSMVS
      Activates IBM InfoSphere DataStage MVS Edition
      SAS
      Activates IBM InfoSphere DataStage Pack for SAS
      BalOpt
      Activates IBM InfoSphere DataStageBalanced Optimization
    • Each time you run the command, specify the feature codes for all editions and feature packs to activate. Include any editions and feature packs that are already activated, that you want to remain activated. Any editions and feature packs that you do not list in the command are deactivated.
    • If you are entitled to both IBM InfoSphere DataStage Server and IBM InfoSphere DataStage from DataStage Server Trade Up, specify the DS feature code only. Do not specify the DSServer feature code.
    • Feature codes are not case sensitive. To include white space within the feature code list, enclose the list in quotation marks.
For example, to activate InfoSphere DataStage, InfoSphere DataStage Balanced Optimization, and the InfoSphere DataStage Pack for SAS, run the following command.
LicensingServiceAdmin -user isadmin -password ispwd -set_features DS,SAS,BalOpt
The command activates the features. In this example, the Mainframe canvas is not enabled within the InfoSphere DataStage client applications. The command then lists the results:
DS,SAS,BalOpt,QS
Enabled components:
IBM InfoSphere DataStage
IBM InfoSphere DataStage Pack for SAS
IBM InfoSphere DataStage Balanced Optimization
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
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