Download procedure.

1. Download following file to your desktop.
   • Click to download LDMF V1.3 Base Zaps
     MS-DOS .EXE format


2. Extract the data from the downloaded file on your desktop.



3. Should receive following file.
   Verify the filesize.
   • ZAP_BASE_Data
     Must have a filesize of 45,408 bytes.


4. Transfer to MVS
• If any of the receiving data sets are NOT preallocated, you will have to supply a quote site command to specify the data set attributes.
  
  To view an example of a basic Command Prompt FTP session, click
  .
   
• Transfer file ZAP_BASE_Data to a MVS sequential data set.
  This is an EBCDIC file, MUST BE transferred to MVS without any translation (i.e.: BINARY).
  
  Required Receiving Data Set Attributes.
  LRECL=88   <----- Note Size
  RECFM=FB
  BLKSIZE=    Any valid block size. DSORG=PS  (Sequential)
  
  Each record of data contains an 8 byte checksum. This checksum is added to each record as extra protection to ensure the correct data was received. These 8 bytes will be removed prior to actually unloading the data into the MVS data set.



5. Check the transferred data.
   You should be able to view all the data with ISPF and have data that is readable.



6. Create the MVS PDS.
   
   A sample TSOBATCH is located in your production LDMSLIB library - 'hlq.LDMvrr.LDMSLIB(TSOBATCH)'
   
   The rexx script required to unload the data is located in your production LDMFEXEC library - 'hlq.LDMvrr.LDMELIB(LDMFREXX)'
   
   The input data set should reflect where ZAP_BASE_Data was transferred.
   
   Choose one of the following procedures to process the data on MVS.
   
   
   1. Run the script via TSO BATCH (recommended procedure). Allows you to get the JES SYSOUT (if needed for problem determination).
      To view an example, click
      
      
      
   2. From the TSO command line, you can enter the command to execute the script.  Once invoked there will be no interaction with the script. With some of the larger data sets you may notice periods of time where nothing is presented to the TSO console while the checksum is processed.
      To view an example, click
      
      
      
   Following data sets will be created in this step (hlq will be your PROFILE PREFIX).
   More information: TSO/E USERS GUIDE, SC28-1880
   
   hlq.LDMvrr.BASE.ZAPS
   
   
7. Apply the ZAPS.
   The created data set has members in both SMP/E and SUPERZAP format.
   
   • Member names with a "S" suffix are the SMP/E zaps and are input data (SMPPTFIN) to SMP/E's RECEIVE process.
      
   • Member names with a "N" suffix are the NON-SMP/E zaps and are input data (SYSIN) to AMASPZAP program.   Note.   Check the comments to verify the order of applying the zaps.