× 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.



I recommend that you go into DST (SST in later releases?) and create some 
users, as needed. Then do not ever use QSECOFR - it is too easy to fat-finger 
this, and it gets disabled too easily. Besides, if there is auditing turned on, 
you now know who did what. And you can specify what rights each user has - 
remember, this is not the same user as the iSeries user profiles.

Vern

-------------- Original message -------------- 
From: Jerry Adams <jerry@xxxxxxxxxxxxxxx> 

Are you on V5R3 or later? 

I fat fingered the Service Tools password once. Fortunately, there's a 
command that lets QSECOFR change the password: CHGDSTPWD. There should 
always be a User id of QSECOFR in Service Tools. This would probably be 
the one to change - if you're the Security Officer. And the 
recommendation is that the password not be the same for both. 


It is possible for a ST security officer to set-up users for selective 
functions. 


* Jerry C. Adams 
*IBM System i5/iSeries Programmer/Analyst 
B&W Wholesale Distributors, Inc.* * 
voice 
615.995.7024 
fax 
615.995.1201 
email 
jerry@xxxxxxxxxxxxxxx 



Don Cavaiani wrote: 

I don't remember what needs to go here ?? 
------------------------------------------------------ 
Type choice, press Enter. 

Service tools user ID. . . . 
Service tools password . . . 
Note: The password is case-sensitive. 













-----Original Message----- 
From: midrange-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx 
[mailto:midrange-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On 
Behalf Of rob@xxxxxxxxx 
Sent: Thursday, October 05, 2006 9:10 AM 
To: Midrange Systems Technical Discussion 
Subject: Re: Sluggish Performance 

http://faq.midrange.com/data/cache/418.html 

Rob Berendt 
-- 
Group Dekko Services, LLC 
Dept 01.073 
PO Box 2000 
Dock 108 
6928N 400E 
Kendallville, IN 46755 
http://www.dekko.com 





fbocch2595@xxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx 
10/05/2006 06:32 AM 
Please respond to 
Midrange Systems Technical Discussion 


To 
midrange-l@xxxxxxxxxxxx 
cc 

Subject 
Re: Sluggish Performance 






What do you mean by search on battery cache, how is that done? 


-----Original Message----- 
From: ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx 
To: midrange-l@xxxxxxxxxxxx 
Sent: Wed, 4 Oct 2006 12:03 PM 
Subject: RE: Sluggish Performance 


Couple of things to start off with: 

Search on 'battery cache' in the archives. 

Also, double check your memory pool allocations (WRKSYSSTS, WRKSHRPOOL), 
perhaps when you added subsystems you also reallocates some memory from 
*BASE. 

Elvis 

-----Original Message----- 
Subject: Sluggish Performance 

I've looked at the archives and tried some of the solutions there first 
before posting. 

We're experiencing very sluggish performance. Our CPU utilization is 
pretty low most of the time 20-30%. WRKDSKSTS reveals our I/O running 
40-60% Busy with gust to 80-100%. Actual job through put is pretty 
slow. 

This has happened recently all at once. We had added some new 
subsystems and the sluggish performance started. The slowdown caused us 
to take them out. We're still slow. I don't know if the subsystems had 
anything to do with the performance. 

Any ideas or things to check would be greatly appreciated. 

Glenn Thompson 
Senior Analyst 





-- 
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 thread ...


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.