• Subject: RE: Another ASP question
  • From: "Bob Crothers" <Bob2@xxxxxxxxxxxxxx>
  • Date: Fri, 18 May 2001 15:00:27 -0500
  • Importance: Normal

Put a limit on max aux storage their profiles can own.  CHGUSRPRF xxxx
MAXSTG(value)

Bob

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Jim Damato
Sent: Friday, May 18, 2001 2:38 PM
To: 'MIDRANGE-L@midrange.com'
Subject: Another ASP question

We have a 740 with about 550 gig. of storage used for production and
development.  We've been dealing with the classic issue of developers
overrunning storage with test copies of large production files.  Our
Unix
and VMS admins point out that it's not an issue on those systems
because
development directories are confined to their own disk.  I decided to
insulate production from development by confining development libraries
to
their own ASP.

The first time someone filled up development libraries in ASP 2 I
discovered
that OS/400 automatically spills ASP 2 into ASP 1.  It creates a mess
that
may be difficult to recover from, and it keeps sending messages to
QSYSOPR
while you've got ASP 2 objects partially supported in ASP 1.  We
discovered
that ASP 2 can be prevented from spilling into ASP 1 by compressing ASP
2.
Apparently the system will not extend the compressed objects into a
non-compressed ASP.  The first time someone filled up development
libraries
in compressed ASP 2 it created a bigger mess by locking up the whole
system,
attempting to recompress for the incoming huge objects.

Am I missing something basic?  Is there an easy way to section off a
development ASP so developers can't overrun production storage?

Much thanks...

-Jim

James Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.