Frequently Asked Questions
1. What is ThinView?
ThinView is a Java-based, Web-to-host e-business application developer that allows secure Web browser access to AS/400 applications and data. No prior programming experience is required, since ThinView's unique "set-up wizards" quickly produce easy-to-use applets for 5250 terminal emulation, viewing and/or printing reports, or database applications.
2. Who can use ThinView applets?
Any locally attached, intranet or Internet user equipped with either Netscape Navigator or Microsoft Internet Explorer, and Java Plug in 1.3 can use ThinView applets.
3. What are the ThinView AS/400 components?
A ThinView library containing the server objects and a "ThinView" user profile. The ThinView server is an active AS/400 job. For each applet, two new AS/400 jobs start, one of which remains active until the applet is closed.
4. What are the ThinView client components?
The "ThinView.jar" and "ThinView.html" files. These files can reside in a directory in the PCs file system, or in a network directory, or (preferably) be placed on a Web server directory.
5. How secure is ThinView?
ThinView secures your data. Users must have a valid AS/400 user ID and Password. After the initial protocol handshake, all data to and from the client and server is encrypted utilizing Secure Sockets Layer (SSL) for client and server authentication, data integration and privacy. ThinView also honors AS/400 system security through levels 40 and 50, and produces an audit trail listing all changes made by users.
6. How do I troubleshoot ThinView installation problems?
7. How do I troubleshoot ThinView logon problems?
8. What AS/400 authority is needed to install ThinView?
The AS/400 user profile must have the special authorities of "*secadm" and "*allobj".
9. How do I start the ThinView server?
The ThinView server is activated during installation. If you need to restart it at a later time, logon to an AS/400 terminal using a profile with special authority of "*allobj" and execute the command "thinview/strthinvu". This will start the ThinView server on default port 11093. If you wish to alter this, prompt the command and indicate a different port number. Please keep in mind that ThinView jobs need to be placed in an active JOBQ with no limits on the number of active jobs. If you get an error message about the JOBQ, you can change the ThinView job descriptions in the ThinView library to use a different JOBQ.
10. How do I end the ThinView server?
Logon to an AS/400 terminal and execute the command "thinview/endthinvu". The ThinView Server Shutdown Utility screen will appear displaying any server and client connection jobs. You may end each job individually or all the ThinView jobs for a given server port. Alternatively, you can run the command "thinview/endthinvu *all". This will end the ThinView server and any active client sessions on all ThinView ports. If you wish to end the server for a specific port, prompt the command and indicate a port number.
11. Where are the ThinView applets saved?
ThinView applets are stored on the AS/400 as program objects. The applet appearances are saved in the "thinview/options" database file. The html documents, needed to launch ThinView applets, can be stored in the PC-like directory of your choice.
12. Why can't I logon to ThinView as "qsecofr"?
The ThinView server submits a job with the "user" parameter set to the user ID that was used during ThinView logon. The OS/400 does not permit this parameter value to be set to "qsecofr".
13. How do I serve a ThinView applet from the AS/400 Web server using the "http" protocol?
When generating the html file for your ThinView applet, be sure to check the "Applet Host" box. Copy this html file, along with the "thinview.jar" and "ThinViewBanner.jpg" files to an IFS directory on the AS/400. Make sure the Web server user profile (i.e. "qtmhhttp") has read access to these files.
14. What type of AS/400 data files are supported?
ThinView supports physical, logical, and join-logical files.