v4r5 casualty--cpytoimpf stmfcodpg parameter -- 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: v4r5 casualty--cpytoimpf stmfcodpg parameter
From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
Date: Tue, 4 Sep 2001 09:09:12 -0700
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I can't remember when we first applied the cpytoimpf stmfcodpg parameter
ptf, but it's been over a year and survived the upgrade to v4r4.   We
(better late than never) upgraded to v4r5 over the weekend and blew it away.
As a result, several production batch jobs died.  In case anyone is
interested, the ptf for v4r5 is SF62140.  Apparently it's considered a frill
by IBM.

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.