The situation is the type definition is defined as data and in the processor group there are no processors defined (*NOPROC*). The need is to be able to ship this data to a remote site using Endevor's package ship.
Release: All Supported Releases
There is a way to allow just source code that is stored in Endevor to be shipped to a remote location.
On the type definition panel these are the files that are defined:
BASE/IMAGE LIBRARY ===> iprfx.iqual.BASE1
DELTA LIBRARY ===> iprfx.iqual.DELTA1
INCLUDE LIBRARY ===>
SOURCE O/P LIBRARY ===> iprfx.iqual.SOL
The source output library that is defined in a type definition is unique since the add and move actions are part of the Endevor internal processing when a generate or move processor is not defined to the type you are using.
When a element is added to Endevor we check to see if there is a processor group. If not (and there is source output library defined), we execute a internal processor called BASICGEN. This will copy the element out of Endevor and put it in the source output library that is defined in the type definition. When a move is done, we move to the next stage (same type) and a copy of the member is put in the new source output library. A delete is also done automatically to clean up the previous stage source output library. When the add or move action is run in a package, again the internal software is invoked to create a backout member of the elements along with the action processing previously defined.
The source output library should be defined as a PDS with the attributes of
Any element that does not have a backout record will not be part of the package ship process.
The following errors will be displayed if no backout records are defined and the package ship is executed:
C1BMX03E INPUT VERIFICATION FAILED - RC 0012
C1BMX21E PACKAGE 'TESTING ' HAS NO BACKOUT RECORDS - CANNOT BE STAGED