TECA, Inc.
|
|
|
|
|
|
|
|
|
|
► PRODUCTS ► SUPPORT ► FAQs
► SEARCH ► NEWS
► TECA Inc.
|
FAQs (Frequently Asked Questions) To better serve our customers and to help developers working with our product evaluations, we maintain a knowledge base of Frequently Asked Questions (FAQ) on our web site.
ImageTransferPlusBack to Top
TECA Data400Back to Top
TECA Custom ControlsConnection QuestionsLicensing and DistributionFile TransferData QueuesShared FoldersBack to TopOther QuestionsBack to Top► Connecting to my SQL Server systemQ: I tried to connect to the SQL Server system that was automatically filled in the combo box, but I received a "Connection not completed." dialog? A: You will need to have MDAC version 2.5 or higher on your PC machine. If you don't know what MDAC version you are running you may download a component checker from Microsoft for free at www.microsoft.com/data/download.htm. You may also download for free the correct MDAC version to run ImageTransferPlus at www.microsoft.com/data/download.htm. Back to Top► Registering TECA Data400Q: Do I need to register TECA Data400 during the trial period? A: No. You may use TECA Data400 without registering during the 30-day trial period. Several registration status dialog boxes will be displayed informing you of your trial status, including trial days left and actual trial expiration date. When you purchase a license for TECA Data400, you will be issued a registration code. You then enter the registration code on the Register Program dialog and the registration status dialog boxes will no longer be displayed. Back to Top
► Active Server Pages (ASP)Q: Can I use TECA Data400 on Active Server Pages (ASP)? A: Yes. TECA Data400 can be used on Active Server Pages (ASP). Set the dboEngine object property ShowMsgBox to 1-no, as Active Server Pages do not allow interaction with message boxes. Q: Do I need Client Access on my server? A: When using TCP/IP connections on your server or PC to the AS/400, TECA Data400 does not require Client Access or any other connectivity products. Back to Top
► SNA Server ConnectionQ: Can I use TECA Data400 with an SNA Server connection? A: Yes. TECA Data400 can connect to your AS/400 over SNA connections, Anynet, or Native TCP/IP. When connecting over SNA, the system name is case specific and needs to match the name configured on your router connection. When connecting over TCP/IP, you may use the IP address or the system name of the AS/400. Back to Top
► Run-time DLLsQ: When I run the TECA Data400 Sample programs, I receive the error 'Wrong run-time DLLs'. Why? A: This is a Visual Basic error indicating the Visual Basic run-time DLLs located on your PC are different than the run-time DLLs used to build the executable program. The TECA Data400 Sample programs were built using Visual Basic 5.0 with Service Pack 2 installed. Service Pack 2 contained a new Visual Basic runtime module. Visual Basic executable programs that are built using SP 2 will receive the 'Wrong run-time DLL' message when they are executed on systems with the original VB 5.0 runtime DLLs. To eliminate this error you can either install Service Pack 2 on your development system or you can recompile the executable programs with your existing version of Visual Basic. To recompile the TECA Data400 sample programs, simply start Visual Basic on your PC, open a sample program and select the option to make an executable program. This causes the sample program to use the Visual Basic runtime support that's installed on your system. Back to Top
► Unknown TCP Return CodeQ: When I first attempted to connect to the AS/400 using TECA Data400 I received an error message that stated that I had an "Unknown TCP return code". I'm able to ping my AS/400. What is causing this problem? A: This problem is generally caused by the AS/400 server jobs not being
started. If you are connecting to the AS.400 using TCP/IP and the AS/400 is
using OS/400 V4R1 or earlier then you need to make sure the your have the appropriate
PTF's applied to the AS/400. The following PTFs are required for TCP/IP connectivity on
preV4R2 systems. In addition, to these PTFs the TCP/IP host server must be started. You can start the AS/400 TCP/IP host server by running the following commands: STRTCPSTRHOSTSVR *ALL AS/400 systems with V4R2 do not need any additional PTFs however you still need to make sure the host server jobs are started. The following commands are used to start the host server jobs on a V4R2 system: STRTCP Back to Top
► Try Again MessageQ: While trying to connect using TECA Data400, I get error message number 318 – "Try again – 11002". What causes this error message? A: This is a TCP/IP related error message. This means you need to enter the hostname and IP address in your HOSTS file on the PC. Or the DNS (Domain Name Server) did not resolve the TCP/IP address to the hostname as expected, in which case you need to correct the DNS IP address and hostname. Back to Top
► Multiple controls on one formQ: Can I have multiple TECA Data400 Data Source Controls on one form? A: Yes. TECA Data400 is apartment threaded and keeps each instance of the control as a separate object. Back to Top
► No Data MessageQ: While trying to connect using TECA Data400, I get error message number 320 : "No Data-11004". What causes this error message? A: If the AS/400 you are connecting to is V4R1 or lower, you need to create a controller and devices on the AS/400. The MODE on these devices need to be set to ‘BLANK’. The instructions for creating the controller and devices is contained in the READ ME FIRST file, located off the TECA Data400 menu item. Back to Top
► 32-bit Router and 32-bit COM ControlsQ: Do I need a 32-bit router to use your 32-bit COM controls? A: Yes. TECA Custom Controls for the AS/400 version 2.0 are native 32-bit COM controls and they require a 32-bit router to connect to the AS/400. However, if you are using a 16-bit router under Windows 95 or Windows NT you can use the 16-bit TECA Custom Controls Version 1.1 which are supported for 16-bit application development under Windows 3.1 as well as Windows 95 and Windows NT. Back to Top
► AS/400 communications products and TECA Custom Controls?Q: Do I need to buy a separate communications product to use TECA Custom Controls? A: Yes. TECA Custom Controls allow you to easily develop AS/400 client./server applications but they do not provide the base communications to the AS/400. An AS/400 router is required for the underlying AS/400 communications. TECA Custom Controls version 1.1 is compatible with the following 16-bit connectivity products: IBM's PC Support V2R2 and higher, IBM's Client Access for Windows V3R1 and higher, NetSoft's Midrange Bundle V4.2 or higher, Wall Data's RUMBA Access/400 V3.0 or higher. The 32-bit TECA Custom Controls version 2.0 are compatible with IBM's Client Access for Windows 95 V3R1 or higher, IBM's Client Access for Windows NT/95 V3R1 or higher, NetSoft's NS/Midrange Bundle for AS/400 Access v2.0, Wall Data's RUMBA Access for Windows 95/NT v3.0. Back to Top
► Automatically connecting to the AS/400Q: Can any of the TECA Custom Controls automatically connect to the AS/400 or is it necessary to make a connection before using them? A: All of the TECA Custom Controls can be used in design mode without a connection to the AS/400. An AS/400 connection is required when you attempt to run an application that contains the controls. Whether or not the connection will be made automatically depends on how the underlying router is configured. All of the supported connectivity products (i.e. Client Access, NetSoft and Wall Data) can be configured to automatically connect to the AS/400 when an application makes its first request. Back to Top
► NetWare for SAA and SNA ServerQ: Can TECA Custom Controls be used if I have a NetWare for SAA or SNA Server link to the AS/400? A: Yes, both TECA Custom Controls for the AS/400 version 1.1 and TECA Custom Controls for AS/400 version 2.0 are compatible with Novell's NetWare for SAA and Microsoft's SNA Server. When running over an SNA gateway connection, TECA Custom Controls still require that each client PC has one of the compatible PC-AS/400 communication products installed. Back to Top
► TECA Custom Controls and TCP/IPQ: Can TECA Custom Controls V 2.0 be used over a native TCP/IP connection without AnyNet or an SNA Gateway? A: Yes. When used with Client Access for Windows 95 or Client Access for Windows 95/NT all of the TECA Custom Controls will work over a native TCP/IP connection without using AnyNet or an SNA Gateway. Back to Top
► Licensing TECA Custom ControlsQ: Do I have to buy a runtime license of TECA Custom Controls for every system that will run the applications I've built using your controls? A: No. You may freely distribute any application you create that uses TECA Custom Controls. TECA Custom Controls are licensed per development system. There are no runtime licenses required. When you install TECA Custom Controls, a design-time license file is also installed. This license file is not required at runtime. Instead, it allows you to use TECA Custon Control's at design-time a development environment. You are not allowed to include that license file with any application that you develop and distribute. Back to Top► Distributing FilesQ: I've built an application using TECA Custom Controls and now I'm creating a setup program. What files do I need to distribute? A: Applications that are built using TECA Custom Controls will need any runtime files required by your development platform and all of the TECA Custom Control OCX's that were used by the application. For instance, if you have developed an application using Visual Basic 4.0 that uses the TECA FileTransfer/OCX, you can run the VB Setup Wizard to create a setup program. The VB Setup Wizard will display a prompt which allows you to include all of the runtime files that are used by your application. The transf.ocx file which provides the runtime support for the TECA FileTransfer/OCX will be automatically included in this list. The TECA files that can be distributed are: transf.ocx - TECA FileTransfer/OCX dataq.ocx - TECA DataQueue/OCX folders.ocx - TECA Folders/OCX registry.ocx - TECA Registry/OCX rmtcmd.ocx - TECA RemoteCommand/OCX sysname.ocx - TECA SystemName/OCX transf.vbx - FileTransfer/VBX dataq.vbx - DataQueue/VBX sharedf.vbx - SharedFolders/VBX ini.vbx - INI/OCX rmtcmd.vbx - RemoteCommand/VBX sysname.vbx - SysName/VBX Back to Top
► Uploading data to the AS/400Q: How do I upload data to the AS/400 using the FileTransfer/OCX? A: You can upload data to the AS/400 using the TECA FileTransfer/OCX by using an SQL replace statement in the Buffer property of the TECA FileTansfer/OCX. For instance, to upload a source file to the AS/400 you could enter the following SQL statement in the TECA FileTransfer/OCX buffer property: REPLACE * INTO qgpl/qrpgsrc(member1) filetype(source) rcdlen(80) crtmbr(*yes) After setting the Buffer property you can set the ConvertAuto property to TF_TRUE, the FullFile property to TF_TRUE and the PCFile property to the name of your desired PC input file. Then evoke the SendRequest method followed by the SendRecords method. The member1 member will be created in the file qgpl/qrpgsrc. This simple example shows one option for uploading data to the AS/400. Many other options are also possible. Back to Top
► Using the FileTransfer/OCX to download from multiple filesQ: How can I use the FileTransfer/OCX to download data from mulitple AS/400 files? A: You can join data from several AS/400 files and download it to the PC using the TECA FileTransfer/OCX. To download data from multiple files you need to name those files in the select clause that's entered in the Buffer property of the TECA FileTransfer/OCX. For instance, to join and download the data from two files named file1 and file2 in library datalib, you might enter the following SQL select statement in the Buffer property: SELECT * FROM datalib/file1, datalib/file2 WHERE T1.filekey = T2.filekey After setting the Buffer property you can set the ConvertAuto property to TF_TRUE, the FullFile property to TF_TRUE and the PCFile property to the name of your desired PC output file. Then evoke the SendRequest method followed by the RetreveRecords method. The two files will be joined on the filekey field and all of the data from both files will be downloaded to the PC. This simple example shows one option for downloading data from the AS/400. Many other options are also possible. Back to Top
► What's a data queue?Q: What's a data queue and how can it be used to transfer data to the AS/400? A: A data queue is an AS/400 object that's used to communicate between multiple programs. While data queues were originally intended for AS/400-to-AS/400 program communications, their high performance and low overhead also made them an excellent basis for client/server applications. Data queues can be organized by FIFO (First-In-First-Out), LIFO (Last-In-First-Out) or by a simple composite key value. When you build an AS/400 client/server application using data queues you will typically need to write an AS/400 HLL program that will act as the server. In this kind of scenario, one or more clients will add entries to one of more data queues. The AS/400 HLL data queue application server will retrieve the entries from the data queue(s) and them perform some type of processing. Finally, the AS/400 data queue application server will then send a response back to the client(s) by wrting a data queue entry that will be retrieved by the client programs. Client/server programs using data queues can often deliver sub-second performance for the client applications. Back to Top
► Communications Error 4019 using the DataQueue/OCXQ: I'm using the DataQueue/OCX over a Client Access for Windows 95 connection and I'm getting a 4019 error. What's a 4019 and how can I fix this problem? A: Error code 4019 indicates an AS/400 communications error. The most frequent cause of this error is having an old version of the AS/400 data queue server programs. IBM has a PTF which addresses this problem. If you are running V3R1, you will need to apply PTF SF27397 to program product 5763-SS1. If you are running V3R6, you will need to apply PTF SF26033 to program product 5716-SS1. Back to Top
► Client Access and data queue performanceQ: Does PTF SF27397 also address performance? I've found the data queue performance using Client Access APIs to be horrible. It is much slower than NetSoft. A: PTF SF27397 does not address performance. We have found that the performance of our DataQueue/OCX over a Client Access connection has a slower initialization time than using the DataQueue/OCX over either NetSoft or Wall Data connections. However, after the initial connection has been made the speed is comparible. Back to Top
► SharedFolders/VBX and Windows 95Q: Can the 16-bit Shared Folders/VBX be used under Windows 95? A: No. None of the supporting 16-bit communicaitons products (i.e. Client Access, NetSoft or Wall Data) support 16-bit Shared Folders under Windows 95. You must use one of the 32-bit communications products to enable Shared Folders support under Windows 95. TECA's Folders/OCX can then be used to assign and release AS/400 shared folders as well as other network drive mappings. Back to Top
► Ask your own questionIf you have any questions you would like to be answered please send an e-mail to info@teca.com Back to Top
|
|
© Copyright 2000-2003, TECA, Inc. All rights reserved. |