NetEx EFT213 Reference Manual Rel 5.4

For example, if a user were to send the file PROGRAM.FOR to an z/OS host with a TSOPREFIX of SMITH,the resulting data set name would be SMITH.PROGRAM.FOR.Conversion to/from a Partitioned Data Set Name:and,For example, if a user were to send data set member SMITH.FOR(PROGRAM) from an z/OS host, the resultingfile would be PROGRAM.FOR.This conversion takes place at file transfer time when no destination file is specified on the SEND/RECEIVEcommand line. It assumes TYPE is always the last element or qualifier of a data set name and that it can bemapped to an EXTENSION. If these conversion rules do not map appropriately for a particular data set, it isalways safe to specify a fully qualified data set name (or entire path and file name) as the destination filespecification.Note also above that the current value of TSOPREFIX (which is equivalent to DIRECTORY) is prefixed ontoany destination data set name that is built unless it is a fully qualified data set (enclosed in apostrophes).See a description of the SEND and RECEIVE commands for IBM z/OS for further discussion on this topic.Source Wildcard Support for IBM z/OS File TransfersWildcarding is valid on the source file specification for both the SEND and RECEIVE commands. TwoNetEx/eFT wildcard characters have been defined in an attempt to standardize the wildcarding for all hostswhich can support it. These are:* matches zero or more characters within the current data set name level or member name of a partitioneddata set. For example, XXX.*DEF matches the data sets XXX.ABCDEF,XXX.CDEF, andXXX.DEF, but not XXX.DEF.ABC** Two asterisks together matches zero or more characters in all levels of a data set name. For example,XXX.XYZ** matches the data sets XXX.XYZ123, XXX.XYZ123.ABC.DEF, XXX.XYZ.ABC, andXXX.XYZ.? matches exactly one character within the current data set name level or member name of a partitioneddata set. For example, XXX.?DEF matches the data sets XXX.ADEF, XXX.BDEF, XXX.CDEF, butdoes not match XXX.ABCDEF or XXX.DEF.IBM z/OS NetEx/eFT supports wildcarding within data set names and member names of partitioned data sets.The wildcard characters can be combined to search multiple data set name levels. Wildcarding is also notallowed in the first level of a fully qualified data set name.Wildcarding under NetEx/eFT for IBM z/OS can be used to match sequential data set specifications, partitioneddata set specifications, or both. NetEx/eFT matches on only sequential data sets when no memberspecification exists. To tell NetEx/eFT to match only on partitioned data sets (and their members), append amember specification at the end of the data set qualifiers. Within the parenthesis must be either additionalwildcard characters or a valid member name. By default, NetEx/eFT looks for, and matches only on sequen-Page 54 File Handling Under IBM z/OS NetEx/eFT REF-eFT213-R5.4-08