Re: Reason not to go to V6R1 -- MIDRANGE-L

× 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.

Subject: Re: Reason not to go to V6R1
From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
Date: Thu, 10 Jan 2008 13:01:45 -0500
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi, James:

> James Lampert wrote:

Side issue:

1. What's the minimum release level that produces *PGMs that, without full observability, will convert to V6?

V5R1

2. Does it have to actually be compiled from source at that level?

Can be compiled on any release >= V5R1. e.g. could be compiled on V5R4 with TGTRLS(V5R2M0).

Or you can even compile on releases <= V5R1, but then just do NOT remove observability.

HTH,

Mark

As an Amazon Associate we earn from qualifying purchases.

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