[ Up To Index ]
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
More...
At this screen you may work with the following header information:
Current releases only support an archive outqueue named IVIEW/IVWARCH. Do not change the default.
You must specify at least one line of archive recognition information:
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.
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
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
Option 12 from menu IVIEW will end the IVIEWSBS subsystem.
12. End iView Subsystem
There are two scenarios to consider when setting up the iView engine to start automatically:
To setup iView engine to start daily (or weekly) at a scheduled time, enter this command to run in a scheduled job:
SBMJOB CMD(STRIVWSRV IVWSRV(IVIEWSEVER)
IVWJOBQ(SRVJOBQ) IVIEWLIB('IVIEW') IDOCSLIB('FMG')
IVIEWLOG(*NO)) JOBQ(*LIBL/QS36EVOKE) USER(QSECOFR)
(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:
ENDSBS SBS(IVIEWSBS) OPTION(*CNTRLD) DELAY(600)
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.
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
SBMJOB CMD(STRIVWSRV IVWSRV(IVIEWSEVER)
IVWJOBQ(SRVJOBQ) IVIEWLIB('IVIEW') IDOCSLIB('FMG')
IVIEWLOG(*NO)) JOBQ(*LIBL/QS36EVOKE) USER(IVIEW_USER)
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
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:
[ Up To Index ]