It appears that you have to specify the paths as separate include statements.
I would use a USS REXX script using readdir and build the include statements. I've done something similar to chase file names down from a starting directory to build a second shell script for a bunch of sed commands. On Tue, Sep 29, 2020 at 5:53 PM Sean Gleann <[email protected]> wrote: > I'm currently investigating the use of DFDSS DUMP PATH to secure data held > in UNIX files and folders. > > As far as I can see, I have to specify the WORKINGDIRECTORY to establish > the starting point for the DUMP operation, then use INCLUDE to _explicitly_ > specify the files I want. The available documentation states: > "DFSMSdss does not provide wildcard support when processing UNIX files." > which, for my purposes, is a complete show-stopper. > > The subject UNIX folder contain many hundreds, perhaps thousands, of > individual files and sub-folders (and sub-sub-folders, etc). What I want to > do is to dump the complete contents of a UNIX folder in a way analogous to > dumping all z/OS files with a common set of HLQs. > > I can see a possible method of including a massaged version of 'ls' output > in the INCLUDE parameter, but I don't see this as a particularly workable > solution. > > Am I reading things wrongly and missing a vital point here? Does anyone > know if wildcard support is something that will be made available in the > future? > > Also, with a DUMP of data comes the requirement to be able to RESTORE it to > - possibly - a different WORKINGDIRECTORY, but I haven't got that far yet. > > Regards > Sean > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
