Re: S36 to AS400 migration -- 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: S36 to AS400 migration
From: "Douglas Handy" <dhandy@xxxxxxxxx>
Date: Thu, 11 Jan 2007 15:24:49 -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>

Jerry,

I need to determine DASD requirements.  Their S36 has a capacity of

1,200,000 blocks.  How many bytes is this?



Blocks under SSP were ten sectors, each 256 bytes, so a block was 2560
bytes.
So that is basically 3GB of capacity.

Stuff takes more room on the i5, but it shouldn't be too hard to have over
3GB available on a new machine....

Doug

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: S36 to AS400 migration , Jerry Draper

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.