The system name returned by the Q USERID and the IDENTIFY both are the same for me
Thanks - I've updated my code to use the pipe command and all is great. Thanks everyone Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We're here to make lives better." I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. From: Shimon Lebowitz <[EMAIL PROTECTED]> To: [email protected] Date: 02/21/2008 12:04 PM Subject: Re: z/VM REXX Functions for system information And there is another system name, not necessarily the same: 'PIPE CP Q USERID | SPECS W3 1 | VAR CPSYSNAME' Which 'system name' do you want? ---- Original message ---- >Date: Thu, 21 Feb 2008 14:22:25 -0500 >From: Jim Elliott <[EMAIL PROTECTED]> >Subject: Re: z/VM REXX Functions for system information >To: [email protected] > >> Thanks - I was looking for an easy way to find the current >> system name so I could include that in alert messages I send >> out. > >> I found I could do this: > >> /* rexx */ >> 'identify (stack' >> parse pull id >> parse value id with x y name . >> .... > >> This at least gives me the system name and that is all I need >> for now. > >Lionel: > >How about: > >'PIPE cms IDENTIFY | specs w3 1 | var name' > >Jim
