Passing Additional Parameters to evilp

Evilp version 3.3.1.232 and higher includes the ability to pass up to ten optional parameters to FormFusion in the call to evilp. These extra parameters can be used to send over a Banner username, one-up number, or any other information you wish from the calling program. Each parameter is a FormFusion system variable that can be used anywhere in any template.

It is important that you communicate with your template developers in regard to what information is being passed over in which extra parameters. Developers only see the system-defined parameter names, and will need to know which ones contain the information they need. Keep in mind that if you make a change to one of the extra parameters at a future date, any templates using that parameter may be affected.

To include some or all of the extra parameters in the call to evilp, add in additional flag(s) -extraparam1 through -extraparam10 as follows:

UNIX Banner environment (gjajobs.shl)

EVIPRINT="$EXE_HOME/evilp $EXE_HOME/evicfg -eviproc $1 -evispp $FORM -eviinput $H/$TEMP.$EXT -eviout /tmp/ -extraparam1 $BANUID –extraparam2 $ONE_UP –extraparam5 $somevariable -evipthru $PRNTOPT -eviprint $PRNTFF"

Windows Banner environment (sctban.pm)

open(PRNT,"|d:\\sct\\banner\\general\\exe\\evilp d:\\sct\\banner\\general\\exe\\evicfg \-eviproc ${sctban_process_name} \-evispp ${sctban_form} \-eviinput ${sctban_file_name}.lis \-extraparam1 ${sctban_user_id} \–extraparam2 ${sctban_oneup_number} \–extraparam5 ${somevariable} \-eviprint print \/D\:${sctban_printer_name} \-evipthru print \/D\:${sctban_printer_name} >${sctban_file_name}.log 2>${sctban_file_name}.log");

UNIX Colleague environment (lp script)

case $ISFF in
     FF)    /usr/bin/evilp /usr/bin/evicfg -eviout /tmp/ -eviproc $1 -evispp $2 -eviinput $EVIINPUT -extraparam1 $SOMEVAR
            –extraparam2 $SOMEVAR2 –extraparam5 $SOMEVAR3 -eviprint $DESTINATION 1>/dev/null 2>/dev/null ;;
     *)    /usr/bin/lpp $1 $2 $3 $4 $5 $6 $7 $8 $9 ;;
esac

Windows Colleague environment (evicfg file)

Use a plain-text editor to open the evicfg file in C:\Program Files\Evisions\FormFusion\VirtualDriver. Add any optional parameters needed:

-evimapsip = MAP server IP or hostname
-eviuser = username
-evipass = password
-extraparam1 = variable1
-extraparam2 = variable2
-extraparam5 = variable3

Note: making subsequent changes using EvilpConfig.exe will overwrite any customizations to your evicfg file, so make sure to keep a backup.

 

You can use any or all of the extra parameters, and they do not need to be listed in any particular order or sequence. In the Banner examples above, -extraparam1 is being used to pass over the Banner username, -extraparam2 contains the one-up number, and -extraparam5 is sending over “somevariable” (either a system variable or another variable previously defined in gjajobs.shl or sctban.pm).

Note: -evipthru (if used) and -eviprint should always be the last two parameters since they can contain additional print flags. Otherwise, the parameters following the call to evicfg can be specified in any order.

 

For Banner users, if you have configured everything correctly, the extra parameters appear in the process log file as follows:

evilp version 3.3.1.232
  UserName: ffuser
  Environment: TEST
  Process: fpapord
  PrintCommand: lp -c -dhppurple
  Connection Override:
  PassPrintCommand:
  InputFileName: fpapord_12345.lis
  SpecialPrintParams[0]: PO_1
  ExtraParam1: jsmith
  ExtraParam2: 12345
  ExtraParam3:
  ExtraParam4:
  ExtraParam5: contents of somevariable
  ExtraParam6:
  ExtraParam7:
  ExtraParam8:
  ExtraParam9:
  ExtraParam10:
Processing is complete

The extra parameters are stored in FormFusion system variables, which you can use anywhere in FormFusion. For information on how to use these variables in a template, please refer to the in-product Help.

The FormFusion system variables

The FormFusion system variables