Re: Adding DASD to a 520 -- 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.

Perhaps the manuals ?

Why would try to do something like this with no written instructions ?

http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/iphan/installmemory8203.htm&resultof=%2522%256d%2565%256d%256f%2572%2579%2522%2520%2522%2569%256e%2573%2574%2561%256c%256c%2561%2574%2569%256f%256e%2522%2520
and
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/iphal_p5/installadiskdrive.htm

Brian Piotrowski wrote:

Thanks for the responses, everyone.

Just as an FYI - the expansion unit is already installed - all I am doing is just installing the additional DASD to the disks that already exist in it (there's four in it right now, so I'd be shoving an additional eight disks into it). I guess that wasn't entirely clear in my original email. Like I said the only concern I have is if I try to do this during production that it will slow our 400 down to a crawl and really cause issues for the folks on the production floor who use it.

But it sounds simple enough - pop the disks in, and use SST. I'm guessing in SST I need to (3) Work with disk units -> (2) Work with disk configuration -> (2) Add units to ASPs - - correct?

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.