Beyond FTP Feature Tour
Beyond FTP Script
Editor - If/Else/End_If Command
 Back
to Feature Tour
If -Else-End_If commands allow you to structure your
scripts. A single command may test for both the failure and success
conditions. They may be nested up to 100 levels deep.
1. An End_if command is always required to terminate an If command. The Else
is optional.
2. Conditionals can apply to all actions, or to those associated with each
server. This is called the scope. When you include the Each_Server clause,
the condition will be applied as the actions for each server are completed.
This allows failures to be detected, but limited to the server that failed.
3. The file Present condition does not include a check on the completion
status of previous actions. Since compound conditions are not allowed, you
must include two If-End_If statements to check for CompletedOK and Present
conditions.
4. The Stop command may be used anywhere within an If-End_If, and
immediately stops the script when encountered. Otherwise, the script
continues processing.
5. The name assigned to a CompletedOK condition may include blanks, but may
not exceed 19 characters. This is the name that appears in the distribution
status display for all parts of a particular If-End_If level.
Example:
:IF: Not Present {APTServe}c:\rtansfer\*.*,
5
:Alert: Mail = C:\Beyond FTP\trouble.mpf
:Stop:
:Else:
:From:{APTServe}c:\transfer\*.*
:To: c:\inbound\*.*
:IF: Not CompletedOK Inbound
:Alert: Mail =
C:\Beyond FTP\xferfailed.mpf
:End_If:
:End_If:
:IF: Present {APTServe}c:\transfer\*.*, 5
:From:{APTServe}c:\transfer\*.*
:To: c:\inbound\*.*
:Else:
:Stop:
:End_If:
Back
to Feature Tour
|
