×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Not necessarily disagreeing with you and somewhat jumping into the middle of this, but why do you need the LPAR identifier? Most business applications, if they want to know "where am I?", would simply access the system name (network attribute SYSNAME) and to access another LPAR they would do that treating the LPAR as simply another system (typically using it's SYSNAME). Most applications I've run into that need to know a specific LPAR identifier are more in the realm of systems management and need special knowledge of their environment. Knowledge typically not needed by the vast majority of applications on the system.
Bruce Vining
Mark Villa <iseries.4.me@xxxxxxxxx> wrote:
dear IBM Dev....
It is so silly to have to put up with difficulties for something as
basic as "where am i" i.e. Why in the heck is LPAR not part of the
current job attributes?
I do not know much about LPAR on iSeries, my only experience is on the
mainframe, but it seems that it should either not matter (i.e.
access the other LPAR as another system) or should be obtainable from
a SYSVAR or something available in CL. Writing code for this is
insane.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.