Conference acadmy::tpas_notes

The following is a list of things needed and minimum versions to be in place 
for installing and running the TPAS software.

	For the LOGIC, WAREHOUSE and EXCLUDED modules:
	----------------------------------------------

		VMS	 5.4-1
		COBOL	 4.3-56
		DECforms 1.2
		NMail	 9.1
		RDB	 3.1C
		SQL	 3.1C

		Corporate Parser Rev N
		PPCS	 1.0  
		     OR
		AMP2 Satalite File

	For the WAREHOUSE modules:
	-------------------------

	   Must request a Proxy for pulling the TPAS and Stockroom data.
	   Supply the Cluster and Vax account that will be running the
	   monthly command streams in the Warehouse Module. These command
	   streams will copy the .RBR files and Import them into the
	   local databases.
	
		Mail request to: 	ACADMY::REQUEST
		Request a proxy for:	TPAS_XFER
		Supply the following:
			Cluster_alias:
  			VAX Account: 
			Site:
			Site Contact:
			Contact DTN:
			Contact E-Mail:


	For the INQUIRY module:
	----------------------

		VMS	 5.4-1
		COBOL	 4.3-56
		DECforms 1.2
		ACMS	 3.1



Note - these are all minimum version requirements

    
     Hello,
    
      The following files are missing from the TPAS logic module
    installation though they are stated in the TPAS installation guide.
    
      Diagram_exclude_mod.ps, diagram_logic_mod.ps, 
      digram_tpas.ps, diagram_warehouse_mod.ps,
      tpas_part.dis, tpas_part_memo.txt
    
     Where can I get these latest files ?
    
    
     Also, there is an error in the TPAS$IVP.COM as show below:
    
      "''tpas_disk':[tpas.com]tpas_stkrm_site_priv.SQL" +-
    
     where the "," is missing after the .SQL
    
    Rgds,
     Yan Noi
    

    
    
    Hello Lois,
    
        You stated that to install and run TPAS s/w, the minimum version
    
        for Corporate Parser is Rev N. 
    
        Here I have a concern. Currently we also run MMI which requires
    
        version Rev M . The last time I heard from Kathy Bombardier is
    
       that MMI cannot use parser of Rev N. That's why we set the
    
       parser revision to  "M" in DMDBPARAM.NCA.
    
       If TPAS is going to use rev "N" parser, how am I going to resolve
    
       this problem ? Please advise.
    
     Rgds,
    
     Yan Noi
     

 Yan Noi,

 Thank you for the feedback on the saveset. I have rebuilt it
 with the proper name for the DIAGRAM files, included the PART memo 
 files and have added it comma in TPAS$IVP. the new name is now TPAS004.A

 As for the Part Number Parser - Rev N vs Rev M. I will try to find the
 answer for you. We have developed against rev N, but if the calls and
 output is the same then it should be okay. I will talk with Malcolm Colgate,
 who now supports MMI and get his input too. Will post the findings  back 
 here.

 Lois Magni 

    
    
     Hello Lois,
    
       Thanks for your reply.
    
       However there are some errors in the kitinstal.com.
    
       The files PHYSICAL_DESIGN.PS , physical_design.txt are not found
    
       in the saveset which contains PHYSICAL-design.ps and .txt
       respectively. (Note: the hyphen and the underscore)
    
       Also note the line  
       DEFINE/SYSTEM/NOLOG   TPAS$AMPS  amp_file_location:APPIX_MPS.DAT
       in the TPAS_LOGICALS.com.  When I enter the ddua:[directory] say
       disk$tpas:[tpas] in the kit install, it will substitute the
    
       above line as
       DEFINE/SYSTEM/NOLOG   TPAS$AMPS  disk$tpa:[tpas]:APPIX_MPS.DAT
       which has a wrong syntax. in the filename.
    
      
       
       The TPAS$IVP.com is still not yet correct because the ","
       in the line "''tpas_disk':[tpas.com]tpas_stkrm_site_priv.SQL", +-
       is places wrongly. It should be before the closing "
    Rgds,
     Yan Noi
    

Yan Noi,

Thanks for doing the testing and the feedback. It has been corrected 
and a new kit created.
Regards,
Lois

 Yan Noi,

This is in response to the question of Rev M vs Rev N of the corporate parser.

I have checked with Malcolm Colgate from the MAXCIM Program Office for input on
MMI. It seems that MMI does require Rev M of the parser, BUT Rev M parser is
stored in the MMI Object Library.

So you can obtain Rev N from the CEO's Office and install it on your system.
MMI will not be effected because it has it's own version installed.
TPAS will call the Rev N version stored in SYS$SHARE and will be able to
obtain parts off of APPIX. TPAS Software takes all incoming parts and sends 
it through the parser prior to looking into either APPIX or AMPs2.

You may have a problem with MMI if you are storing your parts on MAXCIM in Rev N
and then use Rev M from MMI to find the parts. You will not have a problem
with either TPAS or MMI if you store your parts as 9 characters (non-formated) 
or Rev M format.

If you opt not to install Rev N and use Rev M throughout you may have problems
obtaining parts off of APPIX. Look in the CEODEV::PARSER Note # 45. This has a
writeup of the differences and a list of parts that will be effected. If none 
of these parts are applicable to Singapore then you may not have problem.
 
Malcolm stated that the Augusta plant uses Rev N and has MMI installed. You
may want to contact them directly. Ann MacLauchlin should be able to direct
you to the correct person there, her node is DNEAST::MACLAUCHLINA

As far as MMI calling Rev M - it looks like as issue to be addressed with
both the MAXCIM Program Office and the MAXCIM Planning SIG.

Lois

    
    
    Hello Lois,
       Thanks for your reply on note 18.7.   I need more clarification
    
       to the following questions:
    
       1) Local maxcim programs have to call TPAS routines to calculate
          the transfer price.  We have to link these maxcim programs to the
    	  TPAS library and install the programs as part of our MAXCIM
          image.  
    	   
          i) Does the call to TPAS program which calls the dec-std-12 parser 
             depend on the parser revision flag that I have
             set in the maxcim DMDBPARAM.DAT. For your info, Maxcim allows us
    	     to set the parser revision and it uses the defined parser for the
             dec-std-12 parser in its programs. 
             How does TPAS logic module specify whether to use Rev N/M ?
    
         ii) Also how do we link the local tpas programs to our maxcim and
             also the TPAS library ??
     
    
       
        2) what is the latest exact revision of the Dec-std-12 parser ?
         
              
    Thanks and Rgds,
     Yan Noi

    YAN NOI,  we are currently testing TPAS within our Receiving System
    and are having problems as no prices or status is being returned.
    When debugged, the program looks as if it is accessing
    TPAS_CALC_TRNSFR_PRC ok but... no prices.
    
    One solution could be that when we registered for PPCS, we requested
    access from our live production system and our test system and it could
    be that our test system does not have access.
    
    Have you had any such problems.
    
    
    Regards
    Josephine (AYR, Scotland)

    
    
    Josephine,
    
        I tested the tpas_calc_trnsfr_prc today.
        Earlier I faced some problems relating to the TPAS logicals. Here is
        the situation. Before running the program, I DEFINE THE TPAS LOGICALS 	
        BY @TPAS_LOGICALS. However my call to TPAS_CALC_TRNSFER_PRC returns
        the following error message:
        TPAS_RECEIVE_ERROR_MESSAGE:      "-NOSHIPLOGNAM, TPAS$SHIPPING_DATA
        Logical not defined  
        TPAS_RECEIVE_PART_STATUS_CODE:   "F"
    
        which states that the logical TPAS$SHIPPING_DATA is not defined though
        it is defined systemwide. 
        I redefine this logical under my PROCESS and
        rerun the program again. This time it works but a new error message
        from TPAS told me that the TPAS$AMPS_AVAILABLE is not defined.  To
        prevent further such errors, I redefine the tpas logicals in the process 
        level and rerun the program. This time it works but with the
        other errors which I shall describe later.
        
        The program can access the appix prices (I examine the values
        of the std unit cost and mlp through the debugger and compare the
        values with the APPIX MPS lookup which I have also installed. They
        are the same)
        I think the program works because I did not use PPCS as I
        define TPAS$AMPS_AVAILABLE = "N" and  TPAS$USE_AMPS = "Y". 
    
        However I did face some problems due to 
         the following TPAS error message trapped in the debugger:

        TPAS_RECEIVE_PART_STATUS_CODE:   "F"
        TPAS_RECEIVE_ERROR_MESSAGE:      "-PTICMMSELECT, PRICING_TABLE SQL
        Select transaction, No record found   
	
    	I suspect this is due to the PRCG_EFCTVY_END_DATE in the
    pricing_table being 17-NOV-1858 00:00:00.00 instead of null date.
    How do I rectify this problem ?  The dates are defined as this when I
    run TPAS_SITE_IMPORT_DB.COM. 
    Lois, what do you think is the problem ??7
    
    
    I need to rectify this problem before I can proceed further. Please
    help.
    Thanks.
    
    rgds,
     Yan Noi
    

    
    
    Lois,
    
       I have sent you mails on the log files of the tpas_site_import_db and
                                       
       tpas_SITE_IMPORT_STKRM_DB which show some errors when the command 
    
       file is trying to run SQL EXPORT to backup the database. This happen
    
       because I do not have the TPAS$DB for the first time. What I did is 
    
       to modify the command file to bypass this SQL EXPORT. It will then
       
       do a SQL IMPORT ... However, the SQL import contains a fatal error
    
       so that the RMU fails to get through. What I did next is to rerun
    
      the command file from RMU onwards. 
      
      I hope you can correct the two command files and release them again.
    
      Thanks,
      Rgds,
     Yan Noi
    
       
    PS. Here are the  TPAS_DB_IMPORT.LOG and  TPAS_STKRM_DB_IMPORT.LOG
    ===================================================================
IMPORT SCHEMA FROM TPAS_DB$RBR NO ACL FILENAME TPAS$DB ;
Exported by Rdb/VMS V3.1B-0 Import/Export utility
A component of VAX SQL V3.1C-0
Previous name was TPAS$BACKUP_DB
It was logically exported on 20-NOV-1992 09:00
Database NUMBER OF USERS is 50
Database NUMBER OF VAXCLUSTER NODES is 16
Database NUMBER OF DBR BUFFERS is 20
Database SNAPSHOT is ENABLED
Database SNAPSHOT is IMMEDIATE
Database BUFFER SIZE is 6 blocks
Database NUMBER OF BUFFERS is 20
IMPORTing STORAGE AREA: RDB$SYSTEM
IMPORTing table DISCOUNT_TABLE
IMPORTing table PRICING_TABLE
IMPORTing table TRNSFR_AREA_TABLE
@TPAS$ROOT:[COM]TPAS_SITE_PRIV.SQL;

SQL> 
!
SQL> !
! This command procedure grants and revokes database privileges
SQL> ! This command procedure grants and revokes database privileges
!
SQL> !

SQL> 
DECLARE RDB$DBHANDLE SCHEMA FOR FILENAME TPAS$DB;
SQL> DECLARE RDB$DBHANDLE SCHEMA FOR FILENAME TPAS$DB;
This authorization identifier has already been declared.

Would you like to override this declaration (No)? 
%SQL-F-DEFDBDEC, A schema has already been declared with the default authorization identifier
GRANT ALL
SQL> GRANT ALL
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	TO TPAS$DB_OWNER
cont> 	TO TPAS$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	TO TPAS$DB_READ
cont> 	TO TPAS$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 

SQL> 

SQL> 
GRANT ALL
SQL> GRANT ALL
	ON TABLE TRNSFR_AREA_TABLE
cont> 	ON TABLE TRNSFR_AREA_TABLE
	TO TPAS$DB_OWNER
cont> 	TO TPAS$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON TABLE TRNSFR_AREA_TABLE
cont> 	ON TABLE TRNSFR_AREA_TABLE
	TO TPAS$DB_READ
cont> 	TO TPAS$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 

SQL> 

SQL> 
GRANT ALL
SQL> GRANT ALL
	ON TABLE PRICING_TABLE
cont> 	ON TABLE PRICING_TABLE
	TO TPAS$DB_OWNER
cont> 	TO TPAS$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON TABLE PRICING_TABLE
cont> 	ON TABLE PRICING_TABLE
	TO TPAS$DB_READ
cont> 	TO TPAS$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 

SQL> 

SQL> 

SQL> 
GRANT ALL
SQL> GRANT ALL
	ON TABLE DISCOUNT_TABLE
cont> 	ON TABLE DISCOUNT_TABLE
	TO TPAS$DB_OWNER
cont> 	TO TPAS$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON TABLE DISCOUNT_TABLE
cont> 	ON TABLE DISCOUNT_TABLE
	TO TPAS$DB_READ
cont> 	TO TPAS$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 

SQL> 

SQL> 

SQL> 
REVOKE ENTRY 
SQL> REVOKE ENTRY 
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 
REVOKE ENTRY
SQL> REVOKE ENTRY
	ON TRNSFR_AREA_TABLE
cont> 	ON TRNSFR_AREA_TABLE
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 
REVOKE ENTRY
SQL> REVOKE ENTRY
	ON TABLE PRICING_TABLE
cont> 	ON TABLE PRICING_TABLE
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 
REVOKE ENTRY
SQL> REVOKE ENTRY
	ON TABLE DISCOUNT_TABLE
cont> 	ON TABLE DISCOUNT_TABLE
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 

SQL> 

SQL> 
COMMIT;
SQL> COMMIT;

SQL> 
FINISH;
SQL> FINISH;

SQL> 

SQL> 
EXIT;
    

    
IMPORT SCHEMA FROM TPAS_STKRM_DB$RBR NO ACL FILENAME TPAS$STKRM_DB ;
Exported by Rdb/VMS V3.1B-0 Import/Export utility
A component of VAX SQL V3.1C-0
Previous name was TPAS$BACKUP_STKRM_DB
It was logically exported on  9-NOV-1992 15:27
Database NUMBER OF USERS is 50
Database NUMBER OF VAXCLUSTER NODES is 16
Database NUMBER OF DBR BUFFERS is 20
Database SNAPSHOT is ENABLED
Database SNAPSHOT is IMMEDIATE
Database BUFFER SIZE is 6 blocks
Database NUMBER OF BUFFERS is 20
IMPORTing STORAGE AREA: RDB$SYSTEM
IMPORTing table STOCKROOM
@TPAS$ROOT:[COM]TPAS_STKRM_SITE_PRIV.SQL
!
SQL> !
!	This command file grants and revokes database privileges
SQL> !	This command file grants and revokes database privileges
!
SQL> !

SQL> 
DECLARE RDB$DBHANDLE SCHEMA FOR FILENAME TPAS$STKRM_DB;
SQL> DECLARE RDB$DBHANDLE SCHEMA FOR FILENAME TPAS$STKRM_DB;
This authorization identifier has already been declared.

Would you like to override this declaration (No)? 
%SQL-F-DEFDBDEC, A schema has already been declared with the default authorization identifier
GRANT ALL
SQL> GRANT ALL
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	TO TPAS_STKRM$DB_OWNER
cont> 	TO TPAS_STKRM$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	TO TPAS_STKRM$DB_READ
cont> 	TO TPAS_STKRM$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 
GRANT ALL
SQL> GRANT ALL
	ON TABLE STOCKROOM
cont> 	ON TABLE STOCKROOM
	TO TPAS_STKRM$DB_OWNER
cont> 	TO TPAS_STKRM$DB_OWNER
	POSITION 1;
cont> 	POSITION 1;

SQL> 
GRANT SELECT
SQL> GRANT SELECT
	ON TABLE STOCKROOM
cont> 	ON TABLE STOCKROOM
	TO TPAS_STKRM$DB_READ
cont> 	TO TPAS_STKRM$DB_READ
	POSITION 2;
cont> 	POSITION 2;

SQL> 

SQL> 

SQL> 
REVOKE ENTRY
SQL> REVOKE ENTRY
	ON SCHEMA RDB$DBHANDLE
cont> 	ON SCHEMA RDB$DBHANDLE
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 
REVOKE ENTRY
SQL> REVOKE ENTRY
	ON TABLE STOCKROOM
cont> 	ON TABLE STOCKROOM
	FROM [*,*];
cont> 	FROM [*,*];

SQL> 
COMMIT;
SQL> COMMIT;

SQL> 

SQL> 
FINISH;
SQL> FINISH;
    

  re: 18.8 
  ****
	TPAS call to DECSTD12 does not depend on the MAXCIM DMDBPARAM.DAT.
	The call is to the parser found in SYS$SHARE:IMAGELIB.OLB and
	is called DECSTD012_PARSER. The object found there is obtained 
	through the VMSInstall of the Corporate Parser. 
	Whereas MMI code in MAXCIM has the PARSER (REV M) contained in
	it's own MMI Library. It is called DS012_PARSER.
	Therefore, when the linker does it stuff it will resolve all
	references to DECSTD012_PARSER from SYS$SHARE:IMAGELIB.OLB and
	DS012_PARSER from the MMI library.

	To link your modified MAXCIM code with TPAS the add in: 
	TPAS$LIBRARY:TPAS_LOGIC/LIB,SYS$LIBRARY:SQL$USER/LIB 
 	to your MAX_RELINK.COM as follows:

		$LINK/NOTRACE/EXEC=MAXCIM$ROOT:[EXE]MAXCIMV4312.EXE-
			/MAP=MAXCIM$ROOT:[EXE]MAXCIMV4312.MAP -
			MAXCIM$ROOT:[LIB]MAXCIMV4/INC=MAXCIM$MAIN, -
			'MMI'MAXCIM$ROOT:[LIB]MAXCIMV4/LIB, -
			SYS$DISK:'F$DIRECTORY()'MAXCIMV4FMS.OBJ, -
	!Add in here ***
			TPAS$LIBRARY:TPAS_LOGIC/LIB, -	
			SYS$LIBRARY:SQL$USER/LIB,    -
			MAXCIM$ROOT:[LIB]MAXLIB/OPT

	I have not tested this. I believe it should work. Ayr will be
	tying TPAS into MAXCIM also. Once Josephine is done testing
	she will be able to verify the exact link.

	As for the latest version of the parser it is REV N V1.0A
	which was released 16-Oct-1992. The location and relase notes can
	be found in MILPND::PARSER notes conference.

Yan Noi, Josephine,

The following is in response to 18.9,.10 and .11


.9	Running TPAS with PPCS. The only things that need be done is
	that PPCS needs to be installed on the Cluster that TPAS will
	be running on. The PPCS logicals APPIX$PPCS_BSRV and
	APPIX$PPCS_PSRV need to be defined system wide. There is no
	need for proxies on either end as PPCS is driven off Badge
	and password.


.10	Yan Noi, you are correct in defining the logicals at PROCESS 
	level. We will be modifying our code to look at ALL levels
	of logicals in the same order as VMS. That way, sites will
	be able to define the logicals as they want. Will put this
	info into the release notes when releasing the change.


	The EFCTVY_END_DATE is causing problems in our test site (KAO) also.
	We are working on that now. It will be in the next release 
	kit. We did not experience that problem here so we are looking
	at the import/export and RMU load/unload process to see if
	it changes the data.
	If you want to continue testing - change the END_DATEs on both
	the Pricing and Discount tables to sometime in the future, 30 Dec 1994
	is a good date :)




.11	As for the IMPORT and COPY command streams,  those have been 
	corrected and will be in the next release.

	Sorry for any inconveiences - This is the problem of releasing
	software prior to alpha/beta test completion. But thanks for all
	the feedback.
lois

    Hello Lois,
    
       Re to 18.13,
    
         I managed to modify the eff end date but this time another error
    
         occurs due to CMM.. the calculated MLP factor < 1 for part type =
         "RAW". In order to let it goes through, I set the MLP factor to be
         say 1.2, only then the TPAS logic module returns me a succesful
         flag and messgae. Again it's either the data  in the database is
         not valid or the TPAS logic module doesn't handle this properly.
         Please comment.
    Rgds,
     Yan Noi
    

Yan Noi,

The MLP_CALC_FACTR < 1  IS an error in the database. We knew these
were there, and we do have a process in which these will not be distributed.
The database you have is the preliminary data TAX create to see the impact
to the transfer prices.

Lois

	A new pre-release kit available to pull. 	
	TPAS005.A to be installed with VMS Install.

	Contains:
		the fix when EFCTVY_END_DATE IS NULL.
		The fix to the COPY and IMPORT command 
		   streams as noted by Yan Noi.

    Lois
    
    Today I installed the latest kit TPAS005.A and recompiled and linked my
    test program with the new modules.
    I still get the same undefined symbols as a stated in note 14.3
    
    %LINK-W-NUDFSYMS, 2 undefined symbols:
    %LINK-I-UDFSYM,         APPIX$PPCS_END_LIST_BOM
    %LINK-I-UDFSYM,         APPIX$PPCS_FIND_PART
    %LINK-I-UDFSYM,         SQL$$CLOSE_CURSORS (Weak Reference)
    %LINK-I-UDFSYM,         SQL$END_TRANSACTION (Weak Reference)
    %LINK-I-UDFSYM,         SQL$GA_CUR_MODCTX (Weak Reference)
    %LINK-I-UDFSYM,         SQL$GA_IMPLICIT_TXN_HDL (Weak Reference)
    
    I think the first 2 undefined symbols are part of the AMPS2 software
    which we don't have yet.
    Could you please check this and let me know were I can get this
    software if you agree with me that it is needed.
    
    Thanks,  
    		Rinus Jansen 

Just to post a follow through. Rinus and I have identified the link errors
he was receiving. NJO has not installed PPCS, therefore the lines:

    %LINK-W-NUDFSYMS, 2 undefined symbols:
    %LINK-I-UDFSYM,         APPIX$PPCS_END_LIST_BOM
    %LINK-I-UDFSYM,         APPIX$PPCS_FIND_PART
   
came up. But because NJO is NOT USING PPCS, this will not cause a problem. 
These are only link "Informationals" and will not effect the creation of the 
EXE. They would cause a problem if Rinus set the TPAS$USE_AMPS logical to
'N' indicating to the code to use the PPCS calls. But when TPAS$USE_AMPS
is set to "Y" these calls are never made.

    Lois,
    
    After some testing with the TPAS logic module we noticed that the
    performance of the module call is bad. To avoid the impact of the local
    programs, I tested the TPAS_FAST procedure with 32 TPAS calls. It
    needed at least 6 minutes to complete. This results in an average of >
    10 seconds per TPAS module call. Could you please let me know if this
    is a known problem, or is it only at our site.
    
    Rinus Jansen

    Lois,
    
    This a an adjustment of reply 18.19.
    During the TPAS_FAST process I looked to the databases with RMU/SHOW
    STATISTICS and I noticed that the number of records fetched on the TPAS
    database was more than 19000 records and on the TPAS_STKRM database was 
    more than 5000 records. Is it possible that the indices to access the
    tables are not used ? 
    
    Rinus

A new kit is available on AWARD::TPAS$PUBLIC:TPAS006.A.
This kit includes the following changes:

	1) Logical Name Table Search to allow sites to define
 
	   TPAS$USE_AMPS, TPAS$AMPS_AVAILABLE, TPAS$SHIPPING_DATA
	   TPAS$DISPLAY_W_ERRORS and TPAS$DISPLAY_I_ERRORS

 	   At PROCESS, JOB, GROUP or SYSTEM level.
	   The search is done in that order (VMS order).


	2) Reformatted the TPAS_TRANS_STATUS so that if the 
	   FACILITY code is less than 6 characters it would be
	   space filled. 
	   So 
		%SPWY-F-NOSERVER, connection to remote server not available
	    will now be returned like this:	
		%SPWY -F-NOSERVER, connection to remote server not available

	   The TPAS_TRANS_STATUS is defined as a group field:
		10 TPAS_TRANS_FACILITY_MSG	PIC X(6).
		10 TPAS_TRANS_DASH1		PIC X(1) VALUE "-".
		10 TPAS_TRANS_PART_STATUS_CODE  PIC X(1).
		10 TPAS_TRANS_DASH2		PIC X(1) VALUE "-".
		10 TPAS_TRANS_ERROR_MESSAGE	PIC X(71).


	3) If TPAS$DISPLAY_W_ERROR is "N" it will no longer show
	   the warning messages if running in non-interactive mode.



 These should be all the open issues that have been found. We will be working
 on performance concerns using PCA. We will be doing modifications to increase
 performance once the areas are found.

    Lois,
    
       I have reinstalled TPAS using TPAS006.A. However the definitions
      for  TPAS$DISPLAY_W_ERRORS and TPAS$DISPLAY_I_ERRORS are still defined as
      "0" (not "N") if I answered "N" to the questions . 
      Please refer to the log below:
    
     
    Rgds,
     Yan Noi
    
%CREATE-I-EXISTS, DISK$TPAS1:[TPAS.MAIL] already exists
%CREATE-I-EXISTS, DISK$TPAS1:[TPAS.EXE] already exists
* Display all WARNING messages from Logic Module at the terminal [Y]? N
* Display all INFORMATIONAL messages from Logic Module at the terminal [Y]? N
* Will you be using PPCS or AMP2 (P/A): A
* Enter the location of APPIX_MPS.DAT (ddua:[directory]): DISK$TOPAS    PAS: 1:[AMP2]
* Shipping data: Stockroom, Plant mnemonic, or Transfer area code (S,P,T): T

    1       $ !                 T P A S -  L O G I C A L S . C O M
   52       $ DEFINE/SYSTEM/NOLOG       TPAS$DISPLAY_W_ERRORS 0 
1 substitution
   48       $ DEFINE/SYSTEM/NOLOG       TPAS$DISPLAY_I_ERRORS 0 
1 substitution
   15       $ DEFINE/SYSTEM/NOLOG/TRANS=CONCEALED       TPAS$ROOT  DISK$TPAS1:[T

PAS.]
1 substitution
   34       $ DEFINE/SYSTEM/NOLOG       TPAS$AMPS       DISK$TPAS1:[AMP2]APPIX_M

PS.DAT
1 substitution
   55       $ DEFINE/SYSTEM/NOLOG       TPAS$USE_AMPS        Y
1 substitution
   60       $ DEFINE/SYSTEM/NOLOG       TPAS$AMPS_AVAILABLE  N
1 substitution
   65       $ DEFINE/SYSTEM/NOLOG               TPAS$SHIPPING_DATA   T
1 substitution
$1$DIA0:[SYS0.SYSUPD.TPAS006]TPAS_LOGICALS.COM;6 69 lines

No further questions will be asked during the installation.  Informational
    

The Development Cluster for TPAS has just been upgraded to the attached
versions of software. The software has been tested, although some changes
will take place in the SQLMODs for effeiciency, all software is working. 

	For the LOGIC, WAREHOUSE and EXCLUDED modules:
	----------------------------------------------

		VMS	 5.5-2 
		COBOL	 5.0
		DECforms 1.4
		NMail	 9.3
		RDB	 4.0B
		SQL	 4.0B
		Corporate Parser Rev N
		PPCS	 1.0  
		     OR
		AMP2 Satalite File

	Additional  For the INQUIRY module:
	----------------------------------
		ACMS	 3.2

re: -1

�      TPAS$DISPLAY_W_ERRORS and TPAS$DISPLAY_I_ERRORS are still defined as
�      "0" (not "N") if I answered "N" to the questions . 

The KITINSTAL is being corrected to correctly change the TPAS_LOGICALS.COM
to:
    	TPAS$DISPLAY_W_ERRORS  Y or N
	TPAS$DISPLAY_I_ERRORS  Y or N

instead of 1 or 2. Will be included in TPAS007.A when released.

Lois

    Lois,
    
    We tried to run the TPAS_XCLDD.EXE on our local environment and it
    returned the following error message
    
    TPAS XCLDD Database Update Application starting.
    %SYSTEM-F-ACCVIO, access violation, reason mask=FD, virtual
    address=03C00000, PC
    =00000000, PSL=00000000
    %TRACE-F-TRACEBACK, symbolic stack dump follows
    module name     routine name                     line       rel PC   
    abs PC
    
    TPAS_XCLDD      CHECK_FORMS_STATUS                         00000036 
    0002B7FD
    TPAS_XCLDD      TPAS_XCLDD                                 00000289 
    0002B689
    
    When running an older version dated 23-oct-1992 no error occurred.
    
    Regards, Rinus Jansen

 Rinus,

 Some reaction - Just off the top of my head:
 No changes have been done to the excluded module software since
 the release. Check your ACLs, the TPAS$XCLDD_DB, TPAS$DB and TPAS$STKRM_DB
 all have ACL Protections now. Look at TPAS_INSTALL.TXT, there is an 
 explaination of them in there. Make sure the account running TPAS_XCLDD.EXE 
 has TPAS$DB_READ, TPAS_XCLDD$DB_WRITE AND TPAS_STKRM$DB_READ Rights IDs on 
 their account.

 Another thing - Have you updated RDB since the initial build of TPAS$XCLDD_DB ?
 If you have did you convert the database ?

 I will look further on this end. Let me know if either of these were the
 problem.  
 Lois

  I got the same error as mentioned in 18.25.  I 
  checked the Rights Identifier and the protection
  of TPAS$XCLDD_DB, TPAS$DB and TPAS$STKRM_DB, 
  everything seems okay.

  Rinus,

  How can you solve the problem?

  Best regards,
  Eric Y.

Eric,

I have been working with Rinus on this. We believe it may be due to the 
fact that our development cluster has just upgraded to DECForms 1.4. 
JGO is running DECForms 1.3 and the TPAS_XLCDD.EXE was re-built under 
DECForms 1.4.  I am waiting for JGO to upgrade to 1.4 to see if this
is the problem.

Are you running DECforms 1.3 also? If so, can you upgrade to 1.4 and see if 
it is the cause, as we have tried all other avenues.

Lois M.

   Lois,

   After upgraded DECform from version 1.3 to version 1.4, we can execute
   TPAS_XCLDD.EXE without any error.

   Thanks,
   Eric Y.

    Lois,
    
    Perhaps it is a good idea to remove the TPAS_GET_LOCAL_COST out of the
    TPAS_LOGIC.OLB which is included in the kit. It is only a dummy 
    and it is possible that we forget to replace this module by the local 
    developed one.
    If you remove it out of the kit, we always have to use our local module
    and we can't get confused.
    
    Regards, Rinus Jansen

    Lois,
    
    We noticed that it is not enough to set the SELECT priv on the database
    schema to the users which only need read access. We still got a
    privilege error on the set transaction statement (STKRMSETTRNS error).
    I checked the RDB manuals on this, and the only priv where I can think
    of is the DISTRIBTRAN priv which is needed to start a distributed
    transaction. After granting this DISTRIBTRAN priv to the schemas, we
    were able to proceed our test without the privilege error.
    Do we realy need to grant this priv to the database schemas?
    
    Rinus Jansen

Rinus,

re: -.2

You are not the only organization that has called with the TPAS_GET_LOCAL_COST
problem. Sending it already in the TPAS_LOGIC.OLB allows sites to be able to
run TPAS_DEMOSITE without having to write any code. Also, with the 
standard cost of 100.70, it returned tells me exactly what the problem is if 
someone calls.


re: -.1

On the RDB - DISTRIBTRAN priviledge. As we had developed everything under 
v3.1C RBD/SQL we did not include this privledge. I worked with ACO (GIA)
last week and found this. I have modified the kit to check the version
of SQL and move the appropriate file into place. (The kit announcement -
V1.0 - is forth coming this week. ) 

With V3.2 RDB and under the TPAS$DB_READ and TPAS_STKRB$DB_READ only need the
SELECT privledge in the database.

With V4.0 RDB and over the TPAS$DB_READ and TPAS_STKRB$DB_READ need both the
SELECT and DISTRIBTRAN privledges in the database.


The V1.0 kit now includes :
TPAS_SITE_PRIV_V3.SQL  TPAS_STKRM_SITE_PRIV_V3.SQL  TPAS_XCLDD_SITE_PRIV_V3.SQL
TPAS_SITE_PRIV_V4.SQL  TPAS_STKRM_SITE_PRIV_V4.SQL  TPAS_XCLDD_SITE_PRIV_V4.SQL 

The KITINSTAL checks to see the version RDB installed. If V3 the correct
.SQL files are move to production and the V4 files are copied for future use.
If V4 RDB is installed then the V4 files are moved to production and the
V3 files are deleted.

Lois

   In TPAS_XCLDD.DIS there has a mail address PWDML::TPASMAIL, the Excluded
   Module suppose will send a memo to this address to notify Corporate Tax
   of local tax table modification.  However, I can't found the node PWDML 
   in our network database.  Is there anyone know the physical DECnet 
   address of this node?

   Best regards,
   Eric Y.

�   In TPAS_XCLDD.DIS there has a mail address PWDML::TPASMAIL, the Excluded
�   Module suppose will send a memo to this address to notify Corporate Tax
�   of local tax table modification.  However, I can't found the node PWDML 
�   in our network database.  Is there anyone know the physical DECnet 
�   address of this node?
 

Eric - Quite right. The Node should be POWDML. I have correct the saveset (V1.0)
       Modify your TPAS_XCLDD.DIS if you have already pulled the kit.

       Lois

    Lois,
    
    I have just installed TPAS V1.1 today.  It seems to have gone ok except
    for the following
    
    1.  some files were set with the owner of [CC_0821,SYSTEM] which is
        the account I was installing from (not SYS$UPDATE).  It appears to
        have been files in [.COM], [.DOC] and [.EXE].
    
    2.  testing XCLDD program , PRICING and DISCOUNT, I decided to exit
    	the data input screen using PF1 Q.  This gave the choice to 
    		CHANGE ENTRY ? YES ADD  MODIFY  MAIN MENU  CONTINUE.
    
        The only option to work was MAIN MENU.  Are the other options
    	invalid at this point?
    	Also happended in the DISCOUNT as well.
    
    Question -  in future versions of TPAS will the logicals , copy &
    import command procedures be overwritten (other than there are
    changes)?  Just ask as it means recustomising the procedures to local 
    requirements.
    
    Thanks
    Cathy
    
       
    
                                         

Cathy,

	1) Thanks for the input on the kit install protections.	
	   I'll look into it.

	2) PF1 Q - is quit and that's all you can do is quit

	3) Future releases - haven't given much thought here. Thanks for
	   the input though will take it into consideration.

Lois

    Lois,
    
    We installed the latest TPAS kit V1.1 and linked our software with the
    TPAS software just to be sure to use the latest software.
    Now we see a new undefined symbol COB$UPPER_CASE and we expect that
    this has to do with the different Cobol versions. We are using Cobol
    V4.4 at the moment. I hope that this symbol will not cause any problem
    within our environment. So please don't use any new features of Cobol
    which are not available in previous versions.
    
    Regards Rinus Jansen.