Shipping Destination backup/SCL

[Jackie Barnes]

Hello!
We "lost" one of our 30 destinations last week due to an accidental delete.  We used the Build SCL For Shipment Destination action against one of our other destinations to build SCL to define a Package shipment destination and to define all data set and USS mapping rules associated with a Package shipment destination.  It worked but it was stressful as we had not experienced this before and we were doing it on the fly.

I created a "backup" job to build the SCL for all our destinations.  To split them apart, I need 30 steps in a single job, one for each destination or write a program to split the SCL into 30 individual datasets.  For now I am building a single dataset with all destinations.  

I am hoping someone somewhere has been down this road and can offer some advice.  I appreciate anything offered, except wooden nickels!  :-)

Jackie Barnes
Wells Fargo

[Phontilla Shuffitt]

hello Jackie,  I built a process that runs weekly to support versioning of the Shipment destinations I hope this helps you. 

Step 1)  ENBE1000 to execute - BUILD SCL FOR SHIPMENT DESTINATION "xxx" to a specific Dataset member replace if exists for each destination that is defined. 
BUILD SCL FOR SHIPMENT DESTINATION "abcd"
TO DSNAME "ENDEVOR.SHIPDEST" MEMBER "abcd" REPLACE .

Step 2)   C1BM3000 - to add each member into Endevor
//BSTIPT01 DD *
SET OPTIONS COMMENTS 'SHIPMENT DESTINATIONS' CCID 'ENDEVOR'
UPDATE OVERRIDE SIGNOUT.
SET FROM DSNAME "ENDEVOR.SHIPDEST" .
SET TO ENVIRONMENT 'ADMIN'
SYSTEM 'NDVR'
SUBSYSTEM 'ADMINSCL'
TYPE 'SCL' .
ADD ELEMENT '* '.

[Emlyn Williams]

We do daily backups in one step to PDS members with multiple SCL statements. For example our SCL DATA member contains
BUILD SCL FOR SHIPMENT DESTINATION 'DEST1'
TO DSNAME '<myhlqs>.BACKUP' MEM 'DEST1' REP
.                                          
BUILD SCL FOR SHIPMENT DESTINATION 'DEST2'
TO DSNAME '<myhlqs>.BACKUP' MEM 'DEST2' REP
.                                          
BUILD SCL FOR SHIPMENT DESTINATION 'DEST3'
TO DSNAME '<myhlqs>.BACKUP' MEM 'DEST3' REP

[Jackie Barnes]

I apologize for the delay in responding.  We migrated one of our LPARs that runs Endevor to RACF over the weekend.  It has been a whirlwind since then!  :-) 

Thank you both, Phon and Emlyn.  We are going to use Emlyn's suggestion after I recover from the intense V8 slap I gave myself!  We want each destination's SCL definitions to exist independently of the others.  We do not want to scramble to edit a single dataset down to the one destination we need.  

I also like the versioning aspect of Phon's.  We were thinking of creating the SCL in a GDG to accomplish similar results.  I like having Endevor maintain the versions!

Again, thank you both!!