Re: CPYTOIMPF fails mysteriously -- 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: CPYTOIMPF fails mysteriously
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 20 Jun 2019 14:27:46 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
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>

On Thu, Jun 20, 2019 at 2:13 PM Jack Woehr
<jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I think this is a waste of time now: Clearly, something is
wrong on this LPAR. Perhaps the next cume or TR will fix it.

It's a good excuse to whip up a quick Python script to serve as a
replacement. ;)

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPYTOIMPF fails mysteriously , Jack Woehr

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.