Re: Fwd: Saving a *SAVF to another LPAR -- MIDRANGE-L

Subject: Re: Fwd: Saving a *SAVF to another LPAR
From: "Andrew Lopez (SXS US)" <Andrew.Lopez@xxxxxxxxxxxxxxxxxx>
Date: Thu, 13 Dec 2018 15:41:26 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

No they do not require a BRMS license.
They are not separate objects, so perhaps that is your issue?
They are part of the service program QANESERV

DSPSRVPGM SRVPGM(QANESERV) DETAIL(*PROCEXP)

But it does require option 22 OptiConnect, correct?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Fwd: Saving a *SAVF to another LPAR , Rob Berendt

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.