User Tools

Site Tools


[ Up To Index ]

iView Technical Discussion

iView Known Issues

iView stops working

Check to see if the IBM I Access Server is running:

Trouble with IE

Users experiencing trouble with Internet Explorer are instructed to try this tool:;contentBody

iView Web Not Work After IPL

If you are running iView version 5 check that:

  • ZEND subsystem is running with at least these jobs:

Job         User        Type     -----Status-----  Function     
I5_COMD     QTCP        BATCH    ACTIVE            PGM-EASYCOMD 
ZC_STR_PRN  ZENDADMIN   BATCHI   ACTIVE            PGM-prngd    

  • ZENDCORE apache server is running in subsystem QHTTPSVR

If not, go to menu ZENDCORE/ZCAMENU to stop and restart these.

If you are running earlier versions of iView check that the Apache server IVIEW is running in QHTTPSVR.

iDocs Form Sets

Issue: Using iDocs Form Sets With iView.

iView is not designed to work with iDocs form sets, only with iDocs forms, and the iDocs form prompt will only list iDocs forms. If you are running iView 3.02 updated (iView 3.03) you can type the name of an iDocs formset in the iDocs form field and it will process the formset. iView 3.02 and earlier will not process a formset.

Formsets in iDocs require bursting and one should consider the impact on the iView archive of the formset bursting.

iView Engine Data Queue

Issue: iView Engine Fails To Process Spool Files For No Apparent Reason

Some releases of iDocs contain a duplicate data queue for the iView engine IVIEWSEVER. Check that the outqueue(s) monitored by the iView engine do not have this duplicate data queue selected, i.e. check that the data queue specified in the monitored outqueue(s) is in library iView.

To check, CHGOUTQ outqLib/outqName <F4> <F9> page down to the end and check the name and library of the data queue attached to the outqueue. Should show:

                         Change Output Queue (CHGOUTQ)                        
Type choices, press Enter.                                                    
                           Additional Parameters                              
Display any file . . . . . . . .   *NO           *SAME, *NO, *YES, *OWNER     
Job separators . . . . . . . . .   0             0-9, *SAME, *MSG             
Operator controlled  . . . . . .   *YES          *SAME, *YES, *NO             
Data queue . . . . . . . . . . .   IVIEWSEVER    Name, *SAME, *NONE           
  Library  . . . . . . . . . . .     IVIEW       Name, *LIBL, *CURLIB         
Authority to check . . . . . . .   *OWNER        *SAME, *OWNER, *DTAAUT       

Login Failure Under V5R3

Issue: Login fails with error CPF3C3C.

iView validates user profiles using the system API QSYGETPH. IBM made a change to the QSYGETPH api starting with V5R3. Users running iView 2 and older may experience this error upon upgrading OS/400 to V5R3 or later. The iView login program was updated to the current api. Upgrading to the current version of iView is the recommended solution. However, there is a ptf , outlined here:

that you can install to give you 180 days of temporary operability under the old api.

Tabbed Browsers

Issue: Login Issues with Tabbed Browsers

iView security uses a cookie. Browsers appear to not segregate cookies between tabs. That means that logging into iView in one tab, opening a second tab and logging in again under a different profile, obliterates the first login.

If you are working with different user profiles concurrently in iView use separate browser windows rather than tabs.

Web User Interface Hangs For No Reason

Issue: Web User Interface Hangs For No Reason

If the web front end appears to hang while loading a page in the iView front end, consider disabling the configuration setting for Allow persistent connections. This is found under the System Resources section of the IBM browser based web configuration function. This is V5R3 APAR SE14411, for which the V5R3 patch SI13570 was issued by IBM.

iView Web Security Does Not Work

Issue: After successful login, all users are unable to use the web front end. Security exceptions are displayed that show that the user profile is unknown or there has been a security failure for that profile.

Versions: Versions 3 and earlier.

Cause: iView was originally written before web applications for the System i were common. iView does not share its cookie space well.

Workaround: Create a separate IP address for the System i (which will host multiple IP addresses) and move the iView Apache instance to that IP.

This issue is fixed in iView 4.

Archived PDF Documents Wrong Page Size or Font Size

To adjust the conversion characteristics of *SCS spool files (i.e. archives that do not hand off the spool file to iDocs as a part of archiving) use CHGCMDDFT to change the page size and font/font size default parameters of the CPYIVIEW command.

iView Capacity

iView stores pdf documents in the IFS as separate files. Each iView application has its own storage subdirectory, being a subdirectory of /iview. Thus, for archive application PO the pdf documents may be found as file system objects in /iview/PO.

The search index data is store in DB2/400 database, with a separate database for each archive application.

For *TYPE2 directories, the i5/OS limit is 1,000,000 file system objects per directory. Thus, the following limitations apply to iView:

  • Maximum number of documents in an archive application: 1,000,000 less the number of top level Virtual Folders directories.
  • Maximum number of archive applications on one System i server: about 999,000

Virtual Folders limits: In versions 4 and earlier, the apparent location of documents in Virtual Folders is implemented through SQL. There is a system limit to the length of a SQL statement of about 32,000 characters. Thus, Virtual Folders rules should be kept as simple as possible to limit the length of the SQL statements required to present the Virtual Folders structure to the end user. In versions 5 and later there is no limit to or restrictions on the complexity of Virtual Folders.

iView Miscellaneous Issues

Replicating an iView Installation

These instructions are preliminary. Please call technical support before using them.

On the “from” server:
1. Create the iView library savefile:

2. Create the iView IFS savefile:
3. Shutdown the iView server if running ( menu IVIEW )
4. Save the iView library to savefile:
5. Save the iView IFS to savefile:
SAV DEV('/qsys.lib/qgpl.lib/iviewifs.file') OBJ(('/iview/*')) SUBTREE(*ALL)

ftp these files to the “to” machine in library QGPL.

On the “to” machine:

1. Install the Zend Php interpreter from following their instructions.
2. Create user profile IVIEW:

3. Restore the iView library and IFS:
mkdir '/iview'
RST DEV('/qsys.lib/qgpl.lib/iviewifs.file') OBJ(('/iview/*'))
4. Grant authorities:
5. Use the IBM i http server web admin interface to duplicate the changes to the http server instance ZENDCORE. You can use the option to edit the configuration file to copy and paste the changes.

[ Up To Index ]

pub/iviewknownissues.txt · Last modified: 2018/09/05 14:50 by kkramer