Output file location for batch printing

Question

Hi all,
We have a current implementation of Oracle Documaker for our LOB. What we do is run a .BAT file that runs the GEN* brothers (gentnw32, gendaw32, and genptw32). This then uses the XML defined in the DATA segment of the fsisys INI file. This prints out multiple PDFs for us depending on the contents of the XML.
This workspace is a hand-me-down and works as is but with the new requirements, I need to direct the PDFs to a specific directory. Currently, it places them in the root folder/PRINT. This setup is not found on any line in the fsisys or fsiuser files. Is there a configuration I can make to have Documaker place it someplace else? Thanks!
We are using Documaker Studio Version 12.2.0.21451 Build Aug 8 2013. The workspace however was created with an older version (uses an MRL files rather than an ODBC connection)

Answer 1

Your question about scripting was as follows:
Can someone give me a brief explanation of what the lines: "SetGVM("PrtName001" ,file_name ,,"C",254)", "HaveGVM("PRTName001")", and "GVM("PRTName001")" do? I am confused since a DAL script named PDF_NAME is run when I execute GenData but it is not called in any line in the INI file (where is it called). It sets the GVM seen above but it does not reflect immediately when GV1 script and GV2 script are called in GenPrint. However, they are reflected when GV1 is run after POSTTRANSDAL for Batch1. Sorry about the confusing question. These three lines are found in separate DAL scripts.
First, anytime you want a basic explanation for most DAL functions, I would point you to the help. If you have the script open in the Triggers/Script manager in DMStudio and click on the function name, you should see the help panel reflect the function you click. You can also simply press F1 and find all the DAL help and browse it at your leisure.
GVM means Global Variable Member (or something like that). These are variables created and used during the server process - GenTrn, GenData, and GenPrint. Each program is responsible for creating the GVMs that it will used and only live within that program. The only way for GVMs to get "passed" to the next program is if these were written to a file that is subsequently loaded by the next program. For instance, the Gendata step creates the Batch (BCH) files mentioned in the other post. The content written to each recipient record in the BCH file is (typically) taken from GVMs. Then when GenPrint loads a particular batch record, those column values are again turned into GVMs. You may not have needed that lesson, but I thought it might be helpful in explaining the DAL rules you questioned.
HAVEGVM() is used to query whether a GVM actually exists. If it doesn't exist, then there is certainly no way you can get a value from it.
SETGVM() is used to 1) assign a value to an existing GVM; and 2) optionally create a new GVM if it does not already exist. In your case, the parameters to the SetGVM would appear to be allowing the variable creation identifying that it will hold character ("C") content with a max length of 254 bytes.
GVM() is a function that returns the value currently assigned to the named GVM.
So you see that your DAL script is capable of creating a GVM if it does not already exist. From what information you have, I don't know whether that is needed or not. It really depends upon your implementation.
Your PORT= statements define to run an associated script and that ultimately must be returning the actual starting name to use for that output. Assuming this is coming from GVM values, there's not enough information here to say where they are coming from. These could be taken from a column defined in your BCH files; or could be determine by some field value hidden (or otherwise contained) in your transaction data; or might be queried or created by some other scripting method.