| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello and greetings,
ALL-IN-1 IOS V3.0 (British-ish)
The customer has not been able to run the TRM housekeeping procedure since
upgrading to 3.0 (ALL-IN-1 IOS is unpatched - they are still testing upgrades
on their development m/c)
The logfile has a number of errors in Phase 1 as follows:
Error opening SMLOG2.TMP as input file currently locked by another user
There is no Version 2.4 image of OA$SM_FCVR.EXE in the
[ALLIN1.SITE.LIB_ENGLISH] directory being executed when the TRM runs.
The oa$lib_share:oa$sm_fcvr.exe image and it's the correct image ie version 3.0.
Image Identification Information
image name: "OA$SM_FCVR"
image file identification: "ALL-IN-1 V3.0"
link date/time: 12-MAR-1992 03:45:44.10
linker identification: "05-09"
Patch Information
There are no patches at this time.
I saw the another STARS article which mentioned a similar problem with
"Error opening SMLOG2.TMP as input file currently locked by another user".
This related to a bad K603 kit. The customer did NOT install the bad patch
under 2.4 - he had the revide kit with "K603 SS FCVRUPD1 SHARE V2.4 ALL-IN-1".
The customer does have the manager account pointing to [ALLIN1.MGR]
He DOES still have the old K504 oa$sm_fcvr.exe_dummy file. Should it be
deleted? He also has OA$SM_FCVR_PHASE1.EXE, OA$SM_FCVR_PHASE2.EXE; and
OA$SM_FCVR_PHASE3.EXE. There seem to be quite a few of ye olde exes still
about.
Thanks & regards,
Chele
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3938.1 | GIDDAY::BURT | Scythe my dandelions down, sport | Mon Mar 07 1994 01:28 | 19 | |
Hi again,
Customer re-ran TRM. This time an error appeared in SMLOG2.TMP
Error adding daf key to in-memory table. Most likely cause is page file quota
exceeded
This occurred while DAFD was still being processed
Is it possible that this problem is causing the lock?
Customer increased pgflquo to 40,000 from 20,000, but won't be able to
schedule a re-run until next weekend.
Chele
| |||||
| 3938.2 | increased pgflquo might fix it | IOSG::CHAPLIN | Andy Chaplin | Mon Mar 07 1994 14:49 | 15 |
Hi Chele, It's possible that the two errors are linked. We had both errors occurr on IOSG recently, but everything has been OK since we inreased the ALLIN1 account page file quota. Let us know what happens on the re-run -- you may be lucky too. >He DOES still have the old K504 oa$sm_fcvr.exe_dummy file. Should it be >deleted? He also has OA$SM_FCVR_PHASE1.EXE, OA$SM_FCVR_PHASE2.EXE; and >OA$SM_FCVR_PHASE3.EXE. There seem to be quite a few of ye olde exes still >about. These can all be deleted. Andy | |||||
| 3938.3 | GIDDAY::BURT | Scythe my dandelions down, sport | Tue Mar 08 1994 05:53 | 20 | |
Hello again,
The customer plans to increase page file quota for ALLIN1 (the user).
Could someone PLEASE tell me the reference for the PGFLQUO and WSEXTENT
recommendations? For 2.4, according to a STARS article it was as follows:
PGFLQUO and WSEXTENT - must be large for in-memory tables,
and to reduce page faults otherwise
the procedure will run very slowly.
NOTE: WSMAX must be set to at least as much as WSEXTENT.
Recommended to be set to 60 pages per 1000 SDAF records.
You can use the $CONVERT/STAT command on the SDAF file
to determine the number of records. You may wish to
start with WSEXTENT set at 20,000.
For some reason 62 comes to mind, I know it has zip to do with Arthurian
theory. :^)
Chele
| |||||