iView stops working

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

Users experiencing trouble with Internet Explorer are instructed to try this tool: http://download.cnet.com/Complete-Internet-Repair/3000-2094_4-75332305.html?tag=rb_content;contentBody

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    
ZENDCOREAP  ZENDADMIN   BATCHI   ACTIVE            PGM-httpd    

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

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.

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       

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:

http://www-1.ibm.com/support/docview.wss?uid=nas3ab84bf12f76d189c86256eac004d06a8

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

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.

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.

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.

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

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

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

CRTSAVF FILE(QGPL/IVIEW)

2. Create the iView IFS savefile:

CRTSAVF FILE(QGPL/IVIEWIFS)

3. Shutdown the iView server if running ( menu IVIEW )
4. Save the iView library to savefile:

SAVLIB LIB(IVIEW) DEV(*SAVF) SAVF(QGPL/IVIEW)

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 zend.com following their instructions.
2. Create user profile IVIEW:

CRTUSRPRF USRPRF(IVIEW) USRCLS(*SYSOPR) SPCAUT(*ALLOBJ *JOBCTL *SPLCTL)

3. Restore the iView library and IFS:

RSTLIB SAVLIB(IVIEW) DEV(*SAVF) SAVF(QGPL/IVIEW)
mkdir '/iview'
RST DEV('/qsys.lib/qgpl.lib/iviewifs.file') OBJ(('/iview/*'))

4. Grant authorities:

GRTOBJAUT OBJ(IVIEW/*ALL) OBJTYPE(*ALL) USER(IVIEW NOBODY) AUT(*ALL)
CHGAUT OBJ('/iview') USER(IVIEW NOBODY) DTAAUT(*RWX) OBJAUT(*ALL) SUBTREE(*ALL)

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.

Released into beta September 3rd 2010
Features:

• Integration with iScan version 2 scanner interface.
• Import from iScan documents with full OCR of search index data.
• Import from iScan documents with search index data populated from DB2 table.

Released in beta March 30th 2009 The primary feature of this release is the scanned image import from directory function, which permits the admin to easily import scanned images into iView.

Additional features:

• Sending email via iMail was simplified to just use a SBMJOB to put an ESNDMAIL command into a batch subsystem.

This was a fix release that had limited distribution January - March 2009. This release includes:

• Spool number captured as variable IVWSPLN is now 6 digits.
• iView internally with sort/burst will process spool files to the maximum 6 digit value possible in i5/OS.
• iView SCS Monitor will now process *SCS spool files with 6 digit spool numbers. iView Merge Monitor will not, however, process spool files with spool file numbers greater than 9,999 since at this time iDocs will not.

iView 5.1 was released December 31st, 2008. Release 5.1 is an update to the Php Web Interface first released in iView 5. It's major feature is Related Documents.

Released on November 13th, 2008. Full discussion [ here ]

• Php: iView front end implemented in Php.
• Unlimited Virtual Folders: Unlimited rules in Virtual Folders.
• Document Annotation: Attach comments to documents.
• Boolean And/or Logic in Virtual Folders: Configure Virtual Folders using boolean and/or so that multiple tests can be joined.
• Configurable Results Page: Specify which if any search indices are displayed in the search results page, controlling appearance to the end user.
• Appearance Control: Control the appearance through the full provision of CSS and the provision of the html page contex.

Released on July 11th, 2008

This is a maintenance release that updates the following issue:

• Shared Cookie Space: iView now coexists peacefully on the System i web server with other applications that use cookies.
• Different versions: standalone, and integrated versions. Integrated version coexists with iDocs in the same partition.

Release of iView 4 contains these enhancements:

• FTP interface to a remote ftp server is provided for. In addition to archiving as usual, the iView engine will ftp the archived pdf document to the remote host, and optionally include a text file with the search indices values. Also optionally the engine will execute a user specified post ftp command.

• Archiving options for the original spool file are expanded to *RETAIN, *ORIGINAL, *SYSTEM, and *NONE.

• The user profile under which iView archives the spool file and executes the post ftp command is now configurable to be either the system profile IVIEW or the user profile that owns the input spool file iView is processing.

• Archiving of the intermediate *USERASCII spool file is enabled if the data area DSRETASC is set to Y.

Release 3.03 was never released as a separate version. It's objects were distributed separately as required.

• iView now invokes iDocs merges using the standard api TFPRTAPI .
• iView will now process an iDocs form set . This form set should either not sort/burst, or the sort/burst should precisly match that of the iView archive application so that after bursting only one output spool file is produced by iDocs. The user is still unable to prompt for iDocs form sets in archive setup (to discourage people from using them), but the form set name can be keyed and the iView engine will invoke it.
• iView installation now has an option to install only the backend of the product, i.e. all of the product except the web front end.
• iView server will now work with SMB networked directories .

Release 3.02 was released in June of 2007. Changes:

• IVC3000, the iView server launcher, substantially rewritten to simplify and to permit invocation from QSTRUP.

Release 3.01 was distributed starting on 03.19.2007. It is a fix release.

---

[ Up To Index ]