We have a large number of Windows Elements, each goes into a specific directory. Is there an easy way of associating each element with a destination folder?
In other words, could we create a single file which contains all the associations and then as elements are promoted, it could look up the destination folder on the server?
Option 1: If all files reside under the same directory tree
Set up an target file on any machine with a base directory such as( this option requires an Alchemist System Agent running on the target server):
TFILE8(TYPE(COPY) SCHEME(FILE) DOMAIN(QA) PATH(C:/SampleApplications) CALLABLE)
Include sub path names in the entity name, such as:
Entity Name: HelloWorldNET/res/HelloWorldNET.rc2
This will result in the following file on the QA machine: C:/SampleApplications/HelloWorldNET/res/HelloWorldNET.rc2
Option 2: If the files reside in various directory trees
Set up an target file on any machine with a dummy directory such as:
TFILE8(TYPE(COPY) SCHEME(FILE) DOMAIN(QA) PATH(C:/DUMMY) CALLABLE DYNAMIC)
Code OBPCL routines to override the dummy target directory based on the entity name and a location control file.
NOTE: Alchemist 5.2.1
Because this version does not support non-Z/OS target files this must be performed entirely with PCL. You would have to set up a control file, write the PCL to read the control file and transfer the source file to the desired location.