Thanks, Peter and all. I'm disappointed to find this out so late. There were several folks involved in early implementation who decades of z/OS experience, and apparently none of them were aware of this.
The fact that this discussion took a while to get to definitive references is also perhaps indicative that this isn't as well known as it might could/should be. That's not a criticism per se, just an observation--not sure how anyone could fix it at this juncture. I suspect the real solution is to fire up the DeLorean and go back to 1964, make sure this is canon across all OS/360 software teams... -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Relson Sent: Thursday, December 19, 2024 8:32 AM To: [email protected] Subject: Re: z/OS message code length One might say that a "token" longer than 10 characters at the beginning of a message is not a message ID. Another place where the limit is "used" is in National Language Support. NLS skeletons provide room for only 10 characters for the message ID. Another place is the MSGID parameter of the SLIP command which includes the documentation "The input MSGID can be a maximum of 10 characters". Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
