Package Ship Facility › How to Enable Post-Ship Script Execution › Create a Destination Configuration File

Create a Destination Configuration File

If you plan to use symbols that will resolve to values based on the destination in the script files created by your processors, you need to create a Destination Configuration file. The Destination Configuration member contains statements that will be read and parsed at package shipment execution time to create symbols unique to a destination that can be used in script data set members to resolve symbols for the target destination. These symbols must have been created in the script dataset members by your processors in order for the substitution to take place correctly.

Follow these steps:

1. Create a Destination Configuration file to define symbol names and values unique to each package ship destination.

   Use the following syntax to define the symbol names and values for each destination:

   >>--  DESTination 'destid'  ---------------------------> 
     +<----<----<----<----<----<----<----<----<----<---+
   --+-->  SYMbol 'symbol-name' VALue 'symbol-value' ---->
   --->  .  ---------------------------------------------><
   

   This statement can be repeated for each destination and the SYMBOL and VALUE combination can be defined as many times as necessary within each statement. If SYMBOL is coded (there must be at least one) then VALUE must also be coded. To code a null value for a symbol, use two consecutive single quotes after the VALUE keyword.

2. Add the Destination Configuration member to your PARMLIB.
3. Include the symbols in your script data set members as appropriate to represent information that will vary by destination.

   Important: Symbol substitution can cause syntax errors by causing line overflows.

   Consider the maximum length of your symbols, use symbol substringing to generate appropriate syntax, or both. For more information on Symbol substring syntax, see the Extended Processors Guide. Alternatively, if for example you need to substitute long symbols such as path or file names, consider using a variable blocked (RECFM=VB) script file.

Note: The content of the Destination Configuration member can be viewed from the Display Options menu and any syntax errors can be reviewed there. The name of the Destination Configuration member is displayed in the Parameter Library Information section of the Site Information from C1DEFLTS panel. On the DSN Mapping Selection List, SCRIPT appears in the Status column when a script file is identified by a mapping rule. Script Execution status can be returned and displayed in the 'Shipment Status' view by scrolling right.

Example for Create a Destination Configuration File

Example: Destination Configuration File for Post-Ship Script

This example of a Destination Configuration file defines different values for the symbol CICSREGN depending on the target destination.

DESTINATION CA31XCM                                                                                          
    SYMBOL 'CICSREGN' VALUE 'CICS31DN'
    SYMBOL 'DB2SYS'   VALUE 'DBS31DN'  .  
DESTINATION CA11LOC                                                                                          
    SYMBOL 'CICSREGN' VALUE 'CICS11PR'
    SYMBOL 'DB2SYS'   VALUE 'DB2S11DN'  .                                                      

Note: This example creates a CICSREGN symbol for the CICS new copy script created in the example shown in Update Processors for Post-Ship Script.