| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1828.1 | Restore the original version of profile .dat and .fdl | GIDDAY::SETHI | Man from Downunder | Sun Nov 22 1992 22:43 | 15 |
| Hi,
Did you have an ASSET install on your system ? I know of one asset
that increased the size of profile.dat by 1 byte, unfortunately I can
not remember the name of the asset !
Before doing the upgrade you should have saved the PROFILE.DAT and the
.FDl's and replaced them with the uncustomized versions. That all I
can rememeber maybe someone else can add a bit more.
The pre-installation checks may have something on it.
Good luck
Sunil
|
| 1828.2 | Agreed! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Nov 23 1992 11:19 | 16 |
| The CART run (you did do that didn't you??!!) should have told you that
you'd customisedthe PROFIL forms. Unless whatever the ASSET is that
Sunil mentioned didn't use Customisation Management to change the
forms...
In any case, Sunil's advice is sound. Remove any customised versions of
the PROFIL forms or FDLs and do the postinstall again.
I'm slightly confused by one of the error messages you displayed,
perhaps they just got cut off in thelog:
<<%OA-E-DBEOR, Error opening V24_PROFIL - File A1SYS:[ALLIN1.DATA_SHARE]V2;
I assume the "V2" at the end was actually V24_PROFIL.
Graham
|
| 1828.3 | | ISTWI1::YEGEN | | Mon Nov 23 1992 14:46 | 22 |
| Graham,
Thank you very much for your reply. I discovered that profile.dat had a
Record format: Fixed length 1943 byte records, which should have
been 1944. And my colague told me that he had converted the profile.dat
after he had installed LAP-1 (which was an asset and it was written as
the post installation task in the manual). So I found the original
profile.fdl (with record size=1944) and made a
CONVERT/FDL=PROFILE.FDL/pad=" " V24_PROFILE.DAT PROFILE.DAT
and run the postinstallation again and it worked out.
But I really do not know hoe ALL-IN-1 have read profile records until
that time with a different record size in profile.fdl and profile form.
Best regards,
And thank you very much as usual since this have been maybe 1000th help
that I got from you.
Tansu YEGEN
|
| 1828.4 | Mobilizer too? | SIOG::T_REDMOND | Thoughts of an Idle Mind | Mon Nov 23 1992 15:19 | 8 |
| LAP-1 forced people to convert the profile to 1943 byte records?
Sounds like they a program with fixed data structures to map the
profile! But it's also a little extreme to tell people to convert
backwards to 1943 (from V2.4's 1944 size) after an upgrade has already
converted a file. Does Mobilizer (the descendent of LAP-1) include
this anti-social behaviour too?
Tony
|
| 1828.5 | | ISTWI1::YEGEN | | Mon Nov 23 1992 15:57 | 12 |
| What a pity but yes, because my colague also checked also the
profile.fdl which was in the LAP-1 dirctory and which had a record
size of 1943. I had to spend the whole Sunday until I found that.
But now I have some other problems, especially related to printers
which do not print turkish any more. Can I get in contact with somebody
who is willing to help me, because I am lost in printer tables and
ALL-IN-1 v3.0.
Thank you very much for your help,
Tansu YEGEN @TWI
|
| 1828.6 | New record size check in V3.0 | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Nov 23 1992 17:11 | 9 |
| Presumably LAP-1 is hardwired to support the V2.3 profile size...
The reason this worked in V2.4 is that we added a new check in V3.0
that would signal an error if the record size that we got from RMS
wasn't the same as the entry form defined.
Graham
PS Glad to be of help!
|
| 1828.7 | Mobilizer documentation wrong | KERNEL::HOULDINGJ | Jill Houlding - Back in Basingstoke | Wed Nov 25 1992 10:54 | 18 |
| Yes there is a danger that the PROFILE.DAT record size might be wrong
because of Mobilizer (or LAP-1) installation.
The Moblizer Installation Guide is far from clear in this area:
instructions are included which indicate that PROFILE.DAT should
be (RMS) converted using a .FDL file provided with the Mobilizer kit.
The problem is that this .FDL file is only compatible with ALL-IN-1 V2.3
AND there is no need for the conversion on versions of ALL-IN-1 later
than this.
(The conversion is to create the VMS username as a secondary key to
PROFILE.DAT - this is standard practice on ALL-IN-1 versions since V2.3
These instructions should be changed in the future.
Cheers
Jill
|
| 1828.8 | Data file <=> FDL | DUBSWS::EIJS | | Wed Nov 25 1992 17:25 | 11 |
|
Hi Tansu,
I don't think it is strange the access to PROFIL never brought any
errors, as (as far as I know) an FDL in the ;;.FILE;; directive is only
used when creating the data file. Once done, it doesn't need it any
longer. So, they're related, much not as much/strict as you think.
Ciao,
Simon
|