Eform installation

See also: email installation for windows and pcl2pdf installation

spool.glm generates the final output files for eforms. 

• Eforms printed to laser printers will be in trash/r?????.pcl. They will always be black and white documents. 
• Eforms emailed will be in trash/r?????.pdf. Normally emailed eforms are black and white documents but as of 11/01/2016 we support color logos on eforms.  
• You'll probably never need it but eforms sent to a fax machine (over fax modem) will be in trash/r?????.pcl.

Eform installation is not automated because so much of it is custom. 

This page covers eforms for O/E invoices and A/R statements.  Eforms for letterhead are slightly different and are discussed on another page.

Pre-requisites:

• This is an add-on feature.  The customer must have already paid for the feature.
• AUX printing to local laser printers  attached to PC’s is NOT supported.   The printers must be network printers or connected to the Profits Plus server.

• If the customer has a custom orddoc.psm or forstm.psm then you must modify it to tell the printer which eform file to use.   See MVS orddoc.psm include and search for @EFORM.  You will need to make similar changes to the custom version of orddoc like:

IF INSTR(1,UCS(SYP’KEYWORD),”EFORM”)>0 THEN FORM’NAME=”EFIV01”

• You’ll need custom efiv01.pcl (invoice) and/or efst01.pcl (statement) files created for the customers eforms.  These are stored on MVS:/u1/mvs/eforms/usr/???/invoice/  and /stmt directories.    Where ??? is the customer's 3 character custom abbreviation in the site file.   As of 2/9/2017 Neil is the only MV person that has ever known how to create or modify eforms.   As a last resort you can contract with Jim Asman to create a new one (if he hasn't retired yet).  Back in 2004 he charged us $275 for a new form.

Spectra Colour Services Ltd.
10221 144a St.
Surrey, BC   V3R 3P7  CANADA

Telephone:

(604)584-0977   Bus.
(604)619-0977   Cell
(604)584-1471   Home
jlasman@telus.net

• If the customer uses the standard invoice or statement then  you might be able to just insert a new logo, header and trailer yourself.

• Full software update after 8/28/03.

Install pcl2pdf converter for email only:

If they have purchased the email add-on feature then put the pcl2pdf file converter program into their $MVS_ROOT/$MVS_PLATFORM/bin/pcl2pdf and make sure it is executable.  Click here for pcl2pdf installation instructions.  

You can have color logos on pdfs that are emailed.  Here's the instructions.

Site.ini file.

The filename of the converter needs to be in the site.ini file.  As of 3/32/06 the only name supported for both windows and unix is PCL2PDF. 

INI’PCL2PDF’CONVERTER=PCL2PDF

If they are using a converter other than pcl2pdf then put it in the bin directory instead and change the INI'PCL2PDF'CONVERTER parameter in the $MVS_ROOT/dsk0/100001/site.ini file 

 Note: As of 1/8/04 we only use  pcl2pdf.  Spool.glm is coded to work well with it.  If they don't use pcl2pdf then the spool.glm will probably need to be modified to pass different parameters to the alternate converter program's command line interface.

Install eform .pcl files in data directories:

• Each eform file will be custom .pcl for each customer. 
• They are stored in the data directories for each company. If a company directory does not have an eform file in it, no error will occur, but the file will print without a form.  Example: If company #3 still wants to print on their pre-printed forms for a while then don’t give company #3 a .pcl file yet.
• Put Invoice eforms in     $MVS_ROOT/dsk0/250???/efiv01.pcl
• Put statement eforms in $MVS_ROOT/dsk0/210???/efst01.pcl
• Put letterhead eforms in $MVS_ROOT/dsk0/??????/eflh01.pcl.  You will have to put the eflh01.pcl file in every module and every company where it might be used.
• Note:  The filename is important.  It must start with “ef” and have a .pcl file extension.  The 01 is a version number that keeps the form and program in sync.  The middle 2 characters “iv” are not important.

Install .syp files:

Install eform .syp files in S/M module data directories for each company. $MVS_ROOT/dsk0/100???

The S/M task 22. System printers screen requires special .syp files in the S/M module data directories for each company. $MVS_ROOT/dsk0/100???

Put a set of the following files into the customer’s S/M data directory for each company: If the customer has their own set of files in the MVS:/u1/eforms/usr/???/invoice or stmt directory then get the files from there, otherwise take the standard files from MVS:/u/mvs/dsk0/100001.

Make a list:

Discuss with the customer and compose a list of printers and terminals that should start using the eform feature.    You’ll need this list for the next 3 steps.

Make printers use HPLaserJet model in scoadmin:

This is how to change the printer model to HPLaserJet.

Add eform printers:

In S/M task 22. System printers, add a new eform printer for each existing printer that needs the ability to print eforms.

At Field “04. Model ID :” press TAB and enter EFORM at the search name.   This will give you a list of all EFORM models for email, fax and laser.   Choose the correct model.  Complete the record by adding meaningful memo text that will show on the printer selection screen.

Note: They can’t use the email and fax eform printers if they haven’t already purchased the email and fax add-on features.

Printer assignments:

Go to O/E task “32/17/2. Order entry printer assignments”   and change the printer names to their new EFORM printer for every terminal that should print eforms.

Do the same for O/E task “32/17/3. Holding file printer assignment”.  

 Recompile programs:

For invoice eforms recompile the following O/E programs so the new orddoc.psm include will be used.

orddoc, ohsdoc, forsiv

There is no need to recompile ordent and forent.  They use orddoc to print invoices. (except for Ridgways).

For A/R statements recompile forstm.psm

End of installation instructions