|
That's been my belief also. Perhaps the iSeries is as bad at recovering from device errors as the S/38 was at recovering from communication errors? There are some factors which lead me to believe that it is recovery from device errors. This is an LPAR system. And a vast bulk of the processors are allocated to this partition % CPU used . . . . . . . : 10.7 System ASP . . . . . . . : 2443 G % DB capability . . . . : .8 % system ASP used . . . : 85.7205 Elapsed time . . . . . . : 00:00:08 Total aux stg . . . . . : 2443 G Jobs in system . . . . . : 60953 Current unprotect used . : 23582 M % perm addresses . . . . : .152 Maximum unprotect . . . : 25798 M % temp addresses . . . . : 2.068 Sys Pool Reserved Max ----DB----- --Non-DB--- Act- Wait- Act- Pool Size M Size M Act Fault Pages Fault Pages Wait Inel Inel 1 2637.89 707.05 +++++ .1 .1 2.3 53.2 89.9 .0 .0 2 6456.94 4.65 818 .1 230.3 187.3 875.6 15947 .0 .0 3 2265.44 .19 292 2.3 3.5 15.5 29.6 408.2 .0 .0 4 3466.07 .01 80 1.0 1.0 1.3 3.2 857.9 .0 .0 5 173.64 .00 51 .0 .0 .0 .0 .0 .0 .0 Resource Type-model Status Text CEC01 9406-840 Operational Main Card Enclosure PN01 247A Operational System Control Panel MP09 245F-000 Operational System Processor Card MP10 245F-000 Operational System Processor Card MP11 245F-000 Operational System Processor Card MP12 245F-000 Operational System Processor Card MP13 245F-000 Operational System Processor Card MP14 245F-000 Operational System Processor Card MP15 245E-000 Operational System Processor Card MP16 245E-000 Operational System Processor Card MP17 245E-000 Operational System Processor Card MP18 245E-000 Operational System Processor Card MP19 245E-000 Operational System Processor Card MP20 245E-000 Operational System Processor Card PV02 2418-001 Operational Processor Capacity Card PV01 1543-001 Operational Interactive Card SP01 28AA Operational Service Processor Card ... Partition identifier and name . . . . . . . . : 1 GDIHQ Current / available number of processors . . . : 11 / 0 New number of processors . . . . . . . . . . . . 11 Use shared processor pool . . . . . . . . . . . 1 1=Yes, 2=No New shared processor pool units . . . . . . . 11 . 00 Current / available size of main storage (MB) : 15000 / 0 New size of main storage (MB) . . . . . . . . . 15000 Current / available interactive feature . . . : 95 / 0 % New interactive feature . . . . . . . . . . . . 95 % Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/23/2003 09:16 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc Subject RE: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 Rob, I know that this was recommended as of the later-generation CISC boxes, and we had to try this when dealing with some response time problems. This was on a 310, and the advice seemed legitimate at that time. However, I seriously doubt that 450 users in a subsystem could be as much of a strain on today's processors.... Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Tuesday, September 23, 2003 8:59 AM To: Midrange Systems Technical Discussion Subject: Re: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 Any comments regarding IBM's first recommendation? Is having more than 250-300 users in a single QINTER a performance issue? Currently we have about 450 jobs in QINTER. And some of those are multiple session users. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin rob@xxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/22/2003 02:11 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 IBM's response: It appears that the subsystem was busy processing device errors, and didn't respond to the Retrieve Group Attributes request. After the interactive job wits 30 seconds for the subsystem to reply, it will post the CPF1317. . Out first recommendation would be to check the number of users in the interactive subsystem. We recommend only having 250 - 300 users in an interactive subsystem, and we may see a variety of errors if that number is exceeded. The subsystem is just bogged down too much with device processing if we have too many devices. . Second, there are a few PTFs we'd recommend for general subsystem concerns. I'd recommend downloading and applying SI09702 and SI09642 for 5722SS1. There is a third PTF for APAR SE11621, but this third PTF is not yet available. . Hopefully, these recommendations should help prevent this problem from occurring again. By the way, this error occurred in SYS501C. Some of you know what that program is, and also know that I do not have access to the source, etc. I'll order the ptf's and see what they do. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.