I have written an Endevor post-ship script and it is not working correctly.
search cancel

I have written an Endevor post-ship script and it is not working correctly.

book

Article ID: 14815

calendar_today

Updated On:

Products

Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench

Issue/Introduction

I have added information for a post-ship script.  The script is not working the way i want it to. 
How should the script be setup to execute properly?

Environment

All Supported Releases

Resolution

Script data sets are just like any other processor output file.  You create them in a processor and ship them to a remote location.  The difference is the symbolic substitution, which happens on the host side before the shipment takes place and the fact that they are NOT copied to a target dataset at the remote location.

There are 2 skeleton JCL members that you must update to do whatever you need to with the script file members at the remote location: #RJNVRA, executed after the remote copy step and #RJNDVRB, executed before the remote copy step.

These 2 skeleton JCL members are what contain the steps that process the script members.  There are samples in the documentation.

The last piece is the &ZZ symbols created that must be used in the #RJNDVA and #RJNVRB members.  The symbol is created from the last qualifier of the host script dataset name, prefixed with ZZ:  if your DSN=PUBLIC.TEST.SCRIPT then the symbols used in the #RJNDVRA and #RJNDVRB members would be &ZZSCRIPT.

The &ZZSCRIPT symbol resolves to the remote staging dataset name so the script members that are shipped (which are now in the remote staging dataset) can be used by the step added in the #RJNVRA and #RJNVRB members.