Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
On Mon, 30 Mar 2009 14:40:56 -0400, Dan D wrote: >PS. Why aren't people sending to the list so that everyone gets to >contribute/critisize? I've seen the original message and 13 replies before yours via the web site, so it looks to me like people are sending it to the list. Perhaps you're having some kind of email problem? -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
Maybe I'm missing something. You could take that 1 byte from the IXCQUERY and unpack convert it to a 2 byte decimal number to generate a unique console name. ie. x'01' to identify CONSOL01. This way you have the ability to uniquely identify 100 consoles. You could also expand this to convert to a 3 byte name (CONSO255) and identify a maximum of 256 console name/ As I don't know how this 1 byte field is created that is returned from IXCQUERY, I must be missing something. This seems too simple. PS. Why aren't people sending to the list so that everyone gets to contribute/critisize? DanD Edward Jaffe wrote: Smith, Sean M wrote: Thank you for the suggestion Ed. I'll look into IXCQUERY as another option and learning experience. Regarding the use of a single digit, the digit will be used as part of a CONSOLE name so numbers and upper-case alpha and #, $ and @ are the only valid characters. The "normal" approach to unique console naming within a sysplex depends on the system symbol &SYSCLONE. Programs generally call the ASASYMBM service to perform the symbolic substitution. &SYSCLONE values are guaranteed unique, assigned by the customer, and not dependent on the order in which systems join the sysplex. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
Smith, Sean M wrote: Thank you for the suggestion Ed. I'll look into IXCQUERY as another option and learning experience. Regarding the use of a single digit, the digit will be used as part of a CONSOLE name so numbers and upper-case alpha and #, $ and @ are the only valid characters. The "normal" approach to unique console naming within a sysplex depends on the system symbol &SYSCLONE. Programs generally call the ASASYMBM service to perform the symbolic substitution. &SYSCLONE values are guaranteed unique, assigned by the customer, and not dependent on the order in which systems join the sysplex. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
On Mon, 30 Mar 2009 08:57:06 -0400, Rich Greenberg wrote: >In article you write: >>On Fri, 27 Mar 2009 11:44:18 -0700, Smith, Sean M >> wrote: >>>I am modifying an assembler program and I have a need to have a single >>>digit unique identifier for a system within a SYSPLEX. >> >>Don't forget that a parallel sysplex can have 32 systems. I think that will >>make it difficult to have a single-digit identifier that will work in all >>possible configurations :-) > >Your thinking of just digits. Keep in mind that a byte can contain any >of 256 values (x'00' - x'FF'). If you want to stick to printable, the >letters and numbers give you 36 different values. Sean's the one who limited it to "single digit unique identifier" in his original message. I agree, of course, that if you allow other characters you can handle more than 32 systems. -- Walt Farrell, CISSP IBM STSM, z/OS Security Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
Thank you for the suggestion Ed. I'll look into IXCQUERY as another option and learning experience. Regarding the use of a single digit, the digit will be used as part of a CONSOLE name so numbers and upper-case alpha and #, $ and @ are the only valid characters. 10 numbers + 26 Upper-Case + 3 special characters = 39 which is greater than the 32 maximum systems allowed in a SYSPLEX. Of course I would like to see this code live through future changes which is not possible with the naming restrictions for console-name and using a single character: "Value Range: conname is from 2 to 8 characters. The first character of conname must begin with the letters A through Z or with a #, $, or @; the remaining characters can be A through Z, 0 through 9, or #, $, or @." These rules would only allow a single character to be up to 39. With this restriction it seems that I will be forced to code the program to handle up to the current limit of 32 unless I look to change the program to use a 2 character identifier. Sean -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Edward Jaffe Sent: Friday, March 27, 2009 3:33 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Need single character unique identifier for each system in a sysplex. 0-F is fine. Smith, Sean M wrote: > Fellow IBMers and Mark. Zelden in particular, > Mark *is* a celebrity! ;-) > I am modifying an assembler program and I have a need to have a single > digit unique identifier for a system within a SYSPLEX. I started by > looking at Mark Zelden's IPLINFO (thanks again Mark...this has been a > huge boon to me REXX skill set as I reference your techniques > frequently). I looked at the following fields (field names from > IPLINFO): > For supervisor state or PKM 0-7 callers there is IXCQUERY REQINFO=COUPLE,SYSTEMID=area -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
The number of characters on 1442 printer bar? Tom Puddicombe Mainframe Performance & Capacity Planning CSC 71 Deerfield Rd, Meriden, CT 06450 ITIS | (860) 428-3252 | tpudd...@csc.com | www.csc.com This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. Ted MacNEIL Sent by: IBM Mainframe Discussion List 03/30/2009 09:36 AM Please respond to IBM Mainframe Discussion List To IBM-MAIN@bama.ua.edu cc Subject Re: Need single character unique identifier for each system in a sysplex. 0-F is fine. >>Your thinking of just digits. Keep in mind that a byte can contain any >>of 256 values (x'00' - x'FF'). If you want to stick to printable, the >>letters and numbers give you 36 different values. > >62? (What code page are you using?) Where did 62 come from? I see 256, x'00', x'FF', & 36 in the post. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
>62 = 10 (numeric + 26 (alphabetic upper case)+ 26 (alphabetic lower case). >I had to do some arithmetic on it myself, to figure it out. Yes, but! I saw no 62 in the original post, and I admit I was lower-case challenged, too. PS: if nationals are supported, then it's 65. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
62 = 10 (numeric + 26 (alphabetic upper case)+ 26 (alphabetic lower case). I had to do some arithmetic on it myself, to figure it out. Jim Horne Systems Programmer Large Systems Engineering & Messaging IS7-5 Lowe's Companies, Inc. 401 Elkin Highway North Wilkesboro, NC 28659 336-658-4959 jim.ho...@lowes.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Monday, March 30, 2009 9:37 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Need single character unique identifier for each system in a sysplex. 0-F is fine. >>Your thinking of just digits. Keep in mind that a byte can contain any >>of 256 values (x'00' - x'FF'). If you want to stick to printable, the >>letters and numbers give you 36 different values. > >62? (What code page are you using?) Where did 62 come from? I see 256, x'00', x'FF', & 36 in the post. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: All information in and attached to the e-mail(s) below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
>>Your thinking of just digits. Keep in mind that a byte can contain any >>of 256 values (x'00' - x'FF'). If you want to stick to printable, the >>letters and numbers give you 36 different values. > >62? (What code page are you using?) Where did 62 come from? I see 256, x'00', x'FF', & 36 in the post. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
>Don't forget that a parallel sysplex can have 32 systems. >I think that will make it difficult to have a single-digit identifier that >will work in all possible configurations :-) Are numerics, alphas, and nationals supported? Alphas -- 26 Alphas & numerics -- 36 Alphanumerics & nationals -- 39. Obvious? I know. Also, what are the chances of going beyond 5-10 images in a SYSPLEX. I know there are some big shops out there, but the most I've had (almost 5000 MIPS) was 10, and that was a GDPS configuration. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
On Mon, 30 Mar 2009 08:57:06 -0400, Rich Greenberg wrote: > >Your thinking of just digits. Keep in mind that a byte can contain any >of 256 values (x'00' - x'FF'). If you want to stick to printable, the >letters and numbers give you 36 different values. > 62? (What code page are you using?) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
In article you write: >On Fri, 27 Mar 2009 11:44:18 -0700, Smith, Sean M > wrote: >>I am modifying an assembler program and I have a need to have a single >>digit unique identifier for a system within a SYSPLEX. > >Don't forget that a parallel sysplex can have 32 systems. I think that will >make it difficult to have a single-digit identifier that will work in all >possible configurations :-) Your thinking of just digits. Keep in mind that a byte can contain any of 256 values (x'00' - x'FF'). If you want to stick to printable, the letters and numbers give you 36 different values. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself & my dogs only.VM'er since CP-67 Canines:Val, Red, Shasta & Casey (RIP), Red & Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
On Fri, 27 Mar 2009 11:44:18 -0700, Smith, Sean M wrote: >I am modifying an assembler program and I have a need to have a single >digit unique identifier for a system within a SYSPLEX. Don't forget that a parallel sysplex can have 32 systems. I think that will make it difficult to have a single-digit identifier that will work in all possible configurations :-) -- Walt Farrell, CISSP IBM STSM, z/OS Security Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
Smith, Sean M wrote: Fellow IBMers and Mark. Zelden in particular, Mark *is* a celebrity! ;-) I am modifying an assembler program and I have a need to have a single digit unique identifier for a system within a SYSPLEX. I started by looking at Mark Zelden's IPLINFO (thanks again Mark...this has been a huge boon to me REXX skill set as I reference your techniques frequently). I looked at the following fields (field names from IPLINFO): For supervisor state or PKM 0-7 callers there is IXCQUERY REQINFO=COUPLE,SYSTEMID=area -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Need single character unique identifier for each system in a sysplex. 0-F is fine.
On Fri, 27 Mar 2009 11:44:18 -0700, Smith, Sean M wrote: >Fellow IBMers and Mark. Zelden in particular, > >I am modifying an assembler program and I have a need to have a single >digit unique identifier for a system within a SYSPLEX. I started by >looking at Mark Zelden's IPLINFO (thanks again Mark...this has been a >huge boon to me REXX skill set as I reference your techniques >frequently). I looked at the following fields (field names from >IPLINFO): > > >LPAR_# From PCCA + 7 >CSDPLPN From CSD + 252 >JESDSNIDFrom JESPEXT + 100 - Recognizing this is actually a 2 digit >field > > >The program I am modifying is being used in z/OS 1.8 - z/OS 1.10 in both >JES2 and JES3 and in VM guests. The VM Guests ruled out CSDPLPN and >LPAR_# as it always came back as 0 on guests. JESDSNID seems to fit the >bill especially with the description from the IPLINFO utility: > >'This was system number' Format(JESDSNID) 'added to the sysplex.' > >My question is whether or not this field really represents the sequence >a system was added in to the SYSPLEX. From the Data Areas manuals I see >this description: > >JESDSNID ID for temporary data > > sets on this system. > >I did a test on 3 systems to check out this field. All three systems >are in the same SYSPLEX but one is in its own JES MAS. The numbers came >back all unique (1,2,3) so I am encouraged. > >Any commentary or suggestions about my quandary are as always greatly >appreciated. > >Sean It's not documented as such, but empirical evidence has shown me that JESDSNID does indeed represent the sequence a system was added into the SYSPLEX. Since DASD and other resources are assumed to be shared in a sysplex, that number must be unique to avoid duplicate temp data set names. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Need single character unique identifier for each system in a sysplex. 0-F is fine.
Fellow IBMers and Mark. Zelden in particular, I am modifying an assembler program and I have a need to have a single digit unique identifier for a system within a SYSPLEX. I started by looking at Mark Zelden's IPLINFO (thanks again Mark...this has been a huge boon to me REXX skill set as I reference your techniques frequently). I looked at the following fields (field names from IPLINFO): LPAR_# From PCCA + 7 CSDPLPN From CSD + 252 JESDSNIDFrom JESPEXT + 100 - Recognizing this is actually a 2 digit field The program I am modifying is being used in z/OS 1.8 - z/OS 1.10 in both JES2 and JES3 and in VM guests. The VM Guests ruled out CSDPLPN and LPAR_# as it always came back as 0 on guests. JESDSNID seems to fit the bill especially with the description from the IPLINFO utility: 'This was system number' Format(JESDSNID) 'added to the sysplex.' My question is whether or not this field really represents the sequence a system was added in to the SYSPLEX. From the Data Areas manuals I see this description: JESDSNID ID for temporary data sets on this system. I did a test on 3 systems to check out this field. All three systems are in the same SYSPLEX but one is in its own JES MAS. The numbers came back all unique (1,2,3) so I am encouraged. Any commentary or suggestions about my quandary are as always greatly appreciated. Sean -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
