If you want that to run everywhere, make it address command 'PIPE COMMAND IDENTIFY .... this is the only way to make sure that no synonym or EXEC takes over the environment and plays games with you.
2008/2/21, Lionel B. Dyck <[EMAIL PROTECTED]>: > > > Thanks - the PIPE worked great > > ------------------------------ > *Lionel B. Dyck, Consultant/Specialist * > Enterprise Platform Services, Mainframe Engineering > KP-IT Enterprise Engineering > 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED]<[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: Jim Elliott <[EMAIL PROTECTED]> To: > IBMVM@LISTSERV.UARK.EDU Date: 02/21/2008 11:26 AM Subject: Re: z/VM REXX > Functions for system information > ------------------------------ > > > > > 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 > > -- Kris Buelens, IBM Belgium, VM customer support
