"Tom Marchant" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Fri, 18 May 2007 09:51:23 +0200, Vernooy, C.P. - SPLXM > <[EMAIL PROTECTED]> wrote: > > > > > > >"Robert Bardos" <[EMAIL PROTECTED]> wrote in message > >news:<[EMAIL PROTECTED]>... > >> > >> Naive idea: why not provide system symbols for all of these > >> (submission time, conversion time, execution time)? SYSSTIME, > >> SYSCTIME, SYSETIME? > >> > >> Robert > >> > > > >Of which system? Jobs can travel through serveral systems in an NJE > >network, submitted on system1, converted on system2 executed on system3, > >each with their own timesettings. > > Well, let's see.... If I submit a job on system1 and ask for submission time, I > think I would want system1's time. If I submit it to run on system3 and ask > for executuion time, I think I want system3's time. Of course, if e.g. system3 > is a sysplex with images running in different time zones, I'd probably want GMT > time. > > > Dataset1 gets timestamp 10:00, the > >*next* dataset2 can get timestamp 09:10 if created 10 minutes after > >dataset1. Quite confusing. > > I can't see how that would happen unless the two time stamps were based > upon a different kind of time. Or perhaps if the job terminated and was > restarted on a different member in the 'plex that ran in a different time zone > and I was asking for local time. >
It will also work without restart: job1 runs on system1 with time1, job2 runs 10 minutes later on system2 with time=time1-1hr. I must admit, if you know the mechanisme, you know its shortcomings and that could be manageable. I think the problem is at a different level: until now, symbolics are system-wide: with this addition you get symbolics per job. This means that each job must create room to store all these variables. Where do you store them, which variables do you store, how do you keep flexibility in this set of variables, will the user demand a varying set of user variables to be stored (yes, he will), etc. etc.? Kees. ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
