User Tools

Site Tools


[ Up To Index ]

Monitoring Outqueues with the iView Engine


iView Server                                                              
  10. Work with iView Servers                             WRKIVWSRV       
  11. Start iView Server                                  STRIVWSRV       
  12. End iView Subsystem                                 ENDSBS          

To setup the iView outqueue engine, known also as the server, select option 10 from the iView main menu.

  7/06/07                          iView                              IV2000C1  
 14:47:47                      Server Maintenance                     QSECOFR   
 Type options, press Enter.                                                     
  1=Select   3=Copy   4=Delete   7=Rename                                       
                  Opt  Server      Description                                  
                   1   IVIEWSEVER  iView Server Application                     
Select option 1 to update the IVIEWSEVER engine definition. Current releases only support one engine named IVIEWSEVER - do not rename the server or create a second server.

 7/06/07                          iView                              IV2000C3 
14:48:37                      Server Maintenance                     QSECOFR  
Server. . . . . . . . . . : IVIEWSEVER   Archive Out Queue. . . . : IVWARCH   
Description: iView Server Application    Library. . . . . . . . . : IVIEW     
             Originating           Spool      Spool        Archive            
       Library      Out Queue    Attribute    Value        Application        
       IVIEW        DEMOQ        *FORMTYPE    *STD         IVWINVOICE            

At this screen you may work with the following header information:

  • Archive Out Queue / Library: This is the outqueue into which iView will archive input *SCS spool files.

Current releases only support an archive outqueue named IVIEW/IVWARCH. Do not change the default.

  • Description: Server Description.

You must specify at least one line of archive recognition information:

  • Originating Outqueue / Library: This outqueue is watched by the engine for spool files. You may specify multiple outqueues in different libraries. Caution: the iView engine is a dataqueue engine like the iDocs engines. You should not specify an outqueue here that is also monitored by an iDocs engine and vice versa.
  • Spool Attribute: Specify the attribute type to test:

  1. *FORMTYPE: test the name of the form of the spool file.
  2. *USERID: test the userid of the spool file owner.
  3. *JOBNAME: test the name of the job that created the spool file.
  4. *FILE: test the name of the printer file.
  5. *USERDATA: test the user data of the spool file.

  • Spool Value: value used to test against the specified spool attribute.
  • Archive Application: the archive application to process the spool file when the test of the spool value against the spool attribute returns true.

So in the above printscreen, the engine monitors the outqueue iview/demoq and for all spool files with formtype of *STD (the i5/OS default) the archive application IVWINVOICE will be used to archive the spool file. The original spool file is archived into iview/ivwarch outqueue.

Start the Engine

One the engine has been defined, you may start it with option 11 from menu IVIEW.

                         Start iView Server (STRIVWSRV)                   
 Type choices, press Enter.                                               
 iView Server . . . . . . . . . .   iviewsever    Value, or F4 for list   
 iView Job Queue  . . . . . . . .   SRVJOBQ       Character value         
 iView Library  . . . . . . . . .   'IVIEW'       Character value         
 iDocs Library  . . . . . . . . .   'FMG'         Character value, *NONE  
 Enable subsystem logging . . . .   *NO           *YES, *NO, *YES, *NO    

  • iView Server: Enter the name of the server, IVIEWSEVER in the current release.
  • iView job queue: Leave unchanged as SRVJOBQ.
  • iView Library: Specify the library containing the iView executables. This is normally IVIEW.
  • iDocs Library: If running with iDocs specify the iDocs library, presently FMG. If not running with iDocs specify *NONE.
  • Enable Subsystem Logging: Normally use *NO. *YES will cause each process in the IVIEWSBS subsystem to leave a job log.

Very Important: (version 4.01 and later) if running the iDocs integrated version of iView library FMG must be specified as the iDocs library, as iView will presume it is able to use iPDF from an external source; iPDF is bundled with iDocs in library FMG.

After the command completes, the WRKACTJOB command should show the IVIEWSBS subsystem running with 5 jobs running in it:

Opt  Subsystem/Job  User        Type  CPU %  Function        Status  
     IVIEWSBS       QSYS        SBS      .0                   DEQW   
       BRTMONITOR   IVIEW       ASJ      .0  PGM-IVR5000      DEQA   
       IVIEWSEVER   IVIEW       BCH      .0  PGM-IVR3000      DEQA   
       MRGMONITOR   IVIEW       ASJ      .0  PGM-IVR6000      DEQA   
       SCSMONITOR   IVIEW       ASJ      .0  PGM-IVR8000      DEQA   
       SRTMONITOR   IVIEW       ASJ      .0  PGM-IVR4000      DEQA   

End the Engine

Option 12 from menu IVIEW will end the IVIEWSBS subsystem.

12. End iView Subsystem 

Automatically Starting the iView Engine

There are two scenarios to consider when setting up the iView engine to start automatically:

Starting the Engine Daily As A Scheduled Job

To setup iView engine to start daily (or weekly) at a scheduled time, enter this command to run in a scheduled job:


(This is the iView 4.01 startup command).

Library iView must be in the library list of the job at start; consider creating a job description that contains iView library.

The user must have adequate authority; user QSECOFR is shown but is not required.

To end the iView subsystem use the ENDSBS command:


This can be put in a scheduled job. The OPTION and DELAY parameters should be set as appropriate for the individual site.

If the above command does not work the typical cause of failure is the jobqueue. Check that the job queue is multithreaded and leads into a multithreaded batch subsystem. QS36EVOKE is multithreaded by default and leads into multithreaded subsystem QBATCH by default. On some systems sysadmins have changed the defaults or run with multiple copies of these.

Starting the Engine At IPL

Some users want to start the iView engine at IPL. To do so, one must insert code into the i5's startup program.

This work should be done by a qualified programmer.

To determine the startup program, check the value of the system value QSTRUPPGM

dspsysval qstruppgm

You must then find or retrieve the source to that program. You should then insert into the startup program as late in the program as possible this code:

rmvlible fmg
monmsg CPF2104

rmvlible iview
monmsg CPF2104

addlible fmg *first
addlible iview *first


rmvlible fmg
rmvlible iview

The user under which the iView subsystem is invoked must have adequate authority to run iView. User QSYS, under which the startup program runs, must have authority to use the profile under which iView is invoked.

See the remarks on jobqueue under Starting the Engine Daily as a Scheduled Job

Over Printing Removal

In versions subsequent to iView 5.2 over printing removal can be enabled by setting data area DSRMVOV to Y, and disabled with a value of N. Enabling over printing removal removes over printing on the input spool file so that:

  • The archived spool file does not have over printing.
  • The spool file handed to iDocs for merge does not have over printing.
  • The indices scraped for search values are scraped based on correct row/column locations.

[ Up To Index ]

pub/iviewengines.txt · Last modified: 2018/05/24 16:06 (external edit)