Re: IBM Component Codes
Paul, /I wonder what credentials are required for that operation. Perhaps more to "release" a component code than to request one because a prankster coule wreak more mischief by freeing a code in use than by gratuitously having one assigned./ ELEMENT is parsimonious with information about other IDs and ID holders. I would assume that requestor email address, name/title and associated corporate/organisation id are required to align with the details held by IBM. There's a human being at the IBM end, so they can choose to continue a dialog with the requestor until "ELEMENT" is satisfied. The "keeper of the codes" contact address hasn't always been the "departmental" elem...@us.ibm.com. Various individuals were the earlier contacts with the consequent risk of discontinuities as, one way or another, they moved on. From our perspective, for the last 17 years the system has worked well. Cheers, Graeme On 4/07/2017 1:58 PM, Paul Gilmartin wrote: On Tue, 4 Jul 2017 11:46:08 +1000, Graeme Gibson ***@ASE*** wrote: So much time, so little to do! After all the hoo har about component codes, and me even posting helpful links et cetera, it turned out that ASE was holding that SYZ id that Brian W. needed! We don't have a current need for SYZ, so this morning I've asked elem...@us.ibm.com to "release" it so that Brian's request may be met. I wonder what credentials are required for that operation. Perhaps more to "release" a component code than to request one because a prankster coule wreak more mischief by freeing a code in use than by gratuitously having one assigned. And those useful links again: https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80125.htm https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80127.htm Interesting. Some decades ago, I sat in on a meeting in which one ISV who had an assigned code offered to share part of his name space with another who hadn't one. ISV #2 should have been able simply to request his own. Perhaps neither ISV understood the process, or the process hadn't been well defined at that early date, or there may have been a business relationship or lack of one that precluded ISV #2's obtaining one. I believe IBM was then a customer of ISV #1 but not of ISV #2. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IBM Component Codes
So much time, so little to do!
After all the hoo har about component codes, and me even posting helpful links
et cetera, it turned out that ASE was holding that SYZ id that Brian W. needed!
We don't have a current need for SYZ, so this morning I've asked elem...@us.ibm.com to
"release" it so that Brian's request may be met.
And those useful links again:
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80125.htm
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80127.htm
Cheers,
Graeme
--/
Graeme Gibson.Director - enterprise systems services
Australian Systems Engineering Pty. Ltd. ("ASE")
LTXF, OMCS, SLIKSFTP, SLIKSFTM, SLIKZIP //_http://www.ase.com.au_/
<http://www.ase.com.au/>///_http://www.slikzip.com_/ <http://www.slikzip.com/>
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IBM Component Codes. was: Re: IBM customer anchor
Brian, all,
ASE has been using IBM's component code assignment service for many years and
we now have several assigned to us.
Just email "elem...@us.ibm.com" and request the 3-character component code that
you desire. These K.C. entries explain all :
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80125.htm
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.gimb100/gimpkg80127.htm
Cheers,
Graeme Gibson
--/
Graeme Gibson.Director - enterprise systems services
Australian Systems Engineering Pty. Ltd. ("ASE")
cell: 0427 328 937 internat: +61 427 328 937
LTXF, OMCS, SLIKSFTP, SLIKSFTM, SLIKZIP //_http://www.ase.com.au_/
<http://www.ase.com.au/>///_http://www.slikzip.com_/ <http://www.slikzip.com/>
On 2/07/2017 1:00 PM, Brian Westerman wrote:
What IBM assigned message prefix? I never heard that we were supposed to
request one, we have been using SYZpnnnX for almost 30 years and I don't think
I have heard that we ever needed or received an assignment.
Who do I need to speak with to get ours reserved?
Brian
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: k4t4949b (September 2016 refresh of the z/OS 2.2 manuals)
It's possible that someone at IBM has assumed that 7-Zip produces .zip files, which it does not. 7-Zip normally uses the file extension, or type, of ".7z", not '.zip". It's unfortunate, but possibly not inadvertant, that the developers of "7-Zip" chose a product name that suggests they *are* related. Because of the confusion, products that do support the industry-standard .zip file architecture have been pressured by their clients to implement support for .7z files. It's clever. I'm reminded of the cuckoo. Cheers all, Graeme http://www.slikzip.com On 2016/09/18 7:51 AM, John Laubenheimer wrote: To me, this is somewhat bad technique on IBM's part. This doesn't seem to have been documented anywhere, and requiring a 3rd party utility to read the file is not really a good idea. But, 7-Zip works (and is free)! On 2016/09/18 12:41 PM, John Laubenheimer wrote: I guess I should have said that I think that this is a mistake on IBM's part, and not an intentional change. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: So Long, and Thanks For All The Fish
On 2016/01/01 1:47 AM, Shane Ginnane wrote: Shane ... Thought you'd die in the saddle Shane.. :-( Wait.. Is this a New Year resolve gone horribly wrong? :-) In case it's real: the best of wishes to go with those fishes! [Can't imagine the list without your laconic piss-taking mate.] Cheers to all, Graeme -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Passing of Chris Mason reported
'octopuses' is unobjectionable, albeit subliterate; 'octopi' instead of 'octopodes' is not. Ah, I feel the need to re-offend*! Warning to Travellers .. __ For those in Peril near the Sea: Beware the blue-ringed octopii, They're timid, and, I've 'eard, quite shy, But yer a gonna, and you'll soon succumb, If ya let 'em nibble on yer thumb. __ Graeme (grinning!) *first was 9th June 2006 with an (affectionate) illumination by J G on the same day! At 02:41 PM 16/01/2013, you wrote: Shmuel wrote: | De mortui which is perhaps a botched reference to the Latin tag De mortuis nil nisi bonum [dicendum est]. Latin dropouts would do better to refrain from pretention that betrays them into the ridiculous. In other words, get it right or avoid it: 'octopuses' is unobjectionable, albeit subliterate; 'octopi' instead of 'octopodes' is not. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Sad News About Rick Fochtman
Damn.. just found out about Rick F. Knowing him only though the list, I too will miss his presence here. Graeme At 12:46 AM 4/07/2012, you wrote: Rick will be missed. Rich Sandford DB2 Systems Database Administrator System Engineering, Infrastructure Services HealthPlanServices Inc. Tampa, FL 33607-1704 (813) 289-1000 ext. 2931 (800) 237-7767 ext. 2931 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
