relating module prefixes to components and products
john gilmore
http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.ieav200/bpfind.htm
(As usual, watch the wrap.)
and printed in the MVS DG there is a table that relates module prefixes to components and products; and among the many instances of module prefixes listed there that begin with 'IKJ' all appear to be related to TSO.
This table answers most questions of the form
What is the module with prefix '<three characters>' a part of?
and even longer 'prefixes' may well appear in it.
John Gilmore Ashland, MA 01721-1817 USA
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Itschak Mugzach
differentiate IBM code form application code. . Now, the are some new ones
starting with 'S'.
Itschak
Tony Harminc
> Interesting. IBM used to use product prefixes stating with A to J to
> differentiate IBM code form application code. . Now, the are some new ones
> starting with 'S'.
If IBM is using those prefixes, it would seem to be a violation of the
SMP/E Packaging Rules, which clearly says that:
--------------------------
A-I When used by IBM, all three characters of the prefix are generally
alphabetic (with some exceptions). Can be used by non-IBM products
only if the prefix includes at least one numeric or national
character.
J-Z Available for non-IBM products. The prefix can be all alphabetic
or can include numeric or national characters. Note: ZZZ is
reserved for the first three characters of generic USERMODs written by
customers.
Q Used by AS/400
--------------------------
But since IBM makes the rules, presumably they can gratuitously break
them. Indeed there are already cases where they have used prefixes in
e.g. the /usr/lpp file system there are /java, /ldap, /pli, and even
/smp - all of which are rightly in the non-IBM range.One wonders if
they have been properly registered with the Powers That Be.
As for those "S" entries in the Diagnosis Reference, I think they are
remnants of "sysgen" macros, which were SGxxxxxx long before SMP or
packaging rules existed.
Tony H.
Bill Fairchild
them.
Or they can decide how to parse their own rules. E.g., "J-Z Available for non-IBM products" does not say that IBM cannot use these. An unambiguous rule to that effect would be worded thus: "J-Z Available only for non-IBM products.
Bill Fairchild
Software Developer
Rocket Software
275 Grove Street * Newton, MA 02466-2272 * USA
Tel: +1.617.614.4503 * Mobile: +1.508.341.1715
Email: bi...@mainstar.com
Web: www.rocketsoftware.com
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On Behalf Of Tony Harminc
Sent: Wednesday, November 25, 2009 1:58 PM
To: IBM-...@bama.ua.edu
Subject: Re: relating module prefixes to components and products
2009/11/25 Itschak Mugzach <imug...@gmail.com>:
> Interesting. IBM used to use product prefixes stating with A to J to
> differentiate IBM code form application code. . Now, the are some new ones
> starting with 'S'.
If IBM is using those prefixes, it would seem to be a violation of the
SMP/E Packaging Rules, which clearly says that:
--------------------------
A-I When used by IBM, all three characters of the prefix are generally
alphabetic (with some exceptions). Can be used by non-IBM products
only if the prefix includes at least one numeric or national
character.
J-Z Available for non-IBM products. The prefix can be all alphabetic
or can include numeric or national characters. Note: ZZZ is
reserved for the first three characters of generic USERMODs written by
customers.
Q Used by AS/400
--------------------------
But since IBM makes the rules, presumably they can gratuitously break
them.
Tony H.
Peter Relson
What component / product uses "S"?
As other appends have mentioned, it was never "A-J", it was, and is,
"A-I".
Certainly there are protocols, such as ENQ names, where "SYS" has a
special meaning. And there are certain protocols where for industry
standards names outside the normal name scope need to be named. But I
would be surprised if there is an IBM component or product that feels free
to use a 3-char prefix beginning with "S". So feel free to surprise me.
Peter Relson
z/OS Core Technology Design
Scott Fagen
>OK, I'll bite.
>
>What component / product uses "S"?
Has everything from Candle, Tivoli, Consul, and re-branded from Rocket been
"re-modularized" to follow the IBM standard?
Scott Fagen
Chief Architect
CA Mainframe Products
Peter Relson
been
>"re-modularized" to follow the IBM standard?
I hadn't thought of that, and I suspect (as do you) that the answer is
"no".
I'm going to pretend that that case does not count, any more than the
names for a lot of the old interfaces macros count. Grandfathering wins.,
But perhaps that was the case being thought of.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
Pinnacle
From: "Peter Relson" <rel...@US.IBM.COM>
Newsgroups: bit.listserv.ibm-main
Sent: Saturday, November 28, 2009 9:07 AM
Subject: Re: relating module prefixes to components and products
> >Has everything from Candle, Tivoli, Consul, and re-branded from Rocket
> been
>>"re-modularized" to follow the IBM standard?
>
> I hadn't thought of that, and I suspect (as do you) that the answer is
> "no".
>
> I'm going to pretend that that case does not count, any more than the
> names for a lot of the old interfaces macros count. Grandfathering wins.,
> But perhaps that was the case being thought of.
>
> Peter Relson
> z/OS Core Technology Design
>
There was the well-publicized collision between JCLCHECK and FileManager
both starting with CAZ. I never heard the resolution. Apparently JCLCHECK
had never been officially registrated with IBM.
Regards,
Tom Conley
P S
> There was the well-publicized collision between JCLCHECK and FileManager
> both starting with CAZ. I never heard the resolution. Apparently JCLCHECK
> had never been officially registrated with IBM.
>
"Registrated"?? Ouch.
Chase, John
> From: IBM Mainframe Discussion List On Behalf Of Pinnacle
>
> ----- Original Message -----
> From: "Peter Relson"
>
Rocket
> > been
> >>"re-modularized" to follow the IBM standard?
> >
> > I hadn't thought of that, and I suspect (as do you) that the answer
is
> > "no".
> >
> > I'm going to pretend that that case does not count, any more than
the
> > names for a lot of the old interfaces macros count. Grandfathering
wins.,
> > But perhaps that was the case being thought of.
> >
> > Peter Relson
> > z/OS Core Technology Design
> >
>
> There was the well-publicized collision between JCLCHECK and
FileManager
> both starting with CAZ. I never heard the resolution. Apparently
JCLCHECK
> had never been officially registrated with IBM.
CAZ belongs to Application Performance Analyzer now. File Manager has
FMN (unintentionally intuitive?).
-jc-
Pinnacle
From: "Chase, John" <jch...@USSCO.COM>
Newsgroups: bit.listserv.ibm-main
Sent: Saturday, November 28, 2009 6:09 PM
Subject: Re: relating module prefixes to components and products
Duh, it was APA. So it's still CAZ? Interesting.
Tom