| Marga,
1. The command procedure TPAS_LOGICALS.COM has a typing error in the
declaration of the logical TPAS$AMPS.
�� What type of typing error? This has not not changed since Nov 1992.
�� The location of the APPIX_MPS.DAT file does get updated via a response
�� to a question in VMSInstall. Could this have the typo ?
2. We're trying to create the new error NOTUNQBUSTYP on the testsystem,
but we don't succeed in doing this. Can you please give an example of
how this error is created, so we can test our software?
�� Unless a site uses SQL, RDO or another means to update TPAS$DB TRNSFR_AREA
�� table directly this error should never be seen. What this error is
�� saying is that there are two records on the TRNSFR_AREA_TABLE that have
�� the same TRNSFR_AREA_CD but different BUSNS_TYPE_CD. Then to test it
�� if you set the TPAS$SHIPPING_DATA to T and ship to the TRNSFR_AREA_CD
�� in error, this error will be returned.
�� example: PLANT_CODE TRSNFR_AREA_CD BUSNS_TYPE_CD
�� JG JGO MAN
�� FG JGO SAL
�� Then set TPAS$SHIPPING_DATA = T
�� run TPAS_DEMOSITE and ship to JGO
��
3. The command procedures for copying the new databases make use of
serial number files. In the Physical Design it is stated that these
files will be included in the installation kit. However, they're not
in there. Did you forget them?
�� These were not forgotten. The command streams were written to create
�� the TPAS_SERIAL.DAT and TPAS_STKRM_SERIAL.DAT file in TPAS$COM if
�� not found. That way the first time through these files are created for you.
�� So the log will look something like this:
��
�� $ FILE_NAME_DAT=F$SEARCH("TPAS$COM:TPAS_SERIAL.DAT")
�� $!
�� $ SHOW SYMBOL FILE_NAME_DAT
�� FILE_NAME_DAT = ""
�� $!
�� $ IF FILE_NAME_DAT .EQS. ""
�� $ THEN
�� $ TPAS_SERIAL_NUMBER_DAT="0000"
�� $ ELSE
�� $ ENDIF
�� !
�� $ SHOW SYMB TPAS_SERIAL_NUMBER_DAT
�� TPAS_SERIAL_NUMBER_DAT = "0000"
�� $ SHOW SYMB TPAS_SERIAL_NUMBER_DB
�� TPAS_SERIAL_NUMBER_DB = "0054"
�� $!
�� $! Comaprison of Both serial Numbers
�� $!
�� $ IF TPAS_SERIAL_NUMBER_DB .LES. TPAS_SERIAL_NUMBER_DAT
�� $ ELSE
�� $ GOTO GD005
�� $ GD005:
�� $!------
�� $ GOTO ST010
�� $
�� .
�� .
�� .
�� $ SHOW SYMB TPAS_SERIAL_NUMBER_DB
�� TPAS_SERIAL_NUMBER_DB = "0054"
�� $ IF TPAS_SERIAL_NUMBER_DB .NES. ""
�� $ THEN
�� $ OPEN/WRITE OUTPUT_FILE TPAS$COM:TPAS_SERIAL.DAT
�� $ WRITE OUTPUT_FILE TPAS_SERIAL_NUMBER_DB
�� $ CLOSE OUTPUT_FILE
�� $ ENDIF
�� $!
�� $ PURGE/LOG TPAS$COM:TPAS_SERIAL.DAT
�� %PURGE-I-NOFILPURG, no files purged
�� $ TYPE TPAS$COM:TPAS_SERIAL.DAT;
�� 0054
�� $!
�� $!
�� $ GD020:
�� $
|
| Lois,
The TPAS_LOGICALS.COM appeared to be oke. If you enter a logical name
instead of a directory name during the installation, you just should
not forget to enter a ":" behind the logical name. My mistake.
One more question: we did the installation of the TPAS save set twice,
and both times we entered "YES" to the question if we wanted a new
XCLDD database to be created. Both times this didn't happen (at least I
can't find it anywhere). Do you have any idea what may have gone wrong?
thanks and regards,
Marga
|
| Marga,
You are correct on the TPAS$XCLDD_DB not being created. I was about
to send the attached note out - but will also post it here.
******* TPAS V2.0 and TPAS$XCLDD_DB *******
The VMSInstal command procedure for TPAS V2.0 has an error
in it that has been brought to my attention. The TPAS$XCLDD_DB
is NOT created even when user responds "Y" create. A new
KITINSTAL.COM and Kit (v2.1) will be created.
YOU DO NOT NEED TO INSTALL THIS UPGRADE - DO THE FOLLOWING:
To create a TPAS$XCLDD_DB after you have installed TPAS V2.0
go into SQL and execute TPAS_XCLDD_RDB.SQL. Ensure your TPAS
Logicals are set up.
$ @TPAS$COM:TPAS_LOGICALS.COM
$ SQL == "$ SYS$SYSTEM:SQL$"
$ SQL
SQL> @TPAS$COM:TPAS_XCLDD_RDB
SQL> @TPAS$COM:TPAS_XCLDD_SITE_PRIV.SQL
If there are any questions or concerns send mail to ACADMY::QCA_ADMIN
Regards,
Lois M. Magni
|