Directory Transfer Tokens for Local and Remote File Names
$(SDIR)
This case sensitive token is used in the Local IFS File Path Name, Local File Name fields when using CFRCVIFSFP and CFRCVFPNL commands and in the Remote File Path Name field when using CFSNDIFSFP and CFSNDFPNL commands.
When using CFSNDIFSFP and CFRCVIFSFP commands all the sub directory names are added to this token location. If using CFSNDFPNL command all the file names are added to this token location. If using CFRCVFPNL command if the remote platform server is an IBM i system, all the file names else all sub directory names are added to this token location.
Example: For Send commands, you would set:
Local IFS File Path Name field:
For CFSNDIFSFP command: /LocalDirectory/*
Local File Name field
For CFSNDFPNL command: LocalLib/*
Remote File Path Name field:
For CFSNDIFSFP command: /RemoteDirectory/$(SDIR)/$(LocalFileName)
For CFSNDFPNL command: RemoteLib/$(SDIR)/$(LocalFileName) or /RemoteDirectory/$(SDIR)/$(LocalFileName)
Example: For Receive commands, you would set:
Local IFS File Path Name field:
For CFRCVIFSFP command: /LocalDirectory/$(SDIR)/$(RemoteFileName)
Local File Name field
For CFRCVFPNL command: LocalLib/$(SDIR)/$(RemoteFileName)
Remote File Path Name field:
For CFRCVIFSFP command: /RemoteDirectory/*
CFRCVIFSF, CFRCVIFSFP
If the Scan Subdirectories value is yes and there are files in both the remote directory /RemoteDirectory and in the remote subdirectories, then the same subdirectories are created in the local directory /LocalDirectory and local file names is given as $(RemoteFileName) token.
If $(SDIR) token is missing but Scan Subdirectories value is yes, then all the files from remote directory and all subdirectories are created in the local base directory. Their names are given by $(RemoteFileName) token.
CFRCVF, CFRCVFPNL
If the Scan Subdirectories value is yes and the remote platform is not an IBM i system and there are files in both the remote directory /RemoteDirectory and in the remote subdirectories, then the same subdirectories names are created in the local library LocalLibrary/ as the local file names. And the remote file names are created as the local member names and are given as $(RemoteFileName) token.
If the remote platform name is an IBM i system and there are file names in the remote library RemoteLibrary/ then the same remote file names are created in the local library LocalLibrary/ as the local file names. And the remote member names are created as the local member names and is given as $(RemoteFileName) token.
If $(SDIR) token is missing but Scan Subdirectories value is yes and the remote platform is not an IBM i system, then all the files from remote directory and all subdirectories are created in the local base directory. Their names will be given by $(RemoteFileName) token.
If $(SDIR) token is missing but Scan Subdirectories value is yes and the remote platform is an IBM i system, then all the files from the remote library are created in the local base library. Their names are given by $(RemoteFileName) token.
Subdirectories are created with the same access rights as the base directory. If some of the directories do not exist at the base directory path (for example, directory LocalDirectory from the Local File Name field), it is created with the same access as its base directory (RemoteDirectory), and all directories after it are created under it with the same access rights.
File Names are created with the same access rights as the base library. If some of the files do not exist at the base library path (for example, library LocalLibrary from the Local File Name field), it is created with the same access as its base library (RemoteLibrary) and all files after it are created under it with the same access rights.
All Send commands for $(SDIR) token must be used as part of Remote File Path Name field path in the form /RemoteDirectory/$(SDIR)/$(LocalFileName) or RemoteLibrary/$(SDIR)/$(LocalFileName).
If there are no subdirectory structures on the remote side (as on z/OS), then files from the remote side are placed in the local base directory and $(SDIR) are ignored.
$(MEMBER)
This case sensitive token must be used only for Receive commands from a z/OS system. It is used for a similar purpose as the $(SDIR) token, but we use a different token because dataset names work differently than directory names.
So, this token allows you to have file names on the local side that are the same as member names on the z/OS side.
If there is no $(Member) in the file name from the z/OS side, this token is not used. For example, if the path was /mftps/$(MEMBER)/filename , it becomes /mftps/filename.