Dear support team, We already have opened a requirement (ID145570) but they suggested to address here a new idea with the following text which we already used in the requirement: Description:
This requirement is NOT related to IIB, but to FTM SWI...
When you are in Design View in a data set you don't have access to see what the filters are on the data set or to change them, you need to go into Preview View which could take a long time to load if you have a large data set.
almost 4 years ago
in Cognos Analytics
2
Functionality already exists
Provide the ability to restrict access to specific packages with the Exploration tool, as allowed with with tools, such as Report Studio. Not all packages may be designed for optimal use with Exploration. The users may need access to one package f...
about 5 years ago
in Cognos Analytics
1
Functionality already exists
DB2 REST service should support ‘Using ARRAY data type as INPUT parm in a Native SQLPL’
We have a SQLPL with ARRAY type as INPUT/OUTPUT parm. REST Service allows to ‘create’ as service calling ‘SQLPL with ARRAY type as INPUT parm’ but throws error while calling the same service.
Method :POST
Scheme://HOST[“.” PORT][PATH][“?”QUE...
about 5 years ago
in Db2 for z/OS
1
Functionality already exists
Ability to showcase business lineage for capturing policies, stakeholders, data quality dimensions and corresponding scores, and more
Ability to showcase business lineage for capturing policies, stakeholders, data quality dimensions and corresponding scores, and more - DP: with exact names of servers and server ports via which the data flow occurs
Please validate Spectrum Conductor 2.5.1 for RHEL 7.6 PPCLE Linux Servers
PPCLE RHEL 7.6 is not listed as a supported OS for Spectrum Conductor 2.5.1. We already have condcuctor 2.5.0 running on this version of the OS. The documentation doesnt have reference to this version of OS. Can this be validated.
Graphical difference between 2 versions of the same job
currently we are piloting IIS manager to create packages for deploying datastage code into lhigher environments. However there is no way of identifying quickly what the changes were between an old package and a new one.
almost 8 years ago
in DataStage
0
Functionality already exists