Markus Haselbach wrote: >in our installation we do application testing with special dates like end of >month, end of year or leap day by IPling all Lpars in a test sysplex with a >date/time offset which can be as big as 100 days or more. Does someone run >test sysplexes also this way with future dates?
You have gotten good replies, but all of them are leaving some questions. What are you trying to accomplish? Could you be kind to elaborate on that? For example: 1. In a REXX or any other language program, you use by default the system date, but you can feed it a date as argument. 2. For automation products, you can feed a 'fake date' or 'scheduling date' or 'run date' to it. 3. If you want to test out macros/programs/things with time-of-day (TOD) (thinking of SET CLOCK and STCKCONV macro and TIME macro) - Then you need to IPL to get your clock correct. This will require 2 IPLs. One to go to other date and one to go back to current date/time. 4. If you need to test out your applications, it depends on how they are affected by date changes. Depending on the software you can feed it another date or let it default to current date/time. Just be careful - As I have taken precautions in RACF during the Y2K fun - your ids may or may not be available to logon to the system due to inactivity period and password validity period. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
