Endevor

  • 1.  Does anyone have detailed instructions for setting up Deploy for Test?  The manual just isn't detailed enough.

    Posted Oct 25, 2018 05:50 PM

    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.



  • 2.  Re: Does anyone have detailed instructions for setting up Deploy for Test?  The manual just isn't detailed enough.

    Posted Oct 29, 2018 05:47 PM

    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.

    • Create one or more Subsystems in your Test Target locations. You can name them anything you like. A good idea is to use resource names that your developers will recognize - like names of testing CICS regions. Make sure that for each subsystem you define, the NEXT SUBSYSTEM value is 'DEPLOY4T' .  For example, if you want to provide developers with a D2T target for a CICS region named CICSTST3, name the Subsystem CICSTST3.
    • Allocate Endevor libraries for your new D2T Subsystems. Whatever libraries you define for your other subsystems, allocate similar ones for your new D2T Subsystems.

     

    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.

     

    • Define Site Symbols using the target name within each Site variable.  With each Site variable append a 3-byte suffix to indicate the kind of library. The D2T doc suggests using ONL for a CICS load library. Using that suggestion, then a site symbol for our example would say #CICSTST3ONL = 'TST3.CICSLOAD'.  If you wanted to name a DBRM library for CICSTST3, then you might have a site symbols say #CICSTST3DBR = 'DBT3.DBRMLIB' .
    •  Include a step (typically in your MOVE processor) that copies to the non-standard libraries named for your D2T target.  Use ENXMOVE in your CSIQOPTN dataset as an example.  A BSTCOPY step might include, for example, DSN=&#&C1SUBSYS.ONL  

     

    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.



  • 3.  Re: Does anyone have detailed instructions for setting up Deploy for Test?  The manual just isn't detailed enough.

    Posted Nov 20, 2018 11:59 AM

    Dan,

    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,

    Sue



  • 4.  Re: Does anyone have detailed instructions for setting up Deploy for Test?  The manual just isn't detailed enough.

    Posted Nov 26, 2018 09:54 AM

    Hello Sue.

    You may be able to skip using the SITETRG symbolics, if:
    - You do not need to rely on Site symbols for output dataset names
    - Your processors have alternative method for determining the construct of Site Symbol variables for output names.
    Your processor can use the &C1ACTION variable, for example. Or, check to see whether the Site Symbol for the Target (assigned to a processor symbol ) is empty - something like:
    //   IF (&OUTTARG GE 'A')  THEN ...
        


  • 5.  Re: Does anyone have detailed instructions for setting up Deploy for Test?  The manual just isn't detailed enough.

    Posted Nov 27, 2018 11:32 AM

    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 Beckwith
    Technical Writer