How to get a list of the db2 subsystems on a S/390 system?

[clemente.biondo]

Hi
all,
I'd like to know if there is a way (via JCL / TSO command / filesystem
structure
or something other) to get the list of all the db2 subsystems
installed on a generic
s/390 system.
For example, in the system I have acces one can guess this information
by
the presence of datasets of the form:
XXXX.ARCHLOG1.D06217.T0949376.B0050465
XXXX.DSNDBD.<A_DB_NAME>.TEMPTS.I0001.A001
XXXX.LOGCOPY1.DS01
where XXXX is the db2 subsystem, but I suppose that this is not a
general
rule (I suppose that the DBA can install the logs everywhere he
prefers
and can also change the prefix of those files...)
I need this information in order to ease the installation process of
an
open source application I'm writing (not everyone that installs it
know
what is a subsystem is).

By the way... what is the more generic way to refer to a system that
runs an
IBM z/OS Communications Server and have DB2 installed?
Is an s/390 system, an MVS, an OS390 or what?

Thank you in advance.
Clemente Biondo.

[Jeroen van den Broek]

On May 8, 1:36 pm, [e-mail] wrote:

Hi
all,
I'd like to know if there is a way (via JCL / TSO command / filesystem
structure
or something other) to get the list of all the db2 subsystems
installed on a generic
s/390 system.
For example, in the system I have acces one can guess this information
by
the presence of datasets of the form:
XXXX.ARCHLOG1.D06217.T0949376.B0050465
XXXX.DSNDBD.<A_DB_NAME>.TEMPTS.I0001.A001
XXXX.LOGCOPY1.DS01
where XXXX is the db2 subsystem, but I suppose that this is not a
general
rule (I suppose that the DBA can install the logs everywhere he
prefers
and can also change the prefix of those files...)
I need this information in order to ease the installation process of
an
open source application I'm writing (not everyone that installs it
know
what is a subsystem is).

By the way... what is the more generic way to refer to a system that
runs an
IBM z/OS Communications Server and have DB2 installed?
Is an s/390 system, an MVS, an OS390 or what?

Thank you in advance.
Clemente Biondo.

Every DB2 subsystem has at least 3 address spaces associated with it,
the names of which all start with the subsystem-id (SSID):
<SSID>MSTR = system services address space
<SSID>DBM1 = database services address space
<SSID>DIST = DDF (distributed data facility) address space

(next to these, you might have others, like the Stored Procedures
address space and the IRLM (Integrated Resource Lock Manager) address
space, but naming for these is not fixed)

You should be able to identify your SSID's via SDSF's "Status
Display" (option ST on SDSF's Primary Option Menu).
Use the following subcommands to show the various types of fixed
address spaces:
SELECT *MSTR
SELECT *DBM1
SELECT *DIST
from which you can deduct your SSID's.

Regarding your question on s/390, MVS, OS390 and such:

_Hardware_ used to be called S/390 (and S/370, S/360 before that), is
now called zSeries (containing a number of different machines like
z800, z890, z900, z990, z9).
See: http://en.wikipedia.org/wiki/ZSeries
The Operating System used to be called MVS, which via many flavors
evolved into OS/390 and now has become z/OS.
See: http://en.wikipedia.org/wiki/Z/OS

HTH

--
Jeroen

[Clemente Biondo]

Thank you for your prompt and professional answer to my questions.
Unfortunately SDSF is not an option, I am limited to a vt100 terminal
emulator so i can't use SDSF or ISPF
but only tso commands and tso status command does not support
wildcards (what a shame!), but thank you
anyway.

[Knut Stolze]

Clemente Biondo wrote:

Thank you for your prompt and professional answer to my questions.
Unfortunately SDSF is not an option, I am limited to a vt100 terminal
emulator so i can't use SDSF or ISPF
but only tso commands and tso status command does not support
wildcards (what a shame!), but thank you

can you access the MVS console and issue an "d a,l"? That would also give
you the list of started tasks, including the 3 (or 4) mentioned DB2 address
spaces.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[James Campbell]

A couple of points:
- you can't rely on *MSTR being DB2, MQ also uses them
- you can't rely on *DDF, not all DB2 subsystems have communications.
If your package requires communications, then this will be available.
- the only one that you can rely on is *DBM1

It is possible to run an SDSF session in a batch job and in native TSO.
But this will only tell you which ones are active. You'd need to look
at the SSVT to see which one are "installed".

Using a VT100 on an MVS type system is like using a teletype on a Unix
system. Can you get something like s3270 working (part of x3270) to do
the wrapping?

James Campbell

Jeroen van den Broek <nl****@baasbovenbaas.demon.nlwrote in
news:11**********************@p77g2000hsh.googlegr oups.com:

On May 8, 1:36 pm, [e-mail] wrote:

>Hi
all,
I'd like to know if there is a way (via JCL / TSO command /

filesystem

>structure
or something other) to get the list of all the db2 subsystems
installed on a generic
s/390 system.
For example, in the system I have acces one can guess this

information

>by
the presence of datasets of the form:
XXXX.ARCHLOG1.D06217.T0949376.B0050465
XXXX.DSNDBD.<A_DB_NAME>.TEMPTS.I0001.A001
XXXX.LOGCOPY1.DS01
where XXXX is the db2 subsystem, but I suppose that this is not a
general
rule (I suppose that the DBA can install the logs everywhere he
prefers
and can also change the prefix of those files...)
I need this information in order to ease the installation process of
an
open source application I'm writing (not everyone that installs it
know
what is a subsystem is).

By the way... what is the more generic way to refer to a system that
runs an
IBM z/OS Communications Server and have DB2 installed?
Is an s/390 system, an MVS, an OS390 or what?

Thank you in advance.
Clemente Biondo.

Every DB2 subsystem has at least 3 address spaces associated with it,
the names of which all start with the subsystem-id (SSID):
<SSID>MSTR = system services address space
<SSID>DBM1 = database services address space
<SSID>DIST = DDF (distributed data facility) address space

(next to these, you might have others, like the Stored Procedures
address space and the IRLM (Integrated Resource Lock Manager) address
space, but naming for these is not fixed)

You should be able to identify your SSID's via SDSF's "Status
Display" (option ST on SDSF's Primary Option Menu).
Use the following subcommands to show the various types of fixed
address spaces:
SELECT *MSTR
SELECT *DBM1
SELECT *DIST
from which you can deduct your SSID's.

Regarding your question on s/390, MVS, OS390 and such:

_Hardware_ used to be called S/390 (and S/370, S/360 before that), is
now called zSeries (containing a number of different machines like
z800, z890, z900, z990, z9).
See: http://en.wikipedia.org/wiki/ZSeries
The Operating System used to be called MVS, which via many flavors
evolved into OS/390 and now has become z/OS.
See: http://en.wikipedia.org/wiki/Z/OS

HTH

--
Jeroen