RE: Is there an easy way to find out what LPAR you are in?

How about GO SERVICE, then option 6. Based on my machines, this works for V5R3 and above.

Regarding the last question in James H. H. Lampert's email (sorry I don't know how to reply directly to that post), a customer might need to know this information so that he or she could place an order for your software in the first place. Customer support tells me we have that problem with our product too.
============================
James H. H. Lampert's email:
Thanks, everybody. It was as I suspected (maybe not even as bad).

Personally, my first choice would be to use the authorization code installer that comes with any of our products (i.e., WRKVIEWINF for QuestView, WRKWINTINF for Wintouch), which provides that information.

But that doesn't exactly help those who don't have one of our products installed. Although personally, I dunno why somebody would be calling us for tech support if they didn't.
=============================
Regards,
Philip Seay
www.inovis.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, May 06, 2010 11:50 AM
To: Midrange Systems Technical Discussion
Subject: Re: Is there an easy way to find out what LPAR you are in?

No. A "standard" is to license by lpar number. The OP is probably using
those APIs to access the lpar number. He's looking for something to show
the customer that his API is not malfunctioning and that his lpar really
does have a number of 2.

While some people may have system names like
SERIAL#1 where 1 is lpar 1
SERIAL#2 where 2 is lpar 2
and SERIAL# is the system serial number. While a default, it is often not
left that way. I have 10 lpars and none of them use the system serial
number for the system name. See CHGNETA. I run that before creating the
first user profile.
I suspect the number of vendors using system name is small to negligible
compared to those using lpar number or some other means.

Rob Berendt