To enable the Post-Ship Script feature, you must update your processors to add the steps that create your script output data sets.
Follow these steps:
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 CICSNEWC for CICS Phasin requests or DB2BIND for DB2 bind requests. Any destination specific symbols that you want to be substituted at shipment must be present in the script file created by the processor.
Example: Create CICS New Copy Script for Post-Ship Script Execution
The following code sample will create CICS phase-in requests when the processor is executed in a package. The &CICSREGN symbol in this example will be substituted at ship time.
//*************************************************************** //* CREATE CICS NEW COPY SCRIPT //*************************************************************** //PKGCHK IF &C1PKGID NE "" THEN * ONLY IF PACKAGE EXEC //SCRIPCP EXEC PGM=IEBGENER,MAXRC=0 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT2 DD DISP=SHR,MONITOR=&MONITOR,FOOTPRNT=CREATE, // DSN=&DSPREFIX.CICSNEWC(&C1ELEMENT) //SYSUT1 DD DATA,DLM=## /*VS,'F &CICSREGN,CEMT SET PRO(&C1ELEMENT),PHASEIN' ## //PKGCHKX ENDIF
|
Copyright © 2014 CA.
All rights reserved.
|
|