Re: Erasing DASD-decommission an AS400/iSeries/System i -- 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: Erasing DASD-decommission an AS400/iSeries/System i
From: rob@xxxxxxxxx
Date: Fri, 19 Jan 2007 08:22:22 -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>

Isn't the number of bytes in a file member limited to 1.8TB?
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/dbp/rbafoappmax.htm
You'd have to make the file USROPN.  ADDPFM a new member like A000000002. 
EXTNAME to that member with that variable.  OPEN the file.  WRITE until 
error occurs.  CLOSE.
Lather, Rinse, Repeat.

Ah, the beauties of Open Source, we can all pool our ideas on how to 
improve the program.

Rob Berendt

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.