| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2005.2 | non existent logicals OA$SITE_DEV ... | ZUR01::KURTH | Peter Kurth @RLE, R�mlang (CH) | Tue Jan 26 1993 12:44 | 74 |
| Hello
I have also a problem with "Internal error" when running RSF.
ALL-IN-1 V3.0 (no K701), default language=German, second language=English;
upgraded from V2.4.
The log extract looks like this (from REORGANIZE_SYS_FILES_SM.LOG*):
Shared file reorganization starting
Converting "OA$DATA_LLV:FORMAT.DAT" using FDL file "OA$LIB:FORMAT.FDL"
"OA$DATA_LLV:FORMAT.DAT" converted - was 26 blocks, now 26 blocks
.
.
Converting "OA$DATA_LLV:OA$PRINTSTYLES.DAT" using FDL file "OA$LIB:OA$PRINTSTYLES.FDL"
"OA$DATA_LLV:OA$PRINTSTYLES.DAT" converted - was 59 blocks, now 59 blocks
MANAGER finished using ALL-IN-1 at 26-Jan-1993 13:18 *)
"OA$SITE_DEV_ARC_ENGLISH:CM$SITEHIST.DAT" or "OA$LIB:CM$SITEHIST.FDL" does not exist
"OA$SITE_DEV_REC_ARC_ENGLISH:CM$SITEHIST.DAT" or "OA$LIB:CM$SITEHIST.FDL" does not exist
"OA$SITE_DEV_ARC_SHARE:CM$SITEHIST.DAT" or "OA$LIB:CM$SITEHIST.FDL" does not exist
"OA$SITE_DEV_REC_ARC_SHARE:CM$SITEHIST.DAT" or "OA$LIB:CM$SITEHIST.FDL" does not exist
.
.
Converting "OA$SITE_DEV_ENGLISH:CM$SITEHIST.DAT" using FDL file "OA$LIB:CM$SITEHIST.FDL"
"OA$SITE_DEV_ENGLISH:CM$SITEHIST.DAT" converted - was 249 blocks, now 249 blocks
.
.
Shared area reorganization starting
.
.
%SMJACKET-E- Internal error in housekeeping procedure
%SMJACKET-I performing %SMJACKET exit and cleanup processing
.
.
%SMJACKET-I %SMJACKET facility exiting due to error
%SMJACKET-E processing completed with an error for %SMJACKET
*) Here, the script OA$LIB:SMREORG.COM calls ALL-IN-1 and executes
SM_LIST_CM_HISTFILES.SCP. This creates a file containing logicals
for all application areas using:
FOR CM$MAF WITH AREASTATUS:U NES "CLOSED" DO -
GET #area_log = "OA$SITE_DEV_" .AREA ":CM$SITEHIST.DAT" \\-
GET #rec_area_log = "OA$SITE_DEV_" .RECEIVE_AREA":CM$SITEHIST.DAT" \\-
TEXT_FILE WRITE #channel #area_log \\-
TEXT_FILE WRITE #channel #rec_area_log
On our system, most of these logicals do not exist, therefore the above
error messages. The existing logicals are:
(LNM$SYSTEM_TABLE)
"OA$SITE_DEV_ENGLISH" = "OASYS$DISK:[ALLIN1.SITE.DEV_ENGLISH]"
"OA$SITE_DEV_GERMAN" = "OASYS$DISK:[ALLIN1.SITE.DEV_GERMAN]"
"OA$SITE_DEV_REC_ENGLISH" = "OASYS$DISK:[ALLIN1.SITE.DEV_REC_ENGLISH]"
"OA$SITE_DEV_REC_GERMAN" = "OASYS$DISK:[ALLIN1.SITE.DEV_REC_GERMAN]"
"OA$SITE_DEV_REC_SHARE" = "OASYS$DISK:[ALLIN1.SITE.DEV_REC_SHARE]"
"OA$SITE_DEV_SHARE" = "OASYS$DISK:[ALLIN1.SITE.DEV_SHARE]"
CM$MAF contains two times all the areas, e.g. ARC, CBI, CM ... The area
status is "Open". CM$APP looks much better, it contains one time the
area with status "Closed" (exept OA, which is "Open").
Why does CM$MAF contains all these areas? Why status open? Why twice?
If you want to have a look at these files, see ZUR01::SYS$PUBLIC:CM*.DAT.
(ZUR01 = 48.241)
Thanks and regards, Peter
|
| 2005.3 | Known problem during second language installation | UTES09::EIJS | Simon Eijs @Utrecht, 7838-2558 | Tue Feb 02 1993 06:58 | 25 |
|
Peter,
Before the release of BL123A there used to be a problem that when
populating the CM data files CM$APP would have the correct 'For Digital
use only' application codes, but an associated number of application
areas were created, which shouldn't be there. The installation
procedure now creates entries in CM$APP for the OA application (and the
possible applications coming from V2.*), then in CM$MAF the associated
application areas and then the 'restricted' application codes in
CM$APP.
However, it's a known problem that a second language installation,
although following the same path as described above, creates the
application areas for the 'For Digital use only' application codes as
if they were coming from V2.*.
The suggested workaroud is to delete the application areas starting
with: ARC_*, CBI_*, CM_*, DIR_*, EM_*, FC_*, GS_*, KEY_*, OAN_*, SA_*,
SM_*, TM_*, WP_* and WPL_*.
Ciao,
Simon
|
| 2005.4 | Missing CM$SITEHIST.DAT caused troubles ... | ZUR01::KURTH | Peter Kurth @RLE, R�mlang (CH) | Wed Feb 03 1993 17:23 | 33 |
| Hello Simon
Thanks for your help.
I removed all the areas using:
MA (Manage Applications)
SEL
Application: ARC
Area: ARC_GERMAN (and ARC_SHARE and all others)
DA (Delete an application area)
Press RETURN to delete this record
Delete development and receive directories and files? [Y/N] N
The housekeeping RSF now runs correctly through existing directories
(e.g. [ALLIN1.SITE.DEV_GERMAN] and [ALLIN1.SITE.DEV_REC_GERMAN].
Their is now another internal error reported by the procedure, stating
"OA$SITE_DEV_REC_ENGLISH:CM$SITEHIST.DAT not found".
This file is missing in OA$SITE_DEV_REC_ENGLISH. In all other locations
(OA$SITE_DEV_ENGLISH, OA$SITE_DEV_GERMAN, OA$SITE_DEV_REC_GERMAN,
OA$SITE_DEV_REC_SHARE, OA$SITE_DEV_SHARE), the file is stored.
Should CM$SITEHIST.DAT be created during upgrade (English was a second
language upgrade), or when?
I copied the empty file from OA$SITE_DEV_REC_GERMAN and RSF now
completes successfully.
Regards, Peter
|
| 2005.5 | Any error message during upgrade second language? | UTES09::EIJS | Simon Eijs @Utrecht, 7838-2558 | Tue Feb 09 1993 11:20 | 16 |
|
Hi Peter,
During an upgrade installation, CM$SITEHIST.DAT is copied from
OA$DATA_SHARE: to OA$SITE_DEV_SHARE and OA$SITE_DEV_<llv>: During a
second language also (with a check if the one in OA$SITE_DEV_SHARE:
exists). This is done to preserve the info from V2.*.
However, the CM$SITEHIST.DAT in OA$SITE_DEV_REC_*: are created during
the installation. In SHARE and <llv> during a primary language, in
<llv> during a secondary language installation. Didin't any error
message occur?
Ciao,
Simon
|
| 2005.6 | No error messages | ZUR01::KURTH | Peter Kurth @RLE, R�mlang (CH) | Wed Feb 10 1993 09:30 | 5 |
| Hi Simon
No error messages during the second language upgrade.
Thanks for your information.
Regards, Peter
|
| 2005.7 | RSF failure? | ANGLIN::HARRISA | lost in the jungle of doubt | Mon Dec 20 1993 18:54 | 47 |
| ALL-IN-1 3.0-1, VMS 5.5-2
RSF keeps failing with no error message other than "internal error" in
the log file. i've checked the OA$SITE_DEV_* logicals per the DSN
article and they appear OK. i can set default to them and do a dir
fine.
Ann
%START_BATCH-I SYSPRV privilege enabled
%START_BATCH-I Attempt to take out a lock on the sender and fetcher
files
%START_BATCH-I SENDLOCK.DAT and FETCHLOCK.DAT locked
%START_BATCH-I running ALLIN1 under account "MANAGER" (/NOINIT/REENTER)
Stopping server CLIFFY::"73="
%OA-I-SHUT_NOTIFIED, All users have been notified of the shutdown
%START_BATCH-I performing %START_BATCH exit and cleanup processing
%START_BATCH-I SENDLOCK.DAT and FETCHLOCK.DAT unlocked
%START_BATCH-I processing completed ok for %START_BATCH
%SMJACKET-I Invoking Utility command file "OA$LIB:SMSREORG.COM"
%SMJACKET-I Invoking common END_BATCH procedure
%END_BATCH-I Performing End batch job procedures for "RSF"
%OA-I-LASTLINE,
%OA-I-LASTLINE,
%END_BATCH-I Deleting old log files
"OA$LOG:REORGANIZE_SYS_FILES_SM.LOG*;*" bef
%END_BATCH-I Purging old log files
"OA$LOG:REORGANIZE_SYS_FILES_SM.LOG*;*" to "
%END_BATCH-I Total of 2 logfiles, purge to 01, means delete 1
$ delete
APPL$DISK:[ALLIN1.LOG]REORGANIZE_SYS_FILES_SM.LOG1993120504000000;1
%END_BATCH-I Deleting old log files
"OA$LOG:REORGANIZE_SYS_FILES_SA.LOG*;*" bef
%END_BATCH-I Purging old log files
"OA$LOG:REORGANIZE_SYS_FILES_SA.LOG*;*" to "
%END_BATCH-I Total of 0 logfiles, purge to 01, means delete -1
%END_BATCH-I performing %END_BATCH exit and cleanup processing
%END_BATCH-I processing completed ok for %END_BATCH
%SMJACKET-E- Internal error in housekeeping procedure
%SMJACKET-I performing %SMJACKET exit and cleanup processing
%SMJACKET-I close lockfiles
%OA-I-LASTLINE, Submitting server CLIFFY::"73=" startup to batch...
|
| 2005.8 | RSF log 'funnies' (Moved from 3982) | GIDDAY::BURT | Scythe my dandelions down, sport | Wed Mar 16 1994 00:05 | 60 |
| Hello and greetings,
Customer running ALL-IN-1 V3.0 British(ish)
Customer has a couple of sites running ALL-IN-1, and both are running into
problems with RSF. On one node, the FCS does not start up, although there do
not seem to be any error messages explaining _why_.
Customer has CM$SITEHIST.DAT in
[ALLIN1.SITE.DEV_BRITISH]
[ALLIN1.SITE.DEV_REC_BRITISH]
[ALLIN1.SITE.DEV_REC_SHARE]
[ALLIN1.SITE.DEV_SHARE]
The ALLIN1 account DOES have the OAFC$SYSMAN identifier.
One thing we BOTH find particularly intriguing is ALL-IN-1s desire to delete
-1 versions.
Thanks & regards,
Chele
Extracts from the customer logs follow:
%END_BATCH-I Performing End batch job procedures for "RSF"
%OA-I-LASTLINE,
%OA-I-LASTLINE,
%END_BATCH-I Deleting old log files "OA$LOG:RSF.LOG*;*" before date "14-S
%END_BATCH-I Purging old log files "OA$LOG:RSF.LOG*;*" to "01" versions
%END_BATCH-I Total of 2 logfiles, purge to 01, means delete 1
$ delete DISK$ALLIN1:[ALLIN1.LOG]RSF.LOG1994030600010000;1
%END_BATCH-I Deleting old log files "OA$LOG:RSF_SA.LOG*;*" before date "1
%END_BATCH-I Purging old log files "OA$LOG:RSF_SA.LOG*;*" to "01" versions
%END_BATCH-I Total of 0 logfiles, purge to 01, means delete -1
%END_BATCH-I performing %END_BATCH exit and cleanup processing
%END_BATCH-I processing completed ok for %END_BATCH
%SMJACKET-E- Internal error in housekeeping procedure
%SMJACKET-I performing %SMJACKET exit and cleanup processing
%SMJACKET-I close lockfiles
%SMJACKET-I Commencing batch execution of utility type "RSF" at 13-MAR-19
%SMJACKET-I Invoking common START_BATCH procedure
%START_BATCH-I Performing Start batch job procedures for "RSF"
%START_BATCH-I SYSPRV privilege enabled
%START_BATCH-I Attempt to take out a lock on the sender and fetcher files
%START_BATCH-I SENDLOCK.DAT and FETCHLOCK.DAT locked
%START_BATCH-I running ALLIN1 under account "MANAGER" (/NOINIT/REENTER)
Stopping server PEEL::"73="
Stopping server ULM::"73="
%OAFC-E-SRVNOTAVAIL, File Cabinet Server is not available
%OA-I-SHUT_NOT_NOTIFI, Some users could not be notified of the shutdown
%START_BATCH-I performing %START_BATCH exit and cleanup processing
%START_BATCH-I SENDLOCK.DAT and FETCHLOCK.DAT unlocked
%START_BATCH-I processing completed ok for %START_BATCH
%SMJACKET-I Invoking Utility command file "OA$LIB:SMSREORG.COM"
Shared file reorganization starting
|
| 2005.9 | why RSF? | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Thu Mar 17 1994 02:37 | 16 |
| Chele,
what's even funnier or more confusing is why the log is called RSF.LOG
and not the easily memorable and typable
oa$log:REORGANIZE_SYS_FILES_SM.LOG1994012101000000;1
and why doesn't it show all this nice converting "blah.blah" messages
or did you omit that bit.
the purging thing is normal e.g
%END_BATCH-I Total of 0 logfiles, purge to 05, means delete -5
appears even on my badly managed system
regards,
Andrew.D.Wicks
|