| 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 |
As the DIAMONDFT conference seems to be fading into the sunset, I trust
I can ask the following question here. I am upgrading from BL110A to
V3.0 and get the following error during the post installation (from
A1POST030.A). Should I worry about it? Is there a fix? Should I
RTFM?
Enter CMD:get #cm_bl121_type = "PRIMARY"
Enter CMD:do oa$lib:cm_post_bl121
%OA-I-LASTLINE, Modifying record values in ETYPES...
%OA-I-LASTLINE, Modifying record values in CM$OPTIONS$TYPE...
%OA-I-LASTLINE,
%OA-I-LASTLINE, Error adding record for 'PRA I1 002' option
%OA-I-LASTLINE, Deleting reserved records from CM$APP. CM$MAF and CM$AUTH$USERS...
%OA-I-LASTLINE, Adding records to CM$AUTH$LOCATIONS...
Enter CMD:
Before this I unwound the contents of A1POST030.A into OA$LIB_SHARE
(this was needed although the Release Notes said don't bother) and did
the "Primary Language Upgrade from BL110".
%OA-I-VERSION,
ALL-IN-1 IOS Server for VMS V3.0 PBL122D BRITISH 24-JAN-1992
Regards,
Bruce
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 115.1 | Check PRA I1 002 in CM$OPTIONS$TYPE | CESARE::EIJS | All in 1 Piece | Thu Feb 27 1992 12:30 | 28 |
Bruce,
Check if the record PRA I1 002 already existed in the dataset
CM$OPTIONS$TYPE. The post-installation adds them because they were
missing. As the procedure stops at that point, check if the following
records exist also (else the same would happen again):
PRC I1 002
PRA I2 002
PRC I2 002
If this/these record/records exist, either comment out the part in the
Script which adds the records, or delete the entries from the dataset
(procedure = CM_POST_OPTIONS_BL120BL121.SCP).
Then comment out all calls to the other conversion routines in script
CM_POST_BL121.SCP (except the one just changed), and run the
post-installation again.
Another way to solve this (as you're running BL122D) is:
If you haven't changed anything in the dataset CM$OPTIONS$TYPE yet,
extract the dataset from A1030.H, and replace it in OA$DATA_SHARE:
(changes might have been done manually, or have been made automatically
when you created a new "STANDARD" element type).
Ciao,
Simon
| |||||
| 115.2 | Release Notes not quite right? | WELCLU::63550::SYSTEM | Bruce Mason @WLO | Thu Feb 27 1992 15:40 | 9 |
Re .1: I did what you said (about commenting things out) and that ran OK.
However, I realise that all I'm changing is files that I just took out
of the saveset A1030.H anyway by following the steps in 1.8.3 (Primary
Language Upgrade from BL110). So, perhaps these steps don't quite
follow on...
Regards,
Bruce.
| |||||