This parameter is used to control the output file name. There are three possible conditions:
| • | If this parameter is not specified, the file is saved as the original filespec with a .PDF extension. This is the default condition. |
| • | If Save.FullFileName contains a dot not followed by a slash (i.e., the indicator of any extension), then it is interpreted as a <filespec> and causes the output to have that filespec—i.e., full path and full file name. (This is equivalent to setting the Save.File and Save.Path properties.) |
| • | If Save.FullFileName does not contain a dot, the argument is interpreted as the directory where you want the output to go. The file will be placed into that directory and the output filename will be xxxxx.pdf, where xxxxx is the original file name. (This is equivalent to setting the Save.Path property.) |
Note that the <filespec> or path may be in native or AMOS format and contain %env% variables, as well as macros. Also note that the directory will be created if necessary, provided that its parent exists and allows write privileges.
Examples
Assuming that the file being printed is c:\vm\miame\dsk0\007006\test.txt:
//; following will output c:\temp\test.pdf
//PDFX,Save.FullFileName,c:\temp
//; following will output c:\temp\x.pdf
//PDFX,Save.FullFileName,c:\temp\x.pdf
//; self explanatory...
//PDFX,Save.FullFileName,%miame%\pdfdir
//PDFX,Save.FullFileName,PDFDIR:
Notes
FullFileName distinguishes between filenames and paths that have dots in them by whether the dot has a slash to the right of it. For example, "//PDFX,Save.FullFileName,\\mydomain.com" is treated as a file, whereas "//PDFX,Save.FullFileName,\\mydomain.com\" is treated as a directory.
Warning: unless the filespec is AMOS-compatible, you must include an absolute path. For example, “//PDFX,Save.FullFileName,test.pdf” will default to the current directory because it is AMOS compatible and thus will be converted to an absolute path using the standard A-Shell AMOS-to-native conversion logic. But “//PDFX.Save.FullFileName,this is a test.pdf” will not. And relative directories are not recommended because they will be interpreted relative to the driver’s directory context rather than the A-Shell job’s context.
Compatibility
Same in PDFXv3 and PDFXv5+.
