Autodnld INI Options

autodnld_home

This is the home directory for autodnld. Underneath this is the log and the scripts subdir. Example:

cdu_purge_depth

Intex does not encourage using this automated data purge. Please contact Intex with questions about maintaining data growth.

copy_flash_cdu

This is only available with versioin 5.04 and above, and applicable to clients who download flash CDU only.
To set this, add cdu_flash_cdu=1 in autodnld.ini file. With the value set,at the end of cmodata download, for every CDU/idx file in flash directory,autodnld will check whether the same CDU/idx exists in the non flash directory

• If the non flash file doesn't exist or older than the flash one, autodnld will copy the flash one on top of the non flash one.
• If the non flash file exists and newer than the flash one, it will delete the flash file
• This will happen independent of cdu_purge_depth setting

If you have this value set, the process can also be called directly from command prompt by typing

email_to (optional)

This is a comma-delimited list of E-mail addresses, so not include a space in the list. These addresses will receive any E-mail that the program sends.If this parameter is blank, no email will be sent. Example:

mail_bin (UNIX only)

This value will be eval'ed to produce a UNIX command, which we will then "system()" to mail the message. There are three variables that you should use in your Perl expression: For example, suppose we typically send email with a command like this: We would then supply the following Perl expression: (Note: on Windows, we use blat.exe, which uses command line arguments.

mail_exe (optional)

You can enter an alternate to running blat.exe here. By default, it takes the same arguments that blat would:

You can also use %FROM%, %TO%, %SUBJECT%, %FILE% in your command, and autodnld will replace these values. This usage of mail_exe will not append mail_exe_option. For example: If your mail server requires TLS, add these lines (replacing your_username@your_server_name.com below by your actual email address):
sendEmail is only supported in window version 5.04 and above. sendEmail is available to Linux/Unix users as a default from version 5.0u and above.

mail_exe_option (optional)

Autodnld window version uses blat.exe for email client. Type blat /? in a command window will print out syntax used by blat:
Autodnld will append file name and other information pulled from autodnld.ini file to the blat system call. Some user may have a SMTP server requiring username and password to login. User can add a line like this to autodnld.ini file. Autodnld will simply append those options to the end of blat system call.

mail_server (Windows only, and only if email_to is set)

This is the name of your SMTP server, which is typically some other machine on your network.

For information on troubleshooting autodnld emails, see the FAQ section for sending email under Windows.

mail_subject_prefix

If specified, this string will be added to the beginning of the subject line in all Autodnld emails.

mkdir_retry_cnt

Normally autondnld checks for the existence of data subdirs before unpacking data to them.

If the subdir is missing, autodnld will try to create the directory, and check again.

If you are running autodnld under Windows NT or higher (e.g. Windows 2000, Windows XP etc), autodnld will retry three times to make the subdirectory if it is missing, with a 10 second delay after each retry. (There is no retry for other operating systems).

You can set this retry count higher by adding a line like this to the .ini file: mkdir_retry_cnt=30

In the above example, autodnld would retry for about 5 minutes before giving up and returning an error

There is an optional debug feature: you can add one or more special letter(s) immediately after the count.

Here are three different examples:

where d=run "dir" if there is an error and put it the results in autodnld.log
where n=run "net use" if there is an error and put the results autodnld.log
where m=run "map" (for Novell users) if there is an error and put the results in autodnld.log

new_servers

Rarely used. This option provides a comma-delineated list of alternative servers to use if autodnld is unable to connect to the primary server specified by the connection line.

operating_system

Which operating system you are running under. Possible values are nt or unix. The operating_system flag is usually handled by the autodnld configuration program.

no_chdir_code_250

Occasionally, firewalls will not return a success code when changing directories on Intex ship servers. This option ignores resulting errors. Example:

password

This is an encrypted version of your password for the Intex ship servers. To change it, run "autodnld -config".

pool_data_purge

If you do not purge pool data, you can consume a lot of disk room. If you enter pool_data_purge=1 into the autodnld.ini file, older pool data will be erased. By default, no purging of pool data is done.

Please note that "pool_data_purge" is an on/off switch.

Once you have enabled pool_data_purge, there is a second ini file setting that determines how much data you leave behind before you start erasing older data. This is the "pool_data_months_back" setting. This same setting is also used to determine how much data is kept up to date when autodnld runs.
You may not need see "pool_data_months_back" in your ini file. If this is the case, a default value of 2 is assumed.

Example:
In this case, we will count backwards thru the month subdirectories, and once we have more than 6 occurances of a file, we will start the erase any older occurances. Then, if there a year subdirectory with no month data under it, we will erase the year subdirectory.

FYI: To settle a deal in the present, you only need the lastest pooldata. We recommend purging pooldata unless you are doing analysis of historical data. Also, there is always 24 months of pooldata available on the Intex ship servers, so you can load older data up to 2 years back if you decide at some point that you need it.

tgt_cdi_dir

This is the home directory for CDI files, which are part of the Intex database.

A typical value would be "tgt_cdi_dir=c:\intex\cmo_cdi" (or tgt_cdi_dir=/home/intex/cmo_cdi under UNIX).

Autodnld will create subdirectories under this home directory as needed.

tgt_cdu_dir

This is the home directory for CDU files, which are part of the Intex database.

A typical value would be "tgt_cdu_dir=c:\intex\cmo_cdu" (or "tgt_cdu_dir=/home/intex/cmo_cdu" under UNIX).

Autodnld will create subdirectories under this home directory as needed.

user

This is your username for your connection with the Intex ship servers. It is supplied supplied by Intex when we set you up for Internet access.

cdu_check_n_months_back

You only need to set this value if you don't want the default value of 2 months.
Ex: cdu_check_n_months_back=6
Normally, Intex supplies a QA file called cmostat.qa which contains a list of up to 2 months worth of cdu files.

For more information, see the DBStatus section of the manual.

Upon request, Intex will supply a QA file with a longer list, up to a maximum of 12 months worth of files. If you have requested this longer list, you may want to use it to QA more files in your database.

NOTE: this feature was first available in version 2.36 of autodnld.

connection

For https downloads, connection should be set to ship.intex.com. Make sure that you firewall is configured to allow connections from *.intex.com:443.

dbstatus_check

You only need to set this value if you want no dbstatus check.

To disable the check, (which is not recommended), set the value to none. Example:

dbstatus_check_time

By default dbstatus checks the time on the files and allows up to a 2 hour difference. Sometimes this causes false dbstatus errors in unusual circumstances. To bypass this set dbstatus_check_time=2. This does not check the time, but still checks the size.

dbstatus_ignore_file

This option is rarely used.

If you choose to replace an Intex file with your own file e.g. brokersp.inf (broker median speeds), and if you want to suppress dbstatus reporting that the brokersp.inf file is "damaged" (i.e. not the Intex file), you would add a line like this to the .ini file:

If you want to replace multiple files, list them separated by commas:

For Unix systems: this flag requires Windows style backward-slashes.

deal_remit_data_months_back

You only need to set this value if you don't want the default value of 2 months.

This applies to the Deal Remittance data product, which is different than the standard Remittance data files. When we download this data, we compare the files listed in a QA file with the files present on your file system for a certain depth. Any files that are missing or damaged are downloaded. Typically the downloaded files are the newest data files.

disable_ip_check

(version 3.20 and higher) In case of problems or when running with the "-ip" command Autodnld will connect to the Intex website. It can then determine what the IP address that Intex sees and check it against a list of valid IPs stored in the file log\valid_ips.log. So a successfull shipment must have been processed at one point for this to work. "disable_ip_check=N" will skip this check. NOTE: This is actually counter-intuitive with the name of the check, and setting it to "N" turns off this check.

distrib_subdir

(version 3.73 and higher) If the shipments are posted on our ship servers in a seperate subdir (very rare), then adding distrib_subdir=DIRNAME will force autodnld to look in that dir.

disk_space_cmd

You only need to set this value if you want to override the method used to determine disk room. This is sometimes necessary for a less common version of *NIX, or if you have trouble running the "dir" command from the Windows shell.

To use this parameter, write a small program in Perl and place it in the autodnld/scripts subdir. Give this program a name like diskspace.pl.

Within the program, use the "$szSubdir" variable to compute the disk room in bytes, and assign it to the value $iBytesAvaliable.

Then, add a line like this to the ini file:

Alternate usage: to disable all disk space checking, enter a line like this (starting with autodnld version 3.61):

disk_space_pattern

Autodnld looks for the phrase "bytes free" when doing a dir listing to get disk free space. To override this (if for instance you are using a non-English OS) you can set the pattern using this setting in the ini file.

file_download_retry_count

If a file cannot be downloaded from the ship server, the autodnld program may retry the download 0, 1 or 2 more times.

We do this because there may be occasional connection errors that cause a file download to fail, but these problems are often transitory.

The default value for the retry count is 2 (before 2004-03, the default value was 0 retries)

You can use an optional line in the ini file to change the retry count e.g. Permitted values for the retry count are 0,1 or 2. If you use an illegal value, the autodnld progam will stop with a fatal error

FYI: before 2004-03, we never retried for files larger than 80 mB; the limit has now been raised to 200 mB.

file_uncompres_retry parameters

If a file can't be uncompressed or swapped in to your destination folders, we have the ability to sleep and then retry. This can happen if there is a temporary network glitch or if a destination file is in use and can't be updated. Allowing Autodnld to retry will often fix any issues. There are 3 parameters that control this behavior

• file_uncompress_retry_count - default vaule is 1, after an initial failure to uncompress a file, this will control how many retries will happen before giving up
• file_uncompress_retry_sleep - default value is 1 second, after an initial failure, we will sleep this amount before retrying. This will often help if there is a network glitch or a file temporarily in use
• file_uncompress_retry_max_errors - default is 30, once we have this many failed uncompress errors in a given download, we will stop retrying upon unzip failures

Note: setting the retry count to 0 will eliminate any retries

get_id

If this is set to "Y", then autodnld will attempt to download intra day shipments. You need to be setup to receive intra day shipments for this to work. If interested, contact cs@intex.com.
Starting with autodnld version 5.02, you no longer need to add this parameter in your autodnld.ini file after you sign up with Intex client service. Autodnld will get the setting from Intex side. Example:

get_remit_diff_files

If this is set to "Y", then autodnld will download daily diff files for remittance data. Example:
Also see:
rmtd_data_days_back
tgt_rmtddata_dir

httpdump

Setting to 1 adds debug info to log file (also called verbose mode).
Typically, Intex will ask you to temporarily add this line when helping you troubleshoot. Example:

https

This parameter is required and will be set automatically upon installation
Autodnld will use https for all connections and file downloads. It will use the setting of connection for the target server.

http_session_header

This feature is only supported in autodnld version 5.03 or later.
For clients whose https connection must go through a proxy server, you can add the line below to configure your proxy server. Please note: On Windows, you can also use the win_https_wininet parameter to use the proxy server configuration used by your browser. On Unix/Linux, you can use the unix_https_curl parameter to use the curl command to make your connections.

http_save_ind_zip_path

This parameter is to specify a directory location for autodnld to save the individual .zip files for each file downloaded in a given shipment. The files will be stored in the location specified with a subdirectory for each shipment with the UTC time of that shipment. Example: c:\intex\ind_zip_path\1599661248\cmo_cdu-cmocusip.inf.zip Note: Autodnld will not clean up these folders and they can grow quite large, so it is important that you process them and clean them up yourself.

id_tgt_cdi_dir

This is the setting for the location of intra day cdi files. If this is not set, autodnld will use the tgt_cdi_dir location. This setting can only be one location. If you want files to be copied to other machines using replication, you can add the addition locations under tgt_cdi_dir. Autodnld will copy the file there. Example:

id_tgt_cdu_dir

This is the setting for the location of intra day cdu files. If this is not set, autodnld will use the tgt_cdu_dir location. This setting can only be one location. If you want files to be copied to other machines using replication, you can add the addition locations under tgt_cdi_dir. Autodnld will copy the file there. Example:

ignore_dbstatus_return

(version 3.33a and higher) Sometimes dbstatus returns a bad return code, even though it ran fine. Setting ignore_dbstatus_return=Y will ignore the return code, but will still check in other ways if dbstatus ran OK.

ip_script

(version 3.20 and higher) In case of problems or when running with the "-ip" command Autodnld will connect to the Intex website. It can then determine what the IP address that Intex sees and check it against a list of valid IPs stored in the file log\valid_ips.log. So a successfull shipment must have been processed at one point for this to work. Instead of using httpdump.exe you can set a different script name using this ini file setting.

ip_argument

(version 3.20 and higher) This sets the arguments in the ip check exe. Usually used in conjunction with "ip_script" setting.

kill_autodnld

Setting this value will force autodnld to kill all other autodnld processes when autodnld is launched. Be careful with this feature, and only use it if you have a problem with autodnld hanging or keeping the lock file open.

In order for this to work, it must be a Windows system. Also, the system must have pstools installed, so autodnld can use the utilities pslist, and pskill. Example:

To install pstools. please visit, www.sysinternals.com

log_file_max_length

Setting this value to a number will change the maximum length of the log files, instead of the default of 6000 lines.

mail_from (Windows only)

By default, autodnld uses this as the who the mail is from: Intex_auto_download. If you would like to change this to something like "autodnld on server1", use the mail_from directive e.g. For blat.exe users: using this directive will set the value of the "-i" switch.

mail_sender

By default, autodnld uses the machine name as the mail sender. Some mail servers will only accept mail from known senders, and thus will not accept mail from a machine name. To prevent this from happening, you would add a line something like this to your autodnld.ini file:

Even if you use this setting, when you receive the email, the contents of the "From:" field is still controlled by the "mail_from" setting in the .ini file (the default value if not defined is "Intex_auto_download")

If you are doing a new installation, and if you have autodnld version 2.53h or higher, we automatically set the "mail_sender" value to the first name listed in the "email_to" list. This is only a guess, but it often works, and you can always edit the .ini file and correct the value later on.

Tech note: blat.exe: using this directive will set the value of the "-f" switch

minimal_email

You only need to set this value if you want a bare minimum of email. If so, set the value to Y. You will still receive dbstatus error and other downloading errors, but information type emails (e.g.,start downloading,finish downloading, etc.) will not be sent.

pool_data_months_back

Default value =2. Set this value if you don't want the default value of 2. The value is applied to months,not on individual file. i.e.,If a file is not yet available in latest month, it will not check "pool_data_months_back"+1 month for that file either.

When you download pool data, you compare the files listed in a QA file with the files present on your file system for "pool_data_months_back". Any files that are missing or damaged are downloaded. Typically the downloaded files are the newest data files.
Be aware that pooltrak.log determines whether downloading the pooldata QA file or not.
Intex Solutions keeps 24 months of pooldata on its ship servers. By increasing the value of this parameter, you can backfill older pool data if you don't have it already (from shipments from earlier months).

Unless you have a special need for historical pool data information, Intex recommends that you leave this parameter set to 2. For more information on pool data purging, see the pool_data_purge command line argument.

pool_data_skip_geo

If you enter a line like this in the .ini file: autodnld will not download any .geo files.

These files can be quite large. Here is a set of files for one month:

post_download_command

Sets a command for autodnld to run at the end of each shipment. Autodnld will pause while the command is running. The command will run multiple times if you are processing multiple shipments. Adding a command like: will run "dir c:\Users" between downloads.

ps_command

When running the Perl script autodnld.pl under UNIX, we need to detect if autodnld.pl is already running. To do so, we obtain a process list by running the command "ps -af", and search the output for this sub-string: perl autodnld.pl.

If you want to use a different command (e.g. "ps -a") to obtain a process list, put something like this in the log/autodnld.ini file:

If you want to disable the multi-instance checking, put something like this in the log/autodnld.ini file:

remit_data_months_back

You only need to set this value if you don't want the default value of 2 months.

When we download remittance data, we compare the files listed in a QA file with the files present on your file system for a certain depth. Any files that are missing or damaged are downloaded. Typically the downloaded files are the newest data files.

redownload_count

If autodnld fails in downloading a shipment, it will not redownload files it was successful in downloading already. To force re-downloading the files, you can set redownload_count=0 to always redownload, or redownload_count=# to redownload on the #th attempt.

replicate_cmd

Autodnld no longer supports the replication feature. Intex recommends that clients look to their own IT support for a suitable backup/replicate solution if desired.

rmtd_data_days_back

This is for the remitdata daily diff files. You only need to set this value if you don't want the default value of 7 days.

When we download the remittance data daily diff files, we compare the files listed in a QA file with the files present on your file system for a certain depth. Any files that are missing or damaged are downloaded. Typically the downloaded files are the newest data files.

remit_data_prune

... not implemented yet...

This is a flag; set it to 1 to activate pruning of remittance data. By default, this parameter is totally missing from the .ini file and remittance data is not pruned.

If this flag is set, all remittance data greater than "remit_data_months_back" is removed. If "remit_data_months_back" is not specified, the default value of 2 is assumed.

send_histdata_email

Set this to Y to receive emails telling you which historical data files autodnld downloaded. This is turned off by default to minimize emails sent.

save_serialized_group_shiplist

For every Autodnld run, if there is any group data (pooldata, perfdata, ...) downloaded, Autodnld will create a file in the log folder called shiplist_group.UTC.txt that will contain a list of all the files downloaded. This shiplist file is a "|" delimited file with 3 columns: 1) The location of the file on the Intex server for Autodnld purposes, 2) The name of the file stored in your Intex data directory (fully pathed) 3) the size of the file in KB

To activate this option, add a line like this to your autodnld.ini file

The shiplist files will accumulate pretty quickly, so you should be careful to move them to an archive area or delete them regularly.

save_serialized_zip_files

Normally autodnld deletes zip files after it unpacks them. If you set this option, the file shipinfo.timestamp.zip from each shipment will be preserved in the autodnld/log folder Inside this .zip file is a file shiplist.txt. This file contains a list of the files downloaded in this shipment. Shiplist.txt is a "|" delimited file with 3 columns: 1) The location of the file on the Intex server for Autodnld purposes, 2) The name of the file stored in your Intex data directory (path relative) and 3) the size of the file in KB

To activate this option, add a line like this to your autodnld.ini file

The zip files will accumulate pretty quickly, so you should be careful to move them to an archive area or delete them regularly.

save_dbstatus_error_files

If there is a dbstatus error file, it will save the file as dbstatus_YYYYMMDD_HHMM.rpt. So a later change to the dbstatus.rpt will preserve the old error file. Example:

shipment_backup_path

This parameter will tell autodnld to backup the contents of each shipment (after it is downloaded and processed) to the folder specified. The contents will go under the path specified in a subfolder named for the date/time of the download, eg. 20201201_2201. Example:

skip_update_exe

(Version 3.20 and higher) When autodnld is run it will check for a new version of Autodnld and download it if it is available. Setting "skip_update_exe=y" will skip this.

skip_flash_prune

(Version 3.33 and higher) This is only effective when cdu_purge_depth>0 and client who receives flash CDUs.
During pruning process, autodnld default behavior will

• delete any flash CDUs older than 90 days
• delete any flash CDUs if a non-flash and later version CDU exists. If you set this value to "Y", it will skip this deleting process only. It will not effect 90 days cleaning process.

With version 5.04 and above, there is another parameter copy_flash_cdu added outside pruning process to copy flash CDUs and purge any stale flash CDUs.

suppress_log

(Version 4.0.0 and higher) Set suppress_log=y will not log each file being downloaded in http download process. Unless for debugging purpose, we strongly recommend setting this to avoid slowing down download process by logging.
Refer to the FAQ for details of http download method.

suppress_utc_check

Normally we download non-CMO data (pool data, etc) if the file stamp has changed, even though the size is the same.

You should not disable this feature if you cannot maintain stable time stamps on the Intex data files

If you do disable the utc check, we only download if the file is missing or has a different size

Example:

timeout

Timeout increases the amount of time before an error while downloading a chunk. Autodnld defaults to a timeout of 300. Try increasing the timeout if you see EC2014 or Error Code:2014 errors.

You may need to gradually increase the time out value until the issue goes away.

Sometimes the timing of downloading files conflicts with other processes running concurrently. It may help to change your scheduled task to a different time. Example:

temp_download_subdir

This is the folder that autodnld uses to temporarily store downloaded information prior to unpacking to final destination folders or a network drive. temp_download_subdir is set by the autodnld config script.
Here are some requirements to this folder:

• Spaces are not permitted in the pathname of this.
• Make sure autodnld can create the folder if not existing yet and have read/write access right to it.
• A minimum amount of 2G free space is recommended.
• If running on windows, a non-UNC path is required.
• We strongly recommend selecting a local folder for this purpose because we have seen issues reported by clients who were using a network drive for this.

Typically, users place the temp_download_subdir in a temp folder under autodnld home directory. Example:

NOTE: version 3.03 and up contain a feature that if a file in use error is returned when unzipping it will store the files in the "in_use" directory, which is created as a subdirectory of temp_download_subdir directory. At the end of download or prior to any new download it checks the "in_use" directory and copies any files waiting to be copied. It keeps a running log of files coppied, called Previously_copied.txt. This only applies to autodnld windows clients using pkzip32.

tgt_perfdata_dir

By default, perfdata is placed in a subdir "parallel" to the tgt_cdu_subdir. For example, if your ini file contained this line: the perfdata subdir would default to If you want to change the perfdata subdirectory, you could put a line like this in your ini file: Under the perfdata subdirectories, autodnld will create subdirectories like this: NOTE: as of 04/2001, the perfdata subdirectories are as follows:

• abag
• abal
• abau
• abcc
• abeq
• abfp
• abfr
• abhe
• abmc
• abmh
• abre
• abrv
• absb
• absl
• ag
• cmbs
• wl

Depending on which types of perfdata you have subscribed to, you may not have data in all of these subdirectories.

tgt_remitdata_dir

This is the home subdirectory under which "deal remittance data" is placed by autodnld.

This data is always placed in subdirs under the home directory.
The default location, if this is not set, is the location of the cdu files in a subdirectory called "deal_remit_data".
As of 9/2007, the subdirectories are as follows:

• ab_au
• ab_cc
• ab_eq
• ab_fp
• ab_he
• ab_mh
• ab_rv
• cmbs
• wl

Depending on which types of remitdata you have subscribed to, you may not have data in all of these subdirectories.
Examples:

tgt_remitdata_dir

This is the home subdirectory under which "remittance data" is placed by autodnld.

Remitdata is always placed in subdirs under the home directory.
The default location, if this is not set, is the location of the cdu files in a subdirectory called "remitdata".
As of 9/2007, the subdirectories are as follows:

• ab_au
• ab_cc
• ab_eq
• ab_fp
• ab_he
• ab_mh
• ab_rv
• cmbs
• wl

Depending on which types of remitdata you have subscribed to, you may not have data in all of these subdirectories.
Examples:

tgt_remitdata_dir

This is the home subdirectory under which "tranche remittance data" is placed by autodnld.

This data is always placed in subdirs under the home directory.
The default location, if this is not set, is the location of the cdu files in a subdirectory called "tranche_remit_data".
As of 9/2007, the subdirectories are as follows:

• ab_au
• ab_cc
• ab_eq
• ab_fp
• ab_he
• ab_mh
• ab_rv
• cmbs
• wl

Depending on which types of remitdata you have subscribed to, you may not have data in all of these subdirectories.
Examples:

tgt_rmtddata_dir

This is the home subdirectory under which remittance daily diff data is placed by autodnld. The default is the tgt_remitdata dir.

As of 11/2005, the subdirectories are as follows:

• ab_au
• ab_cc
• ab_eq
• ab_fp
• ab_he
• ab_mh
• ab_rv
• cmbs
• wl

Depending on which types of remitdata you have subscribed to, you may not have data in all of these subdirectories.
Examples:

try_alternate_server

Rarely used. Intex has standardized shipping to use ship.intex.com. This can be "y" or "n", with "y" as the default. If set to "y", if there is an error connecting to the server listed in the ini file as connection=, autodnld will try alternate servers until it finds one that works.
The list of possible servers is: ship.intexmirror.com If you run autodnld in the test mode (at a command prompt type "autodnld -t"), it will ask you if you want to test the server. This will create a file log\available_servers.txt. Autodnld will then only check the servers listed in that file. You can also manually edit/create that file, listing one server per line.

upload_dbstatus

Autodnld is able to automatically upload dbstatus error reports directly to Intex for processing. Once Intex receives the file, a fix-up shipment will be processed and put on the Intex ship servers for autodnld to download. When this shipment is ready you should receive an email from Intex and the next time autodnld is launched the fix-up shipment is received. This will save the steps of packaging up the dbstatus report, and emailing Intex automatically.

To enable this feature you need to edit your autodnld.ini file with the setting upload_dbstatus=y. The default setting for this is "n". When a dbstatus error is found, autodnld will then upload the dbstatus report to Intex and the relevant files will be re-shipped.

Some firewalls settings do not allow autodnld to upload data to Intex. Please check with your IT group to see if this is allowed before setting upload_dbstatus=y.

unix_unzip_cmd

If you wish to use an alternate command to unzip on the Unix/Linux platform, you can specify it here. The default is to run ./unzip -o %FILE% In your custom command, %FILE% will be replaced by the name of the .zip file to be extracted. If you wish to use this parameter, you must ensure that your customer command extracts the file in the same way as unzip (force override of existing file, the destination is path relative, case preserving, ...)

unix_safe_unzip

Setting this parameter to 'y' will have the Unix/Linux version of Autodndld unzip to a temp dir and then call Unix/Linux mv command to swap in file. This should be used if you are having problems on Unix/Linux with swapping in files. It makes the time window for swapping in files much smaller and should avoid collisions with your users.

unix_safe_swap_file_cmd

Note: This option is very uncommon and only should be used with guidance from Intex and it needs to be used in conjunction with unix_safe_unzip If you want to use something other than the Unix/Linux mv command (i.e. a custom command to swap the files), then you can enter that custom command here, using %SRC_FILE% and %DST_FILE% in the command to represent the source file and destination file.

where the script can be something you create to that will swap the files.

unix_https_curl

Setting this parameter to 1 will allow you to use the native curl command to make your connections to Intex. The curl command will be constructed from the parameters in your HTTP_SESSION_HEADER parameter, as well as any custom curl options in your curl_options paramter. Please note: As of version 5.30 (and 5.30U), this option will work on Windows and Unix/Linux.

curl_exe

This allows you to use a fully-pathed version of curl when using the unix_https_curl option. If this parameter is not set when using that option, it will to default to searching for curl in the PATH environment variable.

curl_options

Setting this parameter will allow you to pass custom arguments to the curl command when using the unix_https_curl option. You can pass any options that are recognizable to the curl command, such as --tlsv1, --connect-timeout N, ...

win_https_wininet

Setting this parameter to 1 will have use your Windows default proxy server settings shared with your browser. This is the easiest way to configure a Windows machine that requires a proxy server.

win_safe_unzip

Setting this parameter to 'y' will have the Windows version of Autodndld unzip to a temp dir and then call Windows move command to swap in file. This should be used if you are having problems on Windows with swapping in files. It makes the time window for swapping in files much smaller and should avoid collisions with your users.

win_safe_swap_file_cmd

Note: This option is very uncommon and only should be used with guidance from Intex and it needs to be used in conjunction with win_safe_unzip If you want to use something other than the Windows move command (i.e. a custom command to swap the files), then you can enter that custom command here, using %SRC_FILE% and %DST_FILE% in the command to represent the source file and destination file.

where the script can be something you create to that will swap the files.

win_unzip_cmd

If you wish to use an alternate command to unzip on the Windows platform, you can specify it here. The default is to run pkzip32.exe -extract -nofix -over=all -directories %FILE% %DESTDIR% In your custom command, %FILE% will be replaced by the name of the .zip file to be extracted. In your custom command, %DESTDIR% will be replaced by the final destination folder for the file If you wish to use this parameter, you must ensure that your customer command extracts the file in the same way as unzip (force override of existing file, the destination is path relative, case preserving, ...)

Typical autodnld.ini file