IBM Data Server Manager and Db2 11 for z/OS

Daniel Luksetich

IBM Data Server Manager and Db2 11 for z/OS
Anyone having success with Data Server Manager and Db2 for z/OS? It
seems to crash any time I try to set it up for tuning. Also, it seems to
be depending upon a lot of stored procedures, many of which we are not
allowed to run, or have not been configured by our SYSADM team. I am
testing Data Server Manager due to the fact that Data Studio does not
work well over a secure connection. I'm still trying to work through
that problem, but IBM is reluctant to fix Data Studio. If DSM is the
replacement for Data Studio where are all the features?

right now I'm just getting started with DSM, so maybe I have a lot to
learn, but here is what I do with Data Studio:
-build models (Db2 and SQL Server)
-reverse engineer models (Db2 and SQL Server)
-manage databases
-run queries
-build and deploy stored procedures
-read XML documents
-query tuning
-generate DDL
-test stored procedures
-send information in support of query tuning PMR's to IBM

Can all this be done with DSM? I have thus far run some queries with
DSM, but that's it. It's user interface leaves a lot to be desired. I'd
appreciate any comments and feedback.

Thanks,
Dan

James Campbell

IBM Data Server Manager and Db2 11 for z/OS
(in response to Daniel Luksetich)
I looked at the stored procedures some time ago. They are supplied with
- Tools Base for z/OS V1.5 - FMID HAKP150. Not with any other version / release
- various DB2 solution packs - FMID HAKP160

If you have either of these
https://www.ibm.com/support/knowledgecenter/SSS8US_1.5.0/dyx/dyx_landing.html
is as good a starting point for installation as any. Except that SFECLOAD only needs to be
authorised if you are using another tool that supplies and requires it.

No, I haven't tried to use it for tuning.

James Campbell


On 4 Jan 2018 at 6:33, Daniel Luksetich wrote:

> Anyone having success with Data Server Manager and Db2 for z/OS? It
> seems to crash any time I try to set it up for tuning. Also, it seems to
> be depending upon a lot of stored procedures, many of which we are not
> allowed to run, or have not been configured by our SYSADM team.

<rest sniped>