Thanks everyone This is great. Sent from my iPhone
> On Nov 26, 2019, at 5:23 PM, Charles Mills <charl...@mcn.org> wrote: > > Yeah, sorry, I fully admit I have zero real-world experience with UUIDs on Z > -- Japanese or otherwise. And relatively little elsewhere: I have used them > for version signing on Visual Studio -- that's it. > > I would certainly think (hope!) that any reasonable code would be using the > underlying 128-bit binary value, and whether you used abc, ABC or some > mixture would be irrelevant. > > I think the standard is pretty clear: the 128-bit binary value *is* the UUI, > the character string is just a representation thereof, and upper-case hex > values are acceptable. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Cameron Conacher > Sent: Tuesday, November 26, 2019 9:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Question - UUID Approach for Mainframes in Japan > > Thanks Charles, > I was hoping someone with a Japan background would weigh in to say > something along the lines of "have the Consumers upper case the UUID BEFORE > they send it to you" or, "we use DATAPOWER to force upper case on all UUIDs > BEFORE the strings arrive in the mainframe". or something else. > > If a Consumer were to send me a UUID in Lower Case and I return a reply > with the UUID Upper Cased, does this cause some inconsistency on the > Consumer's side of the fence? > I mean, functionally, the UUIDs are the same, but the actual string values > are different. > Does this create issues? > > >> On Mon, Nov 25, 2019 at 4:30 PM Charles Mills <charl...@mcn.org> wrote: >> >> UUID letters as generated are all lower case, so you could translate them >> to upper case without losing any information. >> >> Anything that accepts UUIDs must be prepared to accept upper case, so you >> would be good to go. >> >> -- https://tools.ietf.org/html/rfc4122#section-3 >> >> Charles >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Cameron Conacher >> Sent: Monday, November 25, 2019 3:43 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Question - UUID Approach for Mainframes in Japan >> >> Hello folks, >> I am here with another question today. >> We are a large international company with a market presence in Japan. >> We store our mainframe EBCDIC data for these markets in EBCDIC CodePage >> 930. >> This CodePage has no support for lower case English letters. >> >> If I were a distributed platform and I generated a UTF-8 encoded UUID >> value, and sent this value to the mainframe, it would be then transformed >> into EBCDIC CodePage 930. >> If the UUID were to be generated with any lower case English values ("a", >> "b", "c", "d", "e", or "f") I would expect to encounter some issue at >> conversion/transformation time, since the underlying EBCDIC CodePage cannot >> support the value. >> However, if upper case values were sent instead ("A", "B", "C", "D", "E", >> or "F"), everything would flow and transform politely. >> >> So, my question is whether in the Japan world, mainframe application expect >> Consumers to send only upper cased values, or if an intermediate step prior >> to message transformation occurs close to the mainframe side of things to >> force upper casing of the UUID. >> Or some other technique? >> Similarly, if a UUID were to be sent from the mainframe to the middle tier >> somewhere, should I expect that the mainframe would only pas along upper >> cased values in the UUID area? >> >> I believe I can handle things on the mainframe side by transforming the >> entire message to UTF-16BE, and then upper casing the UUID, and then >> transforming this updated UTF-16BE message area to EBCDIC CodePage 930. >> Not sure if this is a "good" way, but it would work. >> >> Any thoughts? >> >> Thanks >> >> .......Cameron >> >> ---------------------------------------------------------------------- >> 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 >> > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
