

Package Ship Facility › How to Enable Backout and Shipment for Natural Objects › Update Processors for Post-Ship Script Processing of Natural Objects
Update Processors for Post-Ship Script Processing of Natural Objects
To enable the Post-Ship Script feature, you must update your Move processor to add the steps that create your script output data sets for shipment and create backout records to enable backout of these data sets.
Follow these steps:
- Update your Move processor to insert any additional steps needed to build the required remote script Natural LOAD JCL syntax based on your site's requirements. For Natural objects, the additional steps for the Move processor must meet the following requirements:
- Write members to two PDSs, using the CA Endevor SCM element name as the member name. This requires that all objects being shipped have names that will be valid as member names of a PDS.
- The first PDS members contain the individual unload of the Natural objects. This is not a script file.
- The second PDS members contain a complete job step to write the Natural object to the remote Natural library after shipment. This data set must be identified as a (SCRIPT-FILE) during shipment. This is done through the mapping rules based on the shipment destination. For more information about the SCRIPT-FILE, see Define Mapping Rules for Post-Ship Script Data Sets.
- Because each Natural object is individually unloaded, each must also be individually loaded back to Natural.
- Because the script file members contain a complete job step, symbols can be used that will be substituted at shipment time based on the destination, through the destination configuration member of the CA Endevor SCM PARMLIB.
- You must be careful not to use existing processor symbols; &C1 symbol names are not allowed in the destination configuration member.
- Symbols, to be resolved at shipment time, can be used for the values: Natural nucleus name, parameters to the nucleus, and the remote target Natural library name.
- Update the CA Endevor SCM PARMLIB destination configuration member, if symbols are used in the script file members.
- Each destination that will receive the shipment must be updated to include the symbols used in the script file members.
- Each destination can have its own value for the symbols.
- Verify that MONITOR and BACKOUT keywords are specified on the script data set so that package processing can create backout records to track your script files.
- Name your script data set so that it is easy to determine its content. The final qualifier of the script data set will be used when building model control statements. So consider choosing an appropriate name so the different types of script processing can be determined. For example, an appropriate name might be NATCMD for the script file containing the Natural LOAD JCL steps.
Example: Model Code to Create Post-Ship Script Output Data Sets for Natural Objects
The following code sample added to the PNATMOV Move processor for Natural objects will enable package processing for shipment and backout, store unloaded Natural objects into PDS format, and put remote Natload JCL into the NATCMD library. This sample uses symbols that will be resolved at shipment time based upon shipment destination. These symbols all begin with &RMT.
// OBJMT='&C1ELMNT255',
// OBJMD='&C1ELMNT255',
// OBJMS='NAT&C1ELMNT255(1,4)',
// OBJWN='WITH,NEWLIBRARY,&RMTLNAME,%',
// OBJLT='LOAD &C1ELMNT255,LIB,*,OBJTYPE,N,&OBJWN',
// OBJLD='LOAD &C1ELMNT255,LIB,*,OBJTYPE,D,%',
// OBJLS='LOAD &C1ELMNT255,LIB,*,OBJTYPE,E,&OBJWN',
// OBJMEM=&OBJM&C1TY(3,1)
//*
//*******************************************************************
//* PACKAGE PROCESSING FOR SHIPMENT AND BACKOUT (NO DDMS)
//*******************************************************************
//IF1 IF (&C1PKGID NE ' ') THEN
//IF2 IF (&C1TY NE 'NTDDM') THEN
//*
//*********************************************************************
//* STORE UNLOADED NATURAL OBJECT INTO PDS
//*********************************************************************
//GENER1 EXEC PGM=IEBGENER,MAXRC=0
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=&&ELMMOVE,DISP=OLD
//SYSUT2 DD DISP=SHR,
// DSN=BST.MOTM.ESCM715.NATOBJ(&OBJMEM),
// MONITOR=COMPONENTS
//*
//*********************************************************************
//* PUT REMOTE NATLOAD JCL INTO NATCMD LIBRARY
//*********************************************************************
//GENER2 EXEC PGM=IEBGENER,MAXRC=0
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DATA,DLM='$$'
//*
//NATLOAD EXEC PGM=&RMTNATNUC
//STEPLIB DD DSN=&RMTNATLIB,DISP=SHR
// DD DSN=&RMTADALIB,DISP=SHR
//CMPRMIN DD *
&RMTPRM1
&RMTPRM3
&RMTPRM4
&RMTPRM5
//DDCARD DD *
&RMTDDCARD
//CMWKF01 DD DISP=SHR,
// DSN=PUBLIC.MORMI08.NATOBJ(&OBJMEM)
//CMPRINT DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDDRUCK DD DUMMY
//MPMDUMP DD DUMMY
//DDKARTE DD DUMMY
//CMSYNIN DD *
SYSPROF
SYSOBJH
&OBJL&C1TY(3,1)
WHERE,REPLACE,ALL,REPORT
.
FIN
$$
//SYSUT2 DD DISP=SHR,
// DSN=BST.MOTM.ESCM715.NATCMD(&OBJMEM),
// MONITOR=COMPONENTS
//*
//IF2 ENDIF
//IF1 ENDIF
Copyright © 2014 CA Technologies.
All rights reserved.
 
|
|