[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Transfer Price Administration System |
| Notice: | Conference has moved to ACADMY::TPAS_NOTES |
| Moderator: | ACADMY::MAGNI |
|
| Created: | Wed Jul 01 1992 |
| Last Modified: | Fri Mar 21 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 102 |
| Total number of notes: | 459 |
49.0. "TPAS II Kit" by AWARD::MAGNI (IM&T - 223-9837) Tue Dec 13 1994 15:30
From: POWDML::POWDML::MRGATE::"A1::FAHY.EAMONN" 13-DEC-1994 15:00:01.72
To: AWARD::POOJA,ESGOPS::JCURLEY,AWARD::MAGNI,AWARD::MAGNI
CC:
Subj: TPAS II Software Availability 1
From: NAME: Eamonn Fahy @MSO
FUNC: CORPORATE TAX
TEL: 223-9194 <FAHY.EAMONN AT A1 at POWDML at PKO>
To: See Below
CC: See Below
The TPAS II software has successfully concluded the pilot test phase,
and is now available to all implementation sites worldwide.
The installation kit has already been sent to eight sites, other
sites ready to proceed with the technical installation should follow
the attached instructions from Lois Magni. ( Attachment B)
All implementation sites should now be in a position to finalize their
implementation plans, complete the changes to their local systems needed
to interface with TPAS II, and test those interfaces before going live.
In order to facilitate coordination of the overall worldwide implementation
effort I would ask that you provide me with a high level summary of your
implementation plan. (Suggested format is as set out in Attachment A).
Thank you all for your participation to-date, and I look forward to
supporting you with the implementation effort.
Regards
Eamonn
ATTACHMENT:A
TPAS II SUMMARY LEVEL IMPLEMENTATION PLAN
DATE:_________
SITE:_____________ PROJECT MANAGER:____________________
START END
TPAS IMPLMENTATION TASKS DATE DATE STATUS
--------------------------------- ------- ----- ------------------
Write Preliminary Analysis of site
systems to determine:
Where calculation of Transfer
Price is needed.
Write Functional Analysis of site
systems to determine:
How TPAS Calls will be integrated.
Where TPAS Calls will be integrated.
How TPAS Errors will be handled.
How input data will be made available.
How Logicals will be set up.
Will AMPs or PPCS be used.
Write & implement
Physical Design at site
to describe in detail:
TPAS Call integration.
TPAS Error handling routines.
Input data.
System logical set up.
AMPs or PPCS installation.
Implementation of TPAS Monthly Streams.
Write Implementation Plan.
Creation of TPAS Environment.
Write site Support Documentation.
Write Test plan.
Create test area and test cases.
Perform User integrated testing.
Review and rework/accept test results.
Perform implementation.
ATTACHMENT:B
From: AWARD::MAGNI "Lois Mallalieu Magni / IM&T / 237-5548 09-Dec-1994 1511" 9-DEC-1994 15:22:03.52
Subj: TPAS030.A Kit - TPAS II
The TPAS II VMSInstal kit
o Fill out the attached form and send it to ACADMY::QCA_ADMIN.
The kit requires a secure area to be copied to, please
set up the appropriate proxy area.
o The last page of the form needs to be sent to SALEM::ACCOUNTS if you
need a proxy set up for TPAS_XFER. For those sites moving up from TPAS I
to TPAS II this will not be required if you are copying the TPAS Files
from the same location.
All new TPAS Users will be required to obtain the proxy to copy the
monthly update files.
o The saveset includes the installation instructions. Prior to running
INSTALL review the instructions. Extract them from the saveset with
the following command:
BACKUP/SELECT=TPAS_II_INSTALLATION_DOC.PS -
TPAS030.A TPAS_II_INSTALLATION_DOC.PS
Page 1
Attached, you will find an APPIX/TPAS Registration Form. Please read the
structions very carefully, and fill out accordingly.
The following is information on charges for APPIX Products and Services.
The APPIX Parts and Product Reference organization has been instituting a
high-level charge-out method for services during FY93. The client
currently participating in this high-level charge-out method is
Engineering. We have begun discussions with other organizations to use high
level funding in FY94.
High-level funding involves totaling up the APPIX accounts and products
utilized by each client's cost center, taking the yearly total, dividing by
four, and charging identified higher-level cost centers for the combined
account/product charges. This process is done on a quarterly basis via a
Standard Journal Voucher.
This will alleviate the need for each Part & Product Reference
account/product user to be charged directly, but the function as a whole
will receive the charge.
Manufacturing cost centers are not being charged for the use of APPIX/TPAS
products and services. These charges are being absorbed by the Part and
Product Reference organization.
For clients not mentioned above individual accounts/products will be
charged directly to the cost center specified on the registration form.
If you have any questions, please send mail to ACADMY::QCA_ADMIN, or call
the Part & Product Reference Support Hotline @ DTN 285-3999, or
from outside Digital (603)894-3999.
Thank you,
Part & Product Reference Support
MSO2-2/H11
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPIX/TPAS REGISTRATION FORM Page 2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PART & PRODUCT REFERENCE APPLICATION SUPPORT
This form is used to obtain the APPIX/TPAS software.
Please complete this form and forward it to your Cost Center Manager.
Your Cost Center Manager should then send the completed form back to
ACADMY::QCA_ADMIN.
Upon receipt of your completed registration form, the software will
be sent.
Please be aware that your APPIX/TPAS account is for your exclusive use, and
your ACADMY password is confidential. Corporate Security guidelines clearly
prohibit "sharing" any VAX account.
Questions? Write to us at ACADMY::QCA_ADMIN or call the Part & Product
Reference Application Hotline at DTN 285-3999, or outside dial-in
(603)894-3999.
-------------------------------------------------------------------------------
CUSTOMER INFORMATION
CORP. BADGE NUMBER:__________________ COST CENTER:________________________
FIRST NAME:__________________________ CC MGR BADGE NUMBER:________________
LAST NAME:___________________________ CC MGR FIRST NAME:__________________
MAILSTOP:____________________________ CC MGR LAST NAME:___________________
PHONE (DTN):_________________________ CC MGR MAILSTOP:____________________
NODE NAME:___________________________ CC MGR PHONE (DTN):_________________
NODE USERNAME:_______________________ CC MGR NODE NAME:___________________
CC MGR NODE USERNAME:_______________
Is your facility in the United States? ___Yes ___No
If no, please enter General Ledger Number & location code here ___________
Is your cost center part of APA___, Europe___, or U.S.___ ?
All APPIX/TPAS documentation is in Postscript format. Once your account has
been established we provide you with information on how to copy this
documentation.
===============================================================================
AUTHORIZATION:
COST CENTER TO BE BILLED:_____ GROUP NAME:____________________________
ORGANIZATION YOU REPORT INTO:__________________(i.e., Mfg, Eng, D.S., etc.)
CC MANAGER:_________________________________COST CENTER:______DATE:_______
Authorization of CC Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPIX/TPAS REGISTRATION FORM Page 3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=============================================================================
Please return completed form to: | FOR INTERNAL P&P REFERENCE USE ONLY:
|
ELECTRONICALLY |
ACADMY::QCA_ADMIN | Contract Number:________________
OR |
INTERNALLY | Badge Number : _________________
PART & PRODUCT REFERENCE |
APPLICATION SUPPORT | Date Added: ____________________
|
MSO2-2/H11 | Products: ______________________
|____________________________________
The following are Extracts, Server Products or VMSInstal kits. In order
to receive these files or Kits, you must have your System Manager set up
a proxy for the receiving account. Please provide your system manager with
the following information:
All Extract products will come from: ACADMY::APPIX_PROD
Where do you want data/kit sent?
NODE:_________ DEVICE:______________________ DIRECTORY:____________________
(System Managers please note -- to comply with Corporate Security mandates,
we cannot send Extract files to DECNET areas.)
Please include the following contact information for your system manager
in case proxy issues arise:
NAME:_________ VAXMAIL ADDRESS:____________________ DTN:___________________
Date you want to start receiving data :______________
PRODUCT DESCRIPTION ANNUAL COST
-------------------------------------------------------------------------------
XXX Transfer Pricing (TPAS) Distributed KIT NO CHARGE
---
Note: PPCS KIT and/or AMP2 is required for TPAS.
Please complete the last page for setup of proxy on ACADMY.
This is needed by sites running the local TPAS to obtain
the data files monthly.
___ Transfer Pricing (TPAS) Inquiry KIT NO CHARGE
Note: ACMS is required for the TPAS Inquiry kit.
___ TPA Transfer Pricing (TPAS) Inquiry ACCESS NO CHARGE
___ AMP2 APPIX Master Parts Satellite System PER INSTALLATION NO CHARGE
___ Part and Product Client Server - KIT NO CHARGE
___ PPCS Part and Product Client Server - Registration NO CHARGE
Page 4
INFORMATION SECURITY PROGRAM
ACCOUNT OWNERSHIP RESPONSIBILITIES
1) Never use easily guessable passwords such as family members, pets,
hobbies, projects, etc.
2) Your passwords should not be shared with anyone.
3) Passwords should never be transmitted over the network.
4) Users with accounts on multiple systems should ensure that their
password for each account is unique.
5) When logging in, do not let anyone observe you entering your
password.
6) Report any login failure messages you receive that you know you
did not generate. These messages will come up when you enter your
account. Also, be sure to read last login messages. If you feel a
security violation has been committed, please call your system
manager.
7) Do not give dial up access numbers to anybody internal or external
to DIGITAL. If you need dial up numbers for your own use, contact
IM Technical Support HOTLINE @DTN 285-3999.
8) Never leave your terminal logged on when absent from your office.
9) I have, or will, read Personnel Policies and Procedures 6.06
(Confidentiality), 6.24, 6.54 and 8.03.
10) Accessing any account or area without permission is subject to
disciplinary action.
11) If there are no logins to the account for 60 consecutive days at
any time, the account will be disabled. If there is no attempt
to have the account re-established after an additional 30 days,
the account will be removed.
********************************************************************************
To Be Signed by Account Requester
I have read and understand my responsibilities as an account owner.
....................................... ..........................
NAME DATE
*** DIGITAL INTERNAL USE ONLY***
PROXY ACCESS REQUEST FORM
COMPLETE AND SEND TO:
All-In-1 - ACCOUNTS @ NIO VAXmail - SALEM::ACCOUNTS
+----------------------------------------------------------------------------+
| +--+ +--+ |
| |XX| REQUEST FOR NEW PROXY ACCESS | | DELETE CURRENT PROXY ACCESS|
| +--+ +--+ |
+----------------------------------------------------------------------------+
| REQUESTER INFORMATION: |
| |
| NAME:_________________________________________ BADGE #:___________________|
| |
| ORGANIZATION:_________________________________ COST CENTER:_______________|
| |
| DTN:__________________________________________ MAIL STOP:_________________|
| |
| ELECTRONIC MAIL ADDRESS:___________________________________________________|
+----------------------------------------------------------------------------+
| SYSTEM YOU LOG INTO (SYSTEM YOU ARE COMING FROM:) |
| |
| ALIAS (CLUSTER)NAME:__________ USERNAME:________________ |
| |
| LIST NODE NAME(S):_________________________________________________________|
| |
| SYSTEM MANAGER CONTACT INFORMATION: |
| |
| NAME:__________________________________________ DTN:_____________________|
| |
| ELECTRONIC MAIL ADDRESS:___________________________________________________|
| |
+----------------------------------------------------------------------------+
+----------------------------------------------------------------------------+
| SYSTEM TO BE ACCESSED (SYSTEM YOU ARE TRYING TO REACH): |
| |
| NODE/CLUSTER NAME: ACADMY DEFAULT USERNAME TO ACCESS: TPAS_XFER |
+----------------------------------------------------------------------------+
| LIST FILES TO BE ACCESSED: |
| |
| ____ TPAS*.RBR, TPAS*.RPT, TPAS*.UNL, TPAS*.RRD ___________________________|
| |
| ___________________________________________________________________________|
| METHOD OF ACCESS: |
| +--+ +--+ +--+ +--+ |
| |XX| COPYING | | SENDING | | READ ONLY | | UPDATE |
| +--+ +--+ +--+ +--+ |
+----------------------------------------------------------------------------+
| REASON FOR REQUESTING THE PROXY ACCESS: |
| |
| Pulling data files for populating the Local Transfer Price |
| Administrative Systems databases |
| |
+----------------------------------------------------------------------------+
| FOR PRODUCTION ONLY: |
| |
| |
| COMPLETED BY:_________________________ DATE: _____________________________|
+----------------------------------------------------------------------------+
To Distribution List:
ALKO SLOOTS @JGO,
ERIC HENDRIKS @JGO,
PETER MULDERS @JGO,
TOM WALLACE @AYO,
LINDA WILCOX @AYO,
PAT FITZGERALD @REO,
GERRY KEENAN @AYO,
CHARLES FLACH @AYO,
IAN GILLINGHAM @AYO,
Bill Bradley @ILO,
Gerry Conway @ILO,
Mike Gallagher @ILO,
Martin King @ILO,
BOB CAMERON @TRO,
DAVID CAVANAUGH @TRO,
WANDA DENIS @TRO,
JEFF FLANAGAN @TRO,
LORNE KELLAWAY @KAO,
ROSS MILWARD @KAO,
DAVID PELKOLA @TRO,
HARRY RIDGE @KAO,
BRIDGET TERPSTRA @KAO,
EVA CHEUNG @HGO,
TIM HOMER @HGO,
CLARA HUI @HGO,
ALFONSO JIM @HGO,
ANDREW KAN @HGO,
KUNAL KASHYAP @HGO,
MACHAEL LEUNG @HGO,
MICHAEL LEUNG @HGO,
SUZANA TONG @HGO,
GEORGIANA WONG @HGO,
award::pooja@vaxmail,
ESGOPS::JCURLEY@VAXMAIL,
EAMONN FAHY @MSO,
MICHAEL GORMLEY @AKO,
MAGNI @AWARD @VMSMAIL,
TRACY WALKER @MSO,
Barbara Wilfand @MSO,
TONY BERET @SNO,
TERRY BOWMAN @SNO,
WILSON CHEUNG @SNO,
JOE FEROCE @HGO,
LEE FLANAGAN @SNO,
JIM FLAYE @SNO,
ROBERT JONES @SNO,
DARAB KANGA @SNO,
JON LONGWORTH @SNO,
GRAHAM STEVENS @SN,
RICHARD SICARD @SNO,
GLEN WILLIS @SNO,
AWARD::MAGNI@VAXMAIL,
Miller Donaldson @GEO,
barry edmonds @tdc,
Mike Green @EVT,
RACHEL GREGORY @REO,
LEIGHTON HAYWOOD @REO,
ARNE JORGENSEN @DMO,
ALBRECHT KAISER @SBP,
IAIN MCFADZEAN @AYO,
JEAN-HUGUES MOSNY @TDC,
FAZAL QUADIR @GEO
CC Distribution List:
DICK ASHENFELTER @GEO,
ANDREW BARNETT @GEO,
JOE FEROCE @MSO,
JEFF HELMAN @MSO,
ARNE JORGENSEN @DMO,
HENK KNOOP @JGO,
RANDY MCCLENAHAN @AKO,
PAT MCGUIRE @ILO,
AMIT NANAVATI @MSO,
RON RANA @GEO,
JOHN REEVE @REO,
ROLAND RICHARDS @AKO,
ROBIN SPRAGUE @REO,
JOSEPH TIERNEY @MSO,
JIM WARE @MSO,
BARBARA WILFAND @MSO,
NAME: Tracy Walker @MSO <WALKER.TRACY AT A1 at POWDML at PKO>
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 49.1 | V3.1 RELEASED | AWARD::MAGNI | Lois, 237-5548 | Fri Jan 27 1995 15:36 | 7 |
|
TPAS II V3.1 software has successfully concluded the pilot test phase,
and is now available to all implementation sites worldwide.
Please mail all requests for the software to ACADMY::QCA_ADMIN
V3.1 was to upgrade the TPAS II V3.0 kit to meet more DEC STD 095 requirements.
|
| 49.2 | v3.2 or run with v3.1 thru testing? | TROOA::BCAMERON | Bob Cameron, dtn 631-7431, Tea? | Fri Feb 24 1995 11:56 | 14 |
| Hi Lois,
We are approaching our scheduled round of user testing (next week).
Based on the changes for V3.2 kit, should I be planning to update the
kit to V3.2 before we start. I am not concerned with the Overflow problem
for our testing, and am considering running with V3.1 kit until we approach
our implementation in April, and then installing/testing a final kit version.
If you recommend upgrading to V3.2 now, how soon will it be ready?
thanks, Bob C
Canadian IM&T, Finance
|
| 49.3 | Mar 6/7 | AWARD::MAGNI | Lois, 237-5548 | Wed Mar 01 1995 09:16 | 9 |
| Bob,
I am not ignoring you. I am currently updating all the documentaion for
this release. After which I will re-package and make it available to be
sent out. I am pushing for the begining of next week.
I will post the release notes today so you will know the SPRs fixed.
Regards,
Lois
|
| 49.4 | tpas v3.2 release notes | AWARD::MAGNI | Lois, 237-5548 | Wed Mar 01 1995 14:50 | 209 |
| 1 RELEASE NOTES FOR TPAS V3.2 Page 1
These notes contain sections covering the following topics:
o Problems fixed in this release
o Known current problems for TPAS
o Additional installation considerations
o How to report software problems
TPAS V 3.2 requires VMS Version 5.0 or later.
2 PROBLEMS FIXED IN THIS RELEASE
The following problems in previous versions of TPAS have been
corrected in TPAS Version 3.2:
o 94121501 - Add in STR$UPCASE function to input data.
The Ship To/From and Ship To/From Type Code are now converted
to upper case prior to reading the database.
o 94121502 - capture non-numerics in billing code field.
The Ship To/From field is checked to insure that the data
sent is all numeric IF the Ship To/From Type Cd = "B",
Billing Code.
The following fatal error codes are sent back if the data is not
numeric:
%APPIX-F-BLLNGTONOTNUM, Bill/Ship To Billing Code is not numeric
%APPIX-F-BLLNGFROMNOTNUM, Bill/Ship From Billing Code is not numeric
o 95010901 - TPAS_CALC_TRNSFR_PRC.COB
When opening either audit trail file, TPAS$DATA:TPAS_AUDIT_TRAIL.DAT
or TPAS$DATA:TPAS_BELOW_STDCOST.DAT, and an error occurs the
following fatal errors are returned:
%APPIX-F-AUDITFILEERR, Error Opening TPAS$DATA:TPAS_AUDIT_TRAIL.DAT
%APPIX-F-STDAUDFILEERR, Error Opening TPAS$DATA:TPAS_BELOW_STDCOST.DAT
FIXED PROBLEMS Cont. Page 2
o 95012002 - FORMAL DEFINITION OF PASSING DATA
Create one document with all the pertinent information about the
data being passed to and from the programs.
The User and Install documentation has been updated to include
a table with the definition and size of data.
o 95020102 - Audit files opened extend.
The audit files are now opened using the OPEN EXTEND ALLOWING ALL
command in COBOL. There will now be only one of each of the audit
files created and written to in TPAS$DATA.
o 95021601 - Transfer Price Data Overflow.
Both the TRANSFER PRICE and TRANSFER PRICE TO REBILL have been
expanded to 999,999,999,999.99 or 9(12)V9(2).
With this expansion both audit trail file layouts have been
expanded accordingly. The new record layout is expanded by 4.
Two new Fatal errors may be returned if the price is over
999 Billion. There errors are:
%APPIX-F-TRNSPRCOVRFLOW,
Transfer Price greater than 999B - Data Overflow Err
%APPIX-F-RBTRNSPRCOVRFLOW,
Transfer Price to Rebill greater 999B - Data Overflow Err
o 95021701 - Clearer error message when incorrect Ship To/From.
Two clearer fatal error messages have been added. When the
Ship To/From Codes are subsidiary billing codes and they are not
found in the TPAS$DB.TRNSFR_AREA_TABLE the messages now clearly
indicate the error. They are:
%APPIX-F-GETAREAFROM, FROM Subsidiary Billing Code Area not on Corp. Table
%APPIX-F-GETAREATO, TO Subsidiary Billing Code Area not on Corp. Table
o TPAS_II_FUNC_DESIGN, TPAS_II_PHYSICAL, TPAS_II_INSTALLATION_DOC
and TPAS_II_USER_DOC have been updated to reflect changes.
3 KNOWN PROBLEMS
Page 3
o KNOWN PROBLEMS IN TPAS V3.2
This section summarizes problems in the TPAS
that have not been fixed for this release. When a reference
to a note is made see the TPAS Notes file AWARD::TPAS
95010902 - SQL ERROR and VMS ERROR codes
All programs need to be checked to ensure that the
VMS and SQL error codes are being passed back to
TPAS_CALC_TRNSFR_PRC and these codes are being passed
back to the calling program.
See Note 55, 55.1, 56, 56.1
95012001 - SEPARATE OBJ LIBRARIES
Create two separate object libraries that have
different TPAS_GET_PART.COBs in them. One will
be used when site installing replies to use PPCS.
The other is for sites not using PPCS. This is so that
when linking without PPCS installed on the system the
undefined warning messages will not be seen.
See Note 58.1, 58.2
95020101 - TPAS_COPY_NOR_MNTHLY.COM
This command stream should be changed to use a COPY FTSV
with a /POST_FUNCTION to update the control file
and send mail.
KNOWN PROBLEMS Cont. Page 4
95020103 - TRANSACTION REFERENCE NUMBER
Add a transaction number to the record layout of the
audit trail file.
In order to find a specific transaction, the following
data need to be combined to find a unique transaction:
* Date
* part number
* ship/bill to code
a) include this 'Local system reference number' in the
call to TPAS
b) write this reference number to the audit trail file.
95020901 - RMU/VERIFY SPECIAL ACLS for RDB V6.
The RMU VERIFY in the TPAS_SITE_IMPORT_DB,
TPAS_SITE_IMPORT_STKRM_DB and TPAS_SITE_LOAD_NOR_DB does
not work on RDB V6. The reason for this is that RMU needs
special new (VMS 6) ACLs set up to run.
Solutions:
- Remove the RMU/VERIFY in the command streams. Create
a separate command stream with the RMU and put in the
documentation something about how the installation site
needs to add in ACLs to the databases to make this work.
- Change the TPAS$DB, TPAS$STKRM_DB and TPAS$NOR$DB to
RMS files. Change all the SQL code to OPEN/READ
- Change the install to add the ACLS needed for RDB 6
Change the command streams to do a drop table and
do a RMU IMPORT
4 ADDITIONAL INSTALLATION CONSIDERATIONS Page 5
4.1 Installation Procedure Requirements
Make sure that all questions asked during the install are answered ahead of
time. If any changes to default logicals are required then edit the
TPAS$COM:TPAS_LOGICALS.COM and the SYS$MANAGER:TPAS$STARTUP.COM.
The program translate the logicals using the logical name table in VMS order:
PROCESS, JOB, GROUP, SYSTEM and LNM$TPAS
5 REPORTING SOFTWARE PROBLEMS
Complete and concise information will help Digital give accurate and
timely service to software problems. Experience shows that many SPRs
do not contain sufficient information to duplicate or identify the
problem. When you prepare to submit an SPR, please do the following:
o Describe as accurately as possible the state of the system
and the circumstances when the problem occurred. Include in
the description the version number of TPAS being used.
Illustrate the problem with specific examples.
o Reduce the problem to as small a size as possible, preferably
to a program unit of 30 source lines or fewer.
o Remember to include listings of any command files, relevant
data files, CDD record definitions, and so on.
o Place the problem on the notes file, AWARD::TPAS and mail
a copy to ACADMY::QCA_ADMIN.
o Report only one problem per SPR. This will facilitate a
faster response.
|
| 49.5 | V3.2 Released | AWARD::MAGNI | Lois, 237-5548 | Mon Mar 06 1995 13:21 | 18 |
| TPAS V3.2
TPAS V3.2 has been released.
If you currrently have TPAS, please send a note to ACADMY::QCA_ADMIN, with
the location that the kit will be copied to. Make sure that the area has
proxy access for ACADMY::APPIX_PROD
If you do not have TPAS please copy the registration form as follows:
$ COPY AWARD::TPAS$PUBLIC:TPAS_REGISTRATION_FORM.TXT *.*
Complete this form and mail it to ACADMY::QCA_ADMIN
Any questions please mail them to AWARD::MAGNI, copying ACADMY::QCA_ADMIN
Regards,
Lois Magni
|
| 49.6 | Error message mnemonic length | ELIS::RJANSEN | | Fri Mar 10 1995 03:25 | 19 |
| Lois,
The size of a TPAS I error message mnemonics was maximum 15 characters
long (See also note 55.1). Based on this information we defined locally
a TPAS error message file to be able to control the DMS software after
TPAS returned a fatal error.
However you anounced new error messages in your latest release notes
and one of the error mesages is 16 characters long (RBTRNSPRCOVRFLOW).
This is not really a problem, because at this stage it is no problem to
change it locally.
My question is, will 16 be the maximum size of the error message
mnemonics or is it possible that they will be longer in the future.
Please let me know, so I can reserve some extra space in our error
message file.
Rinus Jansen
|
| 49.7 | Correct - but causes no problem | AWARD::MAGNI | Lois, 237-5548 | Mon Mar 13 1995 11:03 | 26 |
| Rinus,
You are correct in the messaging facility the IDENT can only be up to 15
characters. I do not know why that didn't get thrown out.
I will put this up as an SPR and change the error by dropping the last W. But
this won't be until another release with a major SPR.
But, I have looked through my documentation for where I say the error is 15.
Can you point me to the correct place ? I want to correct this because the
error is sent back as:
%APPIX-x-x(71)
05 TPAS_TRANS_STATUS.
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).
I really have no control on the size of the IDENT as the messaging utility
places the comma and message text immediately after the IDENT, not caring if it
is less than 15 characters.
Lois
|
| 49.8 | No error size in the documentation | ELIS::RJANSEN | | Tue Mar 14 1995 03:41 | 8 |
| Lois,
I did not read it in the documentation, but in one of the notes of the
TPAS notes conference you mentioned a size of 15. Sorry but I don't
know which one it was and at the moment I don't have the time to look
for it.
Regards, Rinus
|