From and administrators perspective I'm looking for step by step instructions to setup Deploy for Test target locations from a stage 1 development sandbox.
At a high level, here is what you need to do. The sample processor can do these things for you, but it is not absolutely necessary to use the processor.
The next 2 Steps are optional, and can be exercised if you want D2T to target non-standard library names. For example, if you want Endevor to populate a dataset named TST3.CICSLOAD for D2T actions to CICSTST3, then you would need to complete the next 2 steps.
The last step is also optional if you want your delete processor to automatically clean up D2T outputs. Use the example processor code ENXDCOMP within your Delete processor.
I have a question about the ENXMOVE processor. There is a symbolic &SITETRG. Does that need to be setup in the ESYMBOLS table and do I set that equal to Y also? I can't find any documentation on that value anywhere. &SITETRG=&C1SUBSYS.TRG.
Thanks for bringing this to our attention. We've added a User Story focused on adding more detail to the documentation to the backlog.All the best,Sam BeckwithTechnical Writer
Retrieving data ...