There is a modify command for ANTMAIN which handles cache for DFDSS
ConcurrentCopy to limit the storage used regarding the aux storage available.
Search with keywoard CC in the sms booksheleves.
--
For IBM-MAIN subscribe /
) lpars?
IRA400E 04,PAGEABLE STORAGE SHORTAGE
*IRA404I ANTAS001 ASID 0131 OWNS 386726 PAGES, 326911
FIXED,
158567 FIXED IN SHORTAGE AREA
*IRA404I ANTAS003 ASID 0140 OWNS 388012 PAGES, 311695
FIXED,
114506 FIXED IN SHORTAGE AREA
*IRA404I ANTAS004 ASID 013E OWNS
Hi Sharon,
seem similar with multiple concurrent copy sessionswhen the quantity of
disk updates exceeded the rate at which data was being written to tape
flow control problem...
you need to confirm that your data paths out of your SDM lpar are sufficient
to contain the volume of data
Has anyone seen this on your SDM (SYSTEM DATA MOVER) lpars?
IRA400E 04,PAGEABLE STORAGE SHORTAGE
*IRA404I ANTAS001 ASID 0131 OWNS 386726 PAGES, 326911
FIXED,
158567 FIXED IN SHORTAGE AREA
*IRA404I ANTAS003
On Wed, Oct 27, 2010 at 1:08 PM, Sharon Lopez sharon.lo...@nc.gov wrote:
Has anyone seen this on your SDM (SYSTEM DATA MOVER) lpars?
IRA400E 04,PAGEABLE STORAGE SHORTAGE
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2m9a0/17.29?ACTION=MATCHESREQUEST=IRA400ETYPE=FUZZYSHELF
In a message dated 10/27/2010 1:49:12 P.M. Central Daylight Time,
mike.a.sch...@gmail.com writes:
large amount of memory at the time the message was generated. Review
to see what programs they were running.
pV=nRT ? Gas law. My guess would be too many Requests, pipe/path is
clogged,
Users (or jobs) ANTAS001, ANTAS003, ANTAS004, ANTAS002 was using a
large amount of memory at the time the message was generated.
Review to see what programs they were running.
These are part of z/OS.
Along with ANTMAIN.
I forget exactly what they do, but I believe they have something to do with
http://publib.boulder.ibm.com/infocenter/zos/v1r10/index.jsp?topic=/com.ibm.zos.r10.antg000/sdm.htm
Suggests it is part of eXtended Remote Copy (XRC). You might look at
I/O rates, a cable might have been cut and I/O stacked up on your
primary. Do you route your connections via different routes.
I had the same problem at this site a month ago. My Low and OK
thresholds for frame stealing were already set at 4000,4500. I doubted
that adding a few hundred more to the OK threshold would make a
difference.
What I found was that all of the batch jobs using up memory are running
SyncSort's
Wait a minute, I thought the State of Colorado doesn't have mainframes anymore!
[EMAIL PROTECTED] 4/12/2006 12:24:35 PM
I had the same problem at this site a month ago. My Low and OK
thresholds for frame stealing were already set at 4000,4500. I doubted
that adding a few hundred more to the
On Sat, 8 Apr 2006 08:27:11 +1000, Shane [EMAIL PROTECTED] wrote:
On Fri, 2006-04-07 at 13:09 -0400, Knutson, Sam wrote:
We are talking about a shortage of PAGEABLE storage not paged storage.
Nothing Mark can do with his PAGE data sets is going to help. Every
time we have been bitten by this
Hmm, lost my reply somehow. Anyway, check out your ieaopt/mccafcth setings.
I had to increase mine on a ~2.5gb system to avoid depleted afc and
pageable storage shortages. system would get low and something like a sort
would hit and system couldn't keep up. check out the mxg site or ibmlink
for
Several day ago we received the following messages:
IRA400E 04,PAGEABLE STORAGE SHORTAGE
IRA403E PXXX SWAPPED TO RECLAIM PROCESSOR STORAGE; 001759 PAGES
000117 FIXED
etc...
Then we received:
IRA401E 04,CRITICAL PAGEABLE STORAGE SHORTAGE
IRA403E IOAOSASF SWAPPED TO RECLAIM
eliminated a pathological cause, you should increase
significantly your paging configuration by PAGEADDing one or two large
page data sets. As a standby measure, you should always have another
page data set in reserve, to be PAGEADDed upon receiving the IRA400E
message.
Please follow up
, 2006 11:04 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: IRA400E
Several day ago we received the following messages:
IRA400E 04,PAGEABLE STORAGE SHORTAGE
IRA403E PXXX SWAPPED TO RECLAIM PROCESSOR STORAGE; 001759 PAGES
000117 FIXED etc...
Then we received:
IRA401E 04,CRITICAL PAGEABLE
, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
Don't hit the keys so hard, it hurts.
IRA400E return-code,PAGEABLE STORAGE SHORTAGE
Explanation: The system detected a shortage of pageable central
On Fri, 2006-04-07 at 13:09 -0400, Knutson, Sam wrote:
We are talking about a shortage of PAGEABLE storage not paged storage.
Nothing Mark can do with his PAGE data sets is going to help. Every
time we have been bitten by this it was a SORT product being too
aggressive in using FIXED frames.
Sorry folks. I must have just gotten up from a nap when I read the
original message.
Shane, no trout fishing here, just bridge and taxes.
Cheers,
Steve
Knutson, Sam wrote:
We are talking about a shortage of PAGEABLE storage not paged storage.
Nothing Mark can do with his PAGE data sets is
18 matches
Mail list logo