How do I specify an offset from the current time, plus or minus days or time, in Date Simulator?

Products

• Date Simulator

Issue/Introduction

How can I specify an offset from the current time, plus or minus days/hours/minutes/seconds?

 

 

Environment

Release: TCDASM00200-2-Date Simulator
Component:

Resolution

You can define "C" + an offset in the Date Simulator ISPF "SET" panel, as follows:

------------TransCentury Date Simulator V2.0 - Set Job ------------------------

COMMAND ===>                                                                                                                                               

 Specify the "job" for which time is to be altered:                           

   <jobtype>.... job         JOB(batch), STC(started task), TSO, IMS or DB2   

   <jobname>.... testjob1    jobname or TSOid: 1-8 chars; may end with '*'    

 For batch jobs ONLY you may also restrict by:                                

   <userid>.....             and/or     <jobclass>...                         

 For all jobs specify the simulated start/current time and date               

   <Start or Current?>.. C             <+/- offset>    * Valid for Current    

   <time>............... 03 32 02    |   +  01 02 03   * Increment HH MM SS   

   <date>............... 10 11 2016  |   +  00004      * Increment days       

                                                                              

   <fixed date?>.............. N      <save to file?>........ N               

   <alter TIME macros?>....... Y      <IMS control region?>.. N               

   <CICS transaction-level?>.. N      <IMS MPR?>............. N               

   <DB/2 distributed?>........ N      <IMS BMP?>............. N               

 Optionally, specify where Store Clock instructions are to be altered:        

 <program  offset > <program  offset > <program  offset > <program  offset >                                                                                  

Please see additional information below.

The "CURRENT" parameter can be used within the SET command as per WARMPARM job step as follows:

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

//STEPLIB  DD DISP=SHR,DSN=DATESIM.APFLOAD  

//SYSOUT   DD SYSOUT=*                            

//SYSIN    DD *                                   

SET JOB TESTJOB1 CURRENT DATE +1 TIME +06:00 -    

STCK(CEEPLPKA,01F0E24)                            

Note: This is just a sample, you have to customize the DSN, likely the TESTJOB1 job name, and especially the CEEPLPKA offset which could be different on your system.  The STCK(CEEPLPKA...) parm is required when time warping LE programs.

Additional Information:

With the cursor in a field you can get additional information with the PF1 HELP key. For instance:

---------------------------- Time-Date Mode Help ------------------------------                                                                            

The simulated time and date you specify may be applied in one of two ways.    

If you specify "Start", then each time the job is started, its simulated      

system clock is reset to the specified time and date.  For instance, if       

you SET a batch job and run it three times, each time it will appear to have  

started at the time and date you have specified.                                                                                                         

   Note: A TSO session is considered to be started at the time the user logs  

1. IMS users are considered to be started at the time the IMS Control    

 Region is started.  DB/2 DDF users are considered to be started when the   

   DDF region is started.  For these types of jobs, you may find "Current"    

   time and date to be more useful.                                           

                                                                              

If you specify "Current", this causes the simulated system clock for the      

job to be set to the specified time and date at the moment you do the SET.    

The clock continues to run and is NOT reset each time the job is run.  If you 

run the job 10 minutes after you issue the SET command, its simulated start   

time will be the time you specified plus 10 minutes.  If you run the job again

5 minutes later, its simulated start time will be the time you specified plus 

15 minutes.  Each time the Date Simulator displays this time and date, it will

show the current setting at that moment.   

                                  

 

----------------------- Time Date Help ------------------------------------ 

                                                                              

You may specify a simulated time in the standard 24-hour clock format of     

hour:minute:second in the range 00:00:00 to 23:59:59.                         

                                                                             

Using Current mode, you may specify an offset from the current time plus or  

minus hours, minutes and/or seconds.                                         

                                                                             

You may specify a simulated date in the month/day/year format in the range   

01/01/1900 to 12/31/2041.  This range is dictated by the limitations of      

the ESA/390 Time-of-day (TOD) clock upon which MVS current-date services are 

based.                                                                       

                                                                             

Using Current mode, you may specify an offset from the current date plus or  

minus 'nnnnn' number of days. The resulting date must fall within the range  

01/01/1900 to 12/31/2041 as explained in the previous paragraph.             

                                                                              

NOTE: If any of the special indicators for CICS transaction-level, IMS or    

      DB/2 distributed are set to Y for this job, the time and date specified

      here are not actually used.  Rather, the times and dates specified for 

      specific CICS transactions, IMS users and DB/2 distributed users will  

      be used.