11.07.2015 Views

NetEx EFT213 Reference Manual Rel 5.4

NetEx EFT213 Reference Manual Rel 5.4

NetEx EFT213 Reference Manual Rel 5.4

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Host aliases can translate only into a single host command. This is not typically a problem since most hostssupport command procedures or script files which can then be accessed by a Host alias.The remainder of this section is devoted to issues relating to <strong>NetEx</strong>/eFT aliases. The topics apply to host aliasesas well unless specifically designated as “<strong>NetEx</strong>/eFT Aliases”.Creating Multicommand <strong>NetEx</strong>/eFT AliasesAn alias can translate to a single <strong>NetEx</strong>/eFT command as shown above where FETCH was mapped toRECEIVE. <strong>NetEx</strong>/eFT aliases can also be defined to be a sequence of several commands. The method fordefining a multicommand alias is to put each command of the definition on a separate line, where each line,except for the last one, is terminated by the escape character ‘!’. The escape character tells <strong>NetEx</strong>/eFT to continuethe alias definition on the next line. The following is an example of a three line FETCH alias that connectsto HOSTA, receives a file called ‘sourcefile’, then disconnects:eFT> set alias fetch connect hosta guest netex !More>> receive sourcefile !More>>disconnectThe SHOW ALIAS command can be used to display the new FETCH alias:eFT> show alias fetcheFT: FETCH ............... connect hosta guest netexeFT:receive sourcefileeFT:disconnectNotice that <strong>NetEx</strong>/eFT strips the ‘!’ from the alias definition. It is only needed for the initial definition of thealias.Although they are very powerful, multicommand aliases are limited to roughly 500 characters in length. It issuggested that if an alias approaches this limit, it should be made into an input script and stored in a file.Unlike single command aliases (such as the simplest FETCH alias defined earlier), multicommand aliases donot implicitly pass command parameters or qualifiers through to the actual <strong>NetEx</strong>/eFT commands.<strong>NetEx</strong>/eFT has no way of determining which command a particular parameter is destined for unless the aliasis set up to pass its own parameters, as explained in the next section.Passing Parameters to an AliasWhen creating multicommand aliases, it is often desirable to allow parameters to be passed on the alias commandline. These parameters can then be substituted into various places within the command sequence in thesame way as was done for input scripts.Refer back to the FETCH alias defined in the previous section. To make that alias more flexible, one can defineit to take as parameters such things as userid and password on the CONNECT line, and file name on theRECEIVE line. The definition then is:eFT> set alias fetch {} connect hosta {1} {2} !More>> receive {3} !More>>disconnectNote the empty ‘{}’ above. These are important when defining alias parameters and will be discussed shortly.The resulting alias becomes:eFT> show alias fetcheFT: FETCH .............. connect hosta {1} {2}eFT: receive {3}eFT:disconnectPage 98 Advanced Local User’s Guide REF-eFT213-R<strong>5.4</strong>-08

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!