Output Manager FAQs
Q. Is there an API (Application Programmer’s Interface) available for the Emtex Output Manager software?
A. Yes, it’s called the VPI and is available for you to incorporate into your own programs or workflow. Code libraries are supplied as well as examples and documentation to enable you to link Emtex control routines into your code.
Q. Why don't our Emtex modules show up? We have three of one input, but only one is shown.
A. It's up to you to replicate the appropriate .cfg file in systempath:\config the appropriate number of times. Each replication adds another client in the input/output client window. Some input modules have a port requirement, usually around 6000; if these modules are replicated, then a unique port must be assigned to each client in the replicated .cfg file.
Q. What ar the Emtex Port requirements in a client/server setup?
A. Ports 6000-6030 are used by various Emtex input modules, with gaps left for multiple modules of each type. Emtex output modules do not have any extra port requirements. The client PC needs access to the server fileshares, using Windows networking, and so a minimum of port 139 must also be open for TCP. If you want to allow the full "chatter" of windows, then you should open ports 137 - 139 (TCP and UDP).
Q. I am having trouble with an Emtex PS file with BANNER and STOCK3 stock calls and a mysterious FEED0 assignment. Running the job without any PSIN_STOCK or PS_FEED statements gives messages about requiring PSIN_STOCK calls with T:BANNER and T:STOCK3. When we put these in, it runs, but complains about FEED0 not being assigned. Where is this FEED0 call coming from?
A. The following ps command is used on the first and last (banner/trailer) pages: /MediaPosition 0.
This will always default to PSIN_STOCK0 as stated on page 51 of the VIP 8.9 PS2VDD command guide, so the behaviour you described is expected. I believe this can be overridden by mapping PSIN_STOCK0 manually to one of the ?Media Type () commands used in the postscript data, e.g. PSIN_STOCK0=STOCKREF,S:1,W:75,T:BANNER and the corresponding FEED command would be: PS_FEED_STOCKREF=595 842 75 ORANGE PLAIN.
Note that 'STOCKREF' in these commands is arbitrary; any string can be used.
Q. How does the Emtex TIF2VDI utility work?
A. This is a command-line utility, which takes an uncompressed .TIF file and converts it to an Emtex .VDI (Virtual Image) file. Environment variables need to be set, a .SET file must be correctly setup for TIFP location, and the input and output primary filenames must be passed on the command line. The following batch file does this for you:
===========================
@echo off
SET VIPCFGP=c:\vip8.5\config
SET VIPCFGE=cfg
C:\vip8.5\bin\TIF2VDI c:\vipuser8.5\set\a4.set %~n1 %~n1
===========================
A desktop shortcut to this process allows you to simply drag and drop a .TIF file onto the shortcut and the .VDI file is automatically generated and placed into the VDIP folder, as specified in the .SET file.
Q. Is the P/I Output Manager profile option PDFIN_USE_OVERLAYS or PDFIN_USEOVERLAYS?
A. Actually, EITHER will work. You could even have PDF_IN_USEO_VERL_AYS! ALL "_" symbols are removed internally before processing, so feel free to sprinkle them around to halp readability in your scripts. The Output Manager documentation has liberally used "_" in all keywords for readability.
Q. I want to zip all the files resulting from my Emtex SPLIT processing. If I try to use a POSTJOBCOMMAND in the Profile, it executes for every SPLIT. How can I make it happen only at the end of the job, and when all output processing has concluded?
A. The trick here is to use a POSTJOBCOMMAND, inserted by the vde script into the profile, only when ENDOFJOB comes true. In the final vde script Pass, make a call to a REGION object, which has TEST ENDOFJOB. Create ACTIONS to build a POSTJOBCOMMAND string and put it into the Profile with PROFILEOPTION. Now this command will only be executed once, after all output has finished.
Q. If I am given a Metacode file and know nothing about it, is it possible for Emtex to tell me what resources are required to process it?
A. There are two levels to this:
The first is the record wrapping:
However, the record structure itself is described by the JDL/JDE pair as follows:
Hint: The JDL/JDE pair is used in the START statement which MUST be entered on the Xerox printer to process the job.
If you have the JDL/JDE pair and files, then you can process the job up till it calls for a resource. It then errors out, saying it cannot find the (first) xxxxxx resource. You can drop in a dummy resource, re-run the job and then get the next missing resource name etc. There is a command to ignore resource errors, which then gives you a complete list of what the job calls for.
To summarise, you MUST have at least the JDL/JDE names and files to process a Metacode job through Emtex.
A. Yes, it’s called the VPI and is available for you to incorporate into your own programs or workflow. Code libraries are supplied as well as examples and documentation to enable you to link Emtex control routines into your code.
Q. Why don't our Emtex modules show up? We have three of one input, but only one is shown.
A. It's up to you to replicate the appropriate .cfg file in systempath:\config the appropriate number of times. Each replication adds another client in the input/output client window. Some input modules have a port requirement, usually around 6000; if these modules are replicated, then a unique port must be assigned to each client in the replicated .cfg file.
Q. What ar the Emtex Port requirements in a client/server setup?
A. Ports 6000-6030 are used by various Emtex input modules, with gaps left for multiple modules of each type. Emtex output modules do not have any extra port requirements. The client PC needs access to the server fileshares, using Windows networking, and so a minimum of port 139 must also be open for TCP. If you want to allow the full "chatter" of windows, then you should open ports 137 - 139 (TCP and UDP).
Q. I am having trouble with an Emtex PS file with BANNER and STOCK3 stock calls and a mysterious FEED0 assignment. Running the job without any PSIN_STOCK or PS_FEED statements gives messages about requiring PSIN_STOCK calls with T:BANNER and T:STOCK3. When we put these in, it runs, but complains about FEED0 not being assigned. Where is this FEED0 call coming from?
A. The following ps command is used on the first and last (banner/trailer) pages: /MediaPosition 0.
This will always default to PSIN_STOCK0 as stated on page 51 of the VIP 8.9 PS2VDD command guide, so the behaviour you described is expected. I believe this can be overridden by mapping PSIN_STOCK0 manually to one of the ?Media Type () commands used in the postscript data, e.g. PSIN_STOCK0=STOCKREF,S:1,W:75,T:BANNER and the corresponding FEED command would be: PS_FEED_STOCKREF=595 842 75 ORANGE PLAIN.
Note that 'STOCKREF' in these commands is arbitrary; any string can be used.
Q. How does the Emtex TIF2VDI utility work?
A. This is a command-line utility, which takes an uncompressed .TIF file and converts it to an Emtex .VDI (Virtual Image) file. Environment variables need to be set, a .SET file must be correctly setup for TIFP location, and the input and output primary filenames must be passed on the command line. The following batch file does this for you:
===========================
@echo off
SET VIPCFGP=c:\vip8.5\config
SET VIPCFGE=cfg
C:\vip8.5\bin\TIF2VDI c:\vipuser8.5\set\a4.set %~n1 %~n1
===========================
A desktop shortcut to this process allows you to simply drag and drop a .TIF file onto the shortcut and the .VDI file is automatically generated and placed into the VDIP folder, as specified in the .SET file.
Q. Is the P/I Output Manager profile option PDFIN_USE_OVERLAYS or PDFIN_USEOVERLAYS?
A. Actually, EITHER will work. You could even have PDF_IN_USEO_VERL_AYS! ALL "_" symbols are removed internally before processing, so feel free to sprinkle them around to halp readability in your scripts. The Output Manager documentation has liberally used "_" in all keywords for readability.
Q. I want to zip all the files resulting from my Emtex SPLIT processing. If I try to use a POSTJOBCOMMAND in the Profile, it executes for every SPLIT. How can I make it happen only at the end of the job, and when all output processing has concluded?
A. The trick here is to use a POSTJOBCOMMAND, inserted by the vde script into the profile, only when ENDOFJOB comes true. In the final vde script Pass, make a call to a REGION object, which has TEST ENDOFJOB. Create ACTIONS to build a POSTJOBCOMMAND string and put it into the Profile with PROFILEOPTION. Now this command will only be executed once, after all output has finished.
Q. If I am given a Metacode file and know nothing about it, is it possible for Emtex to tell me what resources are required to process it?
A. There are two levels to this:
The first is the record wrapping:
- is the file blocked or unblocked?
- are the length bytes inclusive or exclusive of themselves?
- what order are the length-bytes interpreted (Most Significant Bit first or Least Significant Bit first)?
- how many bytes from the length bytes to the record?
- etc., etc.
However, the record structure itself is described by the JDL/JDE pair as follows:
- is the record ASII or EBCDIC?
- where in the record is the carriage control character?
- is it Machine or Ansi carriage control?
- what is the DJDE string?
- what other modules are included (FORMs etc. which can include other objects)?
Hint: The JDL/JDE pair is used in the START statement which MUST be entered on the Xerox printer to process the job.
If you have the JDL/JDE pair and files, then you can process the job up till it calls for a resource. It then errors out, saying it cannot find the (first) xxxxxx resource. You can drop in a dummy resource, re-run the job and then get the next missing resource name etc. There is a command to ignore resource errors, which then gives you a complete list of what the job calls for.
To summarise, you MUST have at least the JDL/JDE names and files to process a Metacode job through Emtex.
