Re: Quick easy way to determine what LPAR you're on? -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Quick easy way to determine what LPAR you're on?
From: Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Thu, 4 Feb 2021 16:35:14 +0000 (UTC)
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hi, James,

You are correct, sir!

I was just trying to clarify in answer to the question "where does it come from".

Mark

On Thursday, February 4, 2021, 11:31:30 AM EST, James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:

On 2/3/21 8:55 PM, Mark Waterbury wrote:
This CL program must be "CLLE" (ILE CL), created with CRTCLMOD, and
then bound with BNDSRVPGM(*LIBL/QPMLPMGT) specified on the CRTBNDPGM
command. So, the procedure "dlpar_get_info" is contained in the
*SRVPGM named QPMLPMGT in QSYS.

I gathered that it had to be "CLLE" just from the presence of a CALLP
statment. Given that, it compiled and linked just fine with Option 14 on
PDM, so evidently CRTBNDCLPGM must have found the right service program.

JHHL

This mailing list archive is Copyright 1997-2026 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.