Reporting Deployment Tool issues
| Date: |
1 October, 1999 |
| Product/Release: |
LANSA for Windows Deployment Tool |
| Abstract: |
A checklist for efficiently reporting issues to do with the Deployment
Tool |
| Submitted By: |
LANSA Technical Support |
Detailed Description:
The LANSA for Windows Deployment tool will be generally available in the next full
release of LANSA for Windows. Please, refer to the checklist below whenever you have to
report a problem using the Deployment Tool.
- A file called x_iparam.dat. For both the Source and Target Systems (assuming SETUP.EXE
has run to the end. ie. the user was prompted to Click the Finish button). x_iparam.dat
should be found in
x_win95\x_lansa\x_pkgs\<application name>\<package name>\
- Screen captures of any errors that occurred at any point in time during either package
creation or installation.
- A file called x_err.log. This will only be found if a LANSA application error occured
during package creation.
- A file called export.log create in the windows\temp directory on the source machine.
- A file called dpcreate.log located on the source pc in
- x_win95\x_lansa\x_pkgs\<application
name>\<package name>\
- Screen captures of the ODBC driver configuration.
|
