@bama.ua.edu] On Behalf Of
Ford Prefect
Sent: Saturday, 07 January 2012 13:53
To: IBM-MAIN@bama.ua.edu
Subject: Re: USS Education (Was: Calling all experts on SMFPRMxx SUBSYS)
Disturbing.
On Fri, Jan 6, 2012 at 9:56 AM, Chris Mason chrisma...@belgacom.net wrote
Did you see idle BPXASs having the service class you assigned via WLM
subsystem OMVS? I have only ever seen BPXASs having SRVCLASS=SYSSTC and
WORKLOAD=SYSTEM (but I had never cared to explicitly classify BPXAS
neither under OMVS nor under STC).
I'd expect to find BPXOINIT having SRVCLASS=SYSTEM
Disturbing.
On Fri, Jan 6, 2012 at 9:56 AM, Chris Mason chrisma...@belgacom.net wrote:
Barbara
You know how ignorant I am about USS, don't you?
Well, no, I didn't at all but, since you mention it, perhaps I can help,
assuming you would like to be educated in USS.
These days you most
Barbara Nitz nitz-...@gmx.net wrote in message
news:5715402586594249.wa.nitzibmgmx@bama.ua.edu...
Just to add my speculations to this, too:
For some reason they have excluded SMF records with that subsys.
From the other posts, it is a user-defined SMF type number. The reason
for
Barbara Nitz wrote:
I cannot say with surety. I would have said an unequivocal yes before this
discussion, but as Kees pointed out, anyone can report themselves as an SMF
subsystem. And as Rob showed us, the one who writes the SMF record via SMFEWTM
specifies the subsystem it is written for.
Vernooij, CP - SPLXM wrote:
If an application needs one of them [ ... subsystem ...] like in IEFSSN, you
need to specify that one,
It depends on the product. I know of some third party products which are using
'hooks' to establish a subsystem, for them there is no need to bother with
Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote in message
news:5632376965579273.wa.elardus.engelbrechtsita.co...@bama.ua.edu...
Barbara Nitz wrote:
I cannot say with surety. I would have said an unequivocal yes before
this discussion, but as Kees pointed out, anyone can report
Vernooij, CP - SPLXM wrote:
Yes, we do this in IEFU83 and IEFU84 for the SYSID field.
Thanks very much for your kind reply. It is much appreciated. :-)
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff
You know how ignorant I am about USS, don't you?
Some enlightenment desired? If not hit DEL :-)
I went under the assumption that if it has the word INIT in the
jobname, it must be idle.
This only works with JESx initiators since that JCL PROC is called INIT
and it is started via S INIT,.
Can a SMF exit overwrite and change that subsystem name (or any
field)
in a SMF record as passed on and send these changed SMF records on to be
captured by SMF subsystem and stored on a SYS1.MANx dataset later?
Yes, we do this in IEFU83 and IEFU84 for the SYSID field.
You say that you change
Hunkeler Peter , KIUP 4 peter.hunke...@credit-suisse.com wrote in
message
news:dc74548a025aff4a85f46926802a9b230779e...@chsa1035.share.beluni.net
...
Can a SMF exit overwrite and change that subsystem name (or any
field)
in a SMF record as passed on and send these changed SMF records on to
be
records contain SM100SSI, the DB2 subsystem
name.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of Hunkeler Peter (KIUP 4)
Sent: Friday, January 06, 2012 5:44 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
2012 13:44
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
Can a SMF exit overwrite and change that subsystem name (or any
field)
in a SMF record as passed on and send these changed SMF records on to be
captured by SMF subsystem and stored on a SYS1.MANx dataset later
Barbara
You know how ignorant I am about USS, don't you?
Well, no, I didn't at all but, since you mention it, perhaps I can help,
assuming you would like to be educated in USS.
These days you most probably use USS as described in Chapter 11, Accessing
remote hosts using Telnet of the z/OS
Offset x'12' in the standard SMF record header contains the 4-byte
subsystem name.
Arrgghhh. stupid me. I did look up in the SMF manual before posting
but missed the fact that the headers differ for records with and without
subtypes. Sorry for the noise.
Thanks for setting me right.
--
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Charles Mills
Sent: 06 January 2012 14:43
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
The subsystem name as we have been talking about it here is not part
experts on SMFPRMxx SUBSYS
Offset x'12' in the standard SMF record header contains the 4-byte subsystem
name.
The IEFU8x exits will be able to change this value - however obviously some
care and attention is needed not to confuse the eventual consumer of the
data.
Also - be aware that other software
written as .
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of Rob Scott
Sent: Friday, January 06, 2012 7:48 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
Charles
The SID is at offset X'0E
Charles Mills wrote:
DB2 uses the subtype format as it uses the subsystem ID field but
AFAIK
does not use the subtype field (documents it as reserved). Seems to be
fairly consistently written as .
DB2 doesn't have subtypes because it has its own thing - called an IFCID.
The IFCID is in
Hunkeler Peter , KIUP 4 peter.hunke...@credit-suisse.com wrote in
message
news:dc74548a025aff4a85f46926802a9b230779d...@chsa1035.share.beluni.net
...
The SMF SUBSYS types *I* am aware of are JESx, STC, TSO, OMVS, ASCH.
That's it.
There are three, let's say kinds of address spaces: STC, TSO,
You probably meant idle BPXAS here. Furthermore, any non-idle BPXAS,
i.e. one that is currently hosting a forked process, also is of SMF type
OMVS and still shows up as STCn.
I wasn't sure about BPXAS. But no, I meant BPXOINIT. For the simple reason that
there's some sort of type in the
You probably meant idle BPXAS here. Furthermore, any non-idle BPXAS,
i.e. one that is currently hosting a forked process, also is of SMF
type
OMVS and still shows up as STCn.
I wasn't sure about BPXAS. But no, I meant BPXOINIT.
I'm puzzled. There is only one BPXOINIT per system. BPXOINIT is
Topical: Just yesterday a colleague and I were discussing a user-defined
(not SSI) subsystem - SILO - that a customer appears to have. You can
guess (as I did) the origin of the subsystem. Anyone know anything about
the subsystem? For some reason they have excluded SMF records with that
: +1.617.614.2305
Email: rsc...@rs.com
Web: www.rocketsoftware.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Martin Packer
Sent: 05 January 2012 11:06
To: IBM-MAIN@bama.ua.edu
Subject: Was: Calling all experts on SMFPRMxx SUBSYS - How
Martin Packer martin_pac...@uk.ibm.com wrote in message
news:of81a0b4c6.95d34f88-on8025797c.002b1874-8025797c.003d0...@uk.ibm.c
om...
Topical: Just yesterday a colleague and I were discussing a
user-defined
(not SSI) subsystem - SILO - that a customer appears to have. You can
guess (as I did)
On Thu, 5 Jan 2012 11:06:25 +, Martin Packer martin_pac...@uk.ibm.com
wrote:
Topical: Just yesterday a colleague and I were discussing a user-defined
(not SSI) subsystem - SILO - that a customer appears to have. You can
guess (as I did) the origin of the subsystem. Anyone know anything about
In 01b201cccb2d$0cf4abf0$26de03d0$@mcn.org, on 01/04/2012
at 02:06 PM, Charles Mills charl...@mcn.org said:
I would assume that the writing of SMF Type 30 records would be
controlled by SUBSYS(TSO and SUBSYS(JESn statements -- is that
correct?
There are additional SUBSYS values and Type 30
Thanks much, Barbara. Follow-ups in-line.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of Barbara Nitz
Sent: Wednesday, January 04, 2012 9:05 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
Charles
I'm puzzled. There is only one BPXOINIT per system. BPXOINIT is started
by STC OMVS during initialization and becomes PID=1 of the UNIX system.
I would not consider this AS to be idle, since for me (in this
context) the term idle relates to an initiator AS that is waiting for
work.
You know how
So, is it true that for SMFPRMxx SUBSYS(xxx,(... the only useful xxx are
the five or six types listed above? I say useful rather than valid
because I don't mean that SMF would necessarily generate an error for
SUBSYS(FOO( -- it might, I just don't care at this moment -- but it would
not be
Just to add my speculations to this, too:
For some reason they have excluded SMF records with that subsys.
From the other posts, it is a user-defined SMF type number. The reason for
exclusion is probably just that these types didn't exist when the TYPE
statement was written in SMFPRM. Are
I assume this august group is filled with people who have forgotten more
about SMFPRMxx than I will ever know.
I am trying to determine the exact relationship between various SUBSYS(
specifications and the writing of specific SMF record types. (And yes, I
know there are OTHER variables involved,
I assume this august group is filled with people who have forgotten more
about SMFPRMxx than I will ever know.
I am trying to determine the exact relationship between various SUBSYS(
specifications and the writing of specific SMF record types. (And yes, I
know there are OTHER variables
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Lizette Koehler
Sent: Wednesday, January 04, 2012 3:41 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Calling all experts on SMFPRMxx SUBSYS
I assume this august group is filled with people who have forgotten
more about
Charles,
What I don't understand is the exact mapping of SUBSYS names to record-level
functionality.
If *I* understand you right, then you're confusing SUBSYS as indicated in
SMFPRM and a subsystem defined to the SSI.
The SMF SUBSYS types *I* am aware of are JESx, STC, TSO, OMVS, ASCH. That's
The SMF SUBSYS types *I* am aware of are JESx, STC, TSO, OMVS, ASCH.
That's it.
There are three, let's say kinds of address spaces: STC, TSO, and
Initiator address spaces. The latter type comprises JESx initiators,
APPC initiators, and z/OS UNIX initiators, which all run the MVS
initiator module
36 matches
Mail list logo
