CA Date Simulator - Save Settings to a file.

Document ID : KB000033159
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

 

This document describes how to save settings to a WARPFILE for later reuse.

This new feature has been released via TF1D309 in August 2013.

(See DateSimulator/2.0/Patches/)

 

SET entries can be written to a WARPFILE now.

 

From CA Date Simulator ISPF SET Panel HELP - pressing HELP key (PF1) when the cursor is in the field:

"<save to file?>........ N"

you will see the following details:

 

------------------- Special Indicators Help ----------------------------------

                                                                              

 <fixed date?>  Indicates whether the simulated date is fixed and, therefore, 

   does not rollover to the next date when the simulated time reaches midnight.

                                                                              

 <save to file?>  Indicates whether the SETTING will be saved in the WARPFILE.

   When the indicator equals 'Y' - the setting is saved. When the indicator   

   equals 'N' - the setting is not saved and any previously saved setting is  

   deleted from the file.                                                     

                                                                               

 save to file unavailable  A WAPRFILE has not been allocated to this Date     

   Simulator session via the WARPFILE DD; settings cannot be saved to the file.

                                                                              

 <alter TIME macros?>  Indicates whether TIME macros issued by the job are to 

   have their results replaced with simulated dates.  Normally set to N only  

   for DB/2.                                                                  

                                                                               

 <CICS transaction-level?>  Indicates that the job is a CICS region on which  

   transaction-level date simulation has been installed. When the indicator   

   equals 'A' - all transactions will be adjusted.  When the indicator        

   equals 'Y' - DTSM transaction is used in CICS to pick transactions.        

                                                                               

                              RIGHT = Next HELP Panel                          

 

 

Instructions:  

 

 

1.    Allocatea WARPFILE - JCL sample:

 

//jobcard                                                            

//*------------------------------------------------------------------*

//*                                                                  *

//*    DEFINE CA-DATE SIMULATOR WARPFILE.                            *

//*                                                                  *

//*    THIS JCL STREAM WILL ALLOCATE A WARPFILE.                     *

//*                                                                  *

//*    NOTE: PLEASE MAKE THE FOLLOWING CHANGES:                      *

//*                                                                  *

//*    4) CHANGE $AVG$ TO THE AVERAGE RECORD SIZE.                   *

//*                                                                  *

//*    5) CHANGE $LOADLIB$ TO YOUR CA DATE SIMULATOR LOAD LIBRARY    *

//*                                                                  *

//*    6) DO NOT CHANGE THE CISIZE PARAMETER.                        *

//*                                                                  *

//*    8) REVIEW ANY OTHER PROC VARIABLES AND CHANGE AS              *

//*       NECESSARY                                                  *

//*                                                                  *

//*------------------------------------------------------------------*

//DEFSYM   EXEC PGM=IDCAMS,REGION=1024K                              

//SYSPRINT DD SYSOUT=*                                               

//SYSIN    DD *                                                      

   DELETE YOUR.DATESIM2.WARPFILE CLUSTER PURGE                       

   SET MAXCC=0                                                       

   DEFINE CLUSTER (NAME(YOUR.DATESIM2.WARPFILE)               -                    

                   SHR(3 3)                                   -      

                   RECSZ(88 88)                               -         

                   FREESPACE(20 10)                           -      

                   KEYS(31 0)                                 -      

                   INDEXED)                                   -      

          DATA (                                              -      

             NAME(YOUR.DATESIM2.WARPFILE.DATA)                -                     

             RECORDS(500)                                     -         

             VOL(OSI010)                                      -        

             CONTROLINTERVALSIZE(2048))                       -      

          INDEX (                                             -      

             NAME(YOUR.DATESIM2.WARPFILE.INDEX)               -                    

             TRACKS(10 10)                                    -      

             VOL(OSI010)                                      -        

             CONTROLINTERVALSIZE(512))                               

/*                                                                    

 

 

2.    Initialize the WARPFILE - JCL sample:

 

//INIT     EXEC PGM=WARPINIF                           

//STEPLIB  DD DISP=SHR,DSN=YOUR.DATESIM2.LOAD          

//WARPFILE DD DISP=SHR,DSN=YOUR.DATESIM2.WARPFILE      

//SYSOUT   DD SYSOUT=*                                 

...                                                      

 

3.    Adding WARPFILE DD statements to TIMEWARP/WARMAIN JCL:

//STEP1    EXEC PGM=WARPMAIN,PARM='STCKSVC=228'        

//STEPLIB  DD DISP=SHR,DSN=YOUR.DATESIM2.APFLOAD       

//SYSLIB   DD DISP=SHR,DSN=YOUR.DATESIM2.APFLOAD       

//WARPFILE DD DISP=SHR,DSN=YOUR.DATESIM2.WARPFILE      

 

 

In a batch job you can now add SAVE to the SET command in order to add the statement to the WARPFILE. E.g.:

//STEP1    EXEC PGM=WARPPARM,REGION=2M                           

//STEPLIB  DD DISP=SHR,DSN=YOUR.DATESIM2.APFLOAD                 

//SYSOUT   DD SYSOUT=*                                           

//SYSIN    DD *                                                   

SET JOB TIMET01C CURRENT TIME +06:00 STCK(CEEEV003,043CA58) SAVE 

...

 

If you run the SET for this JOB again, but without SAVE, the entry would be removed from the WARPFILE. This is working as designed.