FAQs

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.

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.

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.

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.

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.

  1. Review the installation instructions in the Install.html and the continuation document (Server.html).

  2. Stop (endtcpsvr *ftp) and restart (strtcpsvr *ftp) the AS/400 FTP server and retry the installation.

  3. If the problem continues, start the “Java Plug-in Control Panel” from the Start-Programs menu. This may take a few moments. If it does not come up, remove the Java Plug-in using  “Add/Remove Programs” in the Control Panel and reinstall it.

  4. Enable the “Show Java Console” box in “Basic” tab, and disable the “Cache JARS in memory” box in Basic tab and the “Enable Just In Time Compiler” box in Advanced tab. Click “Apply,” close the window.

  5. Reboot your PC and try the installation again. This time, a Java Console will appear displaying diagnostic information about the installation.

  6. Please email us the content of the Java Console and any related AS/400 spool files (wrksplf userid) for the user profile used during installation.

  7.  

  1. Make sure the ThinView server job “thinserver” is active. You can end and then restart the ThinView server (use the AS/400 commands “thinview/endthinvu” and “thinview/strthinvu”).

  2. If the problem continues, start the “Java Plug-in Control Panel” from the Start-Programs menu. This may take a few moments. If it does not come up, remove the Java Plug-in from “Add/Remove Programs” in the Control Panel and reinstall it again.

  3. Enable the “Show Java Console” box in Basic tab, and disable the “Cache JARS in memory” box in Basic tab and the “Enable Just In Time Compiler” box in Advanced tab. Click Apply, close the window.

  4. Reboot your PC and try to logon again. This time, a Java Console will appear displaying diagnostic information.

  5. Please e-mail us the content of the Java Console and any related AS/400 spool files (wrksplf userid) for the user profile used during the ThinView Logon.

The AS/400 user profile must have the special authorities of “*secadm” and “*allobj”.

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.

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.

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.

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”.

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.

ThinView supports physical, logical, and join-logical files.