Re: IBM Component Codes. was: Re: IBM customer anchor

Both of those are macros, modules, source code and panels, which are also very important, but that original question and subject (for me) was about message prefixes. Brian -- For IBM-MAIN subscribe / signoff / archive access

Re: IBM customer anchor

Peter sent me the email address. I think we probably were originally assigned back in the 1980's (or 90's), but I figured it would not hurt to ask them if "SYZ" was assigned to us. I found some information in some manuals, but that seems to be related to naming your modules, not the messages

Re: IBM customer anchor

Brian, I wasn't aware either, we go through Partnerworld. Then someone, not sure who, assigned us (IDMWORKS) the three character message/module prefix. The I asked IBM for our customer anchor, Peter kindly responded with it. Regards, Scott On Sun, Jul 2, 2017 at 11:57 AM Tony Harminc

Re: IBM customer anchor

On 2 July 2017 at 10:15, Charles Mills wrote: > I think you would risk trademark issues as well as name collision issues if > you used iBM. And yes, IBM claims the entire space AAA-I99 or perhaps J99, > including IBM. In fact the specific prefix IBM was assigned 30+ years ago

Re: IBM customer anchor

Subject: Re: IBM customer anchor On Fri, 30 Jun 2017 07:37:59 -0400, Peter Relson wrote: >>Are you saying we are better off, using our IBM assigned message >>prefix ..which is MDI ...as part of our Token we use ? > >Yes, definitely. > How should this apply to items in th

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 :

Re: IBM customer anchor

On Fri, 30 Jun 2017 07:37:59 -0400, Peter Relson wrote: >>Are you saying we are better off, using our IBM assigned message prefix >>..which is MDI ...as part of our Token we use ? > >Yes, definitely. > How should this apply to items in the UNIX filesystem? I know there are pathnames like

Re: IBM customer anchor

On Sat, 1 Jul 2017 22:00:14 -0500, 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

Re: IBM customer anchor

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

Re: IBM customer anchor

>If my company has a 3 character prefix reserved with >the VSE group, does that cross into z/OS? I do not know what "reserved with the VSE group" translates to. My guess woult be that the assignment of prefix is operating system agnostic. And that there is only one reservation process. But

Re: IBM customer anchor

The right thing to do is obvious. The major problem, though, is that the right thing being done is on the honor system. Obviously, some of the biggest players in the arena are antisocial enough to believe that being honorable and doing what's right are not applicable to them. > On Jun 24,

Re: IBM customer anchor

Peter, Thank you for your help much appreciated. Scott IDMWORKS On Fri, Jun 30, 2017 at 7:44 AM, Tony Thigpen wrote: > Peter, > > Stupid question. If my company has a 3 character prefix reserved with the > VSE group, does that cross into z/OS? Or, do we need to reserve one

Re: IBM customer anchor

Peter, Stupid question. If my company has a 3 character prefix reserved with the VSE group, does that cross into z/OS? Or, do we need to reserve one though the z/OS side also. (We are considering porting one of our products to z/OS.) Tony Thigpen Peter Relson wrote on 06/30/2017 07:37 AM:

Re: IBM customer anchor

>Are you saying we are better off, using our IBM assigned message prefix >..which is MDI ...as part of our Token we use ? Yes, definitely. When name collisions would be a problem, the best approach is to begin with "your" prefix. In general, names beginning with A-I and SYS are reserved for

Re: IBM customer anchor

On Thu, 29 Jun 2017 23:02:22 +, scott Ford wrote: > >Are you saying we are better off, using our IBM assigned message prefix >..which is MDI ...as part of our Token we use ? > I believe he was more specific: On Mon, 26 Jun 2017 08:28:06 -0400, Peter Relson wrote: >... it has always been

Re: IBM customer anchor

Peter, Are you saying we are better off, using our IBM assigned message prefix ..which is MDI ...as part of our Token we use ? Scott On Wed, Jun 28, 2017 at 7:47 AM Peter Relson wrote: > >Yes, I agree, we use IDENTI... > > I would say that that is wholly unacceptable unless

Re: IBM customer anchor

>Yes, I agree, we use IDENTI... I would say that that is wholly unacceptable unless you own the prefix IDE. If IBM creates a token that happens to collide then we may expect and require you to change. Is that likely? No. Is it conceivable? Yes. Some prefixes within the IBM range that had been

Re: IBM customer anchor

Brian, Yes, I agree, we use IDENTI... Scott On Tue, Jun 27, 2017 at 12:42 AM Brian Westerman < brian_wester...@syzygyinc.com> wrote: > With the NAME/TOKEN, it would be pretty hard to accidentally use the same > token name (assuming you give your token a non-generic name). For ours > they all

Re: IBM customer anchor

With the NAME/TOKEN, it would be pretty hard to accidentally use the same token name (assuming you give your token a non-generic name). For ours they all start with "Syzygy_somthing" or "Syz_somethingelse" and since you have 16 bytes to play with you would have to try pretty hard to

Re: IBM customer anchor

>What precludes collisions of name/tokens? >Simply bigger name space? Nothing precludes collisions of anything. This is one big sometimes-happy family among IBM, ISVs, and customers and I think that those who play by the rules tend to be happiest. This is why it has always been recommended

Re: IBM customer anchor

We belong to Partnerworld and I sent a request and Peter responded so we now have an anchor address. Scott On Sat, Jun 24, 2017 at 12:33 AM Brian Westerman < brian_wester...@syzygyinc.com> wrote: > I think it was just a matter of who sent the letter. When it came from a > competitor, they

Re: IBM customer anchor

I think it was just a matter of who sent the letter. When it came from a competitor, they were aggressive, but when it came from a lawyer, especially as it was from a big firm, they gave up fairly quickly. When you think about it though, we really could not force them to do anything, we could

Re: IBM customer anchor

If they register a three letter message prefix with IBM then they are left with 5 characters for individual products/requests. On Thursday, June 22, 2017, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Thu, 22 Jun 2017 01:00:46 -0500, Brian Westerman wrote: > > >I

Re: IBM customer anchor

On 2017-06-22 13:04, Paul Gilmartin wrote: Had CA squatted on their claim before IBM established a registry? IIRC Peter Relson established the registry when he first established the table. -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel:

Re: IBM customer anchor

On Thu, 22 Jun 2017 01:00:46 -0500, Brian Westerman wrote: >I know we had to contact CA and Sterling, as well as Landmark Systems about >using our offset. The only one that gave us a hard time about it was CA, who >told us they "had it first", and then tried both money and threats to have us

Re: IBM customer anchor

I know we had to contact CA and Sterling, as well as Landmark Systems about using our offset. The only one that gave us a hard time about it was CA, who told us they "had it first", and then tried both money and threats to have us give it up and go back and ask for another one. I believe our

Re: IBM customer anchor

On Wed, 21 Jun 2017 08:36:17 -0400, Peter Relson wrote: >>one problem we kept running into was that not everyone >>registered their use with IBM and apparently we had some >>people's favorite offset number, so occasionally we >>would have people step on us. > >If you have any detailed

Re: IBM customer anchor

>one problem we kept running into was that not everyone >registered their use with IBM and apparently we had some >people's favorite offset number, so occasionally we >would have people step on us. If you have any detailed information on this (such as anything that might identify the

Re: IBM customer anchor

into that problem, fortunately. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Brian Westerman > Sent: Wednesday, June 14, 2017 5:49 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re:

Re: IBM customer anchor

AIN@LISTSERV.UA.EDU Subject: Re: IBM customer anchor We have several products on the market and while we exclusively used to use the anchor when we start(ed) our Syzygy subsystem, it's now just one of several way we keep track of things. We still support it being there (after all we "own" the

Re: IBM customer anchor

We have several products on the market and while we exclusively used to use the anchor when we start(ed) our Syzygy subsystem, it's now just one of several way we keep track of things. We still support it being there (after all we "own" the registration of the slot), but we mostly use the

Re: IBM customer anchor

On Wed, Jun 14, 2017 at 10:25 AM, Charles Mills wrote: > NAME/TOKEN would be a lot more flexible and would not require IBM's > involvement but I have to think the code path for the anchor is a heck of a > lot shorter, at least not counting any validation of version, length,

Re: IBM customer anchor

[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, June 13, 2017 6:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM customer anchor On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills <charl...@mcn.org> wrote: > As a user of the word, you really, really want to think abo

Re: IBM customer anchor

Steve, This is exactly as Charles stated we want to do. Scott On Tue, Jun 13, 2017 at 10:51 PM Steve Thompson wrote: > On 06/13/2017 09:06 PM, John McKown wrote: > > On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: > > > >> As a user of the word, you

Re: IBM customer anchor

On 06/13/2017 09:06 PM, John McKown wrote: On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: As a user of the word, you really, really want to think about upward compatibility. Don't store the address of your product's anchor table there. Assume you will someday have

Re: IBM customer anchor

On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: > As a user of the word, you really, really want to think about upward > compatibility. Don't store the address of your product's anchor table > there. Assume you will someday have multiple products. You would want to >

Re: IBM customer anchor

become corrupted. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Thompson Sent: Tuesday, June 13, 2017 1:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM customer anchor On 06/13/2017 08:35 AM, scott Ford wrote: >

Re: IBM customer anchor

On 06/13/2017 08:35 AM, scott Ford wrote: All: I have a question about something called 'customer anchor table entry' . My colleague said IBM can provide this entry to a ISV like use so we can place an address there for routines. I think it's like a vector address . Has anyone heard of this ?

Re: IBM customer anchor

Yep! That's what we did. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Tuesday, June 13, 2017 5:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM customer anchor Recently came across this too

Re: IBM customer anchor

Recently came across this too. In CBT841 files: "CONTACT PETER RELSON, rel...@us.ibm.com FOR YOUR OWN OFFSET IN THE CUSTOMER ANCHOR TABLE. ONCE YOU HAVE RECEIVED YOUR ASSIGNED VALUE MODIFY.." Also, in the same CBT: "A possible address off the Customer Anchor Table, X'CC' off the ECVT, could

IBM customer anchor

All: I have a question about something called 'customer anchor table entry' . My colleague said IBM can provide this entry to a ISV like use so we can place an address there for routines. I think it's like a vector address . Has anyone heard of this ? -- Regards, *IDMWORKS * Scott Ford