Need support so all files that can be TLD loaded can be included in a TLD deck

File system files can be loaded using OLD or TLD. OLD can load a file system file to any location. By default, a TLD can only load program base unique files. If customers want to allow a TLD to load files to other locations they must update user exit uelk.
When PROGCLEAR=YES is specified in a TLD deck, both programs and program base unique file system files are cleared in the target image, requiring that the TLD must include all required programs and program base unique files.

Currently bldtpf allows a single control file and single loadfile be input as parameters to create a TLD deck containing both programs and files. Control file attributes include whether a program should be included in a TLD deck or not (LOADONLINE, LOAD). No such attribute or mechanism exists to identify whether file system files in loadfiles should be included in a TLD or not. This means there is no reliable way to ensure all program base unique files defined in either tpf.loadfile or usr.loadfile (or any loadfile they include) are included in a TLD which creates an integrity issue for a TLD where PROGCLEAR=YES is defined; if a file is omitted from the TLD deck in error, then this can create online issues.

We need the build tools to be able to reliably ensure all files that can be TLD loaded are included in the TLD deck created by the bldtpf -tld command.