pub:work_with_idriver_engines
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | pub:work_with_idriver_engines [2022/06/25 17:02] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Work with iDriver Engines ===== | ||
+ | The iDriver Engines processes spooled files that are contained in monitored | ||
+ | out queues that match certain spool file characteristics. Once a spooled file | ||
+ | appears in a monitored queue with matching spool file characteristics, | ||
+ | spooled file is archived based on the processing definitions of the iDriver | ||
+ | application. | ||
+ | |||
+ | Option 3 from the iDriver menu allows you to create the fist component, a | ||
+ | finishing server. Selecting this option will display the screen below: | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | Type options, press Enter. | ||
+ | 1=Select | ||
+ | | ||
+ | Opt Server | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | From this screen, pressing the F6 Key creates a new iDriver Server instance, | ||
+ | while entering an option 1 next to an existing server, will allow you to edit | ||
+ | the server. | ||
+ | |||
+ | Press F6 to create a new engine. Doing so will create an empty engine in | ||
+ | which the rules for processing spooled files may be established. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Originating | ||
+ | Library | ||
+ | F4=List | ||
+ | IDR400OBJ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Defining Engine Rules ===== | ||
+ | |||
+ | The column headings, originating library and out queue, point to the out | ||
+ | queues being monitored. | ||
+ | |||
+ | The next column, Spool Attribute, defines the spool file characteristic. | ||
+ | Pressing the F4 prompt key will reveal a list of valid spooled file attributes to | ||
+ | select. The illustration below displays the list when the cursor is in the Spool | ||
+ | Attribute column. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | | ||
+ | 1=Select | ||
+ | | ||
+ | | ||
+ | *FORMTYPE | ||
+ | *JOBNAME | ||
+ | *USER User Profile Name | ||
+ | | ||
+ | | ||
+ | F1=Help | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Press enter to confirm. | ||
+ | </ | ||
+ | |||
+ | Immediately following the Spool Attribute column is the Spool Value column, | ||
+ | which defines the value of the corresponding spooled attribute. | ||
+ | Lastly, the column labeled iDriver Application, | ||
+ | application that will be applied to spool file. | ||
+ | An iDriver Application may be defined using an option 1 off the iDriver menu. | ||
+ | It is an iDriver Application that contains all the requisite finishing options, | ||
+ | which will be used to process the spool file. Moreover, the iDriver application | ||
+ | will also determine which out put queue will be used to print the resulting | ||
+ | spooled file with the finishing options. | ||
+ | Pressing the F4 function key, when the cursor is positioned within this | ||
+ | column, will generate a list of existing iDriver finishing applications. This | ||
+ | screen below displays an example of a list of existing iDriver applications. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | QSECOFR | ||
+ | Select an iDriver Application | ||
+ | t Queue. . . . : DIRENGINE | ||
+ | 1-Select | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Application | ||
+ | F4=List | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | | ||
+ | | ||
+ | | ||
+ | + | ||
+ | F12=Previous | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | It should be noted that the original spooled file is persevered and a new | ||
+ | spool file is created from the original spooled file. Once the new spooled is | ||
+ | created, the original spooled file remains in the original out queue, or if an | ||
+ | archive out queue is defined in the server definition, then the original | ||
+ | spooled file is relocated to that archive out queue. In this way, those spooled | ||
+ | files that have been processed with finishing options are clearly segregated | ||
+ | from those files, which have not been processed. | ||
+ | |||
+ | ===== Starting iDriver Engine ===== | ||
+ | |||
+ | Once the iDriver applications have been associated with the iDriver Engine, | ||
+ | the last step is to start the iDriver Engine. To do so, place an 8 in the option | ||
+ | column next to the server instance from the list of available iDriver Engines. | ||
+ | |||
+ | Doing so will prompt you for the job queue to use for the iDriver Engine. By | ||
+ | default, the job queue QS36EVOKE is used. However, you may enter another | ||
+ | valid job queue instead. | ||
+ | |||
+ | < | ||
+ | Start iDriver Engine(STRIDRSRV) | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | In the above example the iDriver engine, MYENGINE, appears since this | ||
+ | would be the name of the engine, from which an option 8 is selected. Your | ||
+ | server name would likely be different. The iDriver Job Queue, QS36EVOKE, | ||
+ | is a default job queue that will be used to submit your server. Any other job | ||
+ | queue name may be used such as QBATCH, or QPGMR. Consult with your | ||
+ | system administrator to select the most appropriate job queue for running a | ||
+ | continuous job. |
pub/work_with_idriver_engines.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1