How to know or compute from the curent time in a different TZ

[Eric Delawoevre]

I've got multiple tasks

some are scheduled on MU with a TZ

So, that means that the difference with the local timedate is automated (with day light saving for some)

But into an uproc, the whole information is "local"

Also, all the command uxtim and uxdat are based on local

My thinking is : How to know the "time" ? How to know the difference to add/removed fromù the local time ?

The uxlst MU FULL don't display the computed difference.

Thank you for your help

Eric

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Laurent LAO]

You can use uxshw MU to display the timezone and the difference time

-------------------------------------------

[Eric Delawoevre]

Hi Laurent,

Thank you. So, only this little value in parenthesis? No other access ?

 ITEMS | mu           : M_***_***_U
       | label        : USA Central time north america CST_NA
       | dev
       | prod
       | tnode        : ********
       | tz           : America/New_York (-06:00)
       | user         : *****

------------------------------
[DU Master][DU strategy Expert]
[Synapps]
#dollaruniverse
------------------------------

[Angus Reid]

If you are trying to schedule things over various time periods then MU OFFSET can be used, so a process in timezone A will sync with a process in timezone B using inbuilt DUAS functions. 

-------------------------------------------

[Eric Delawoevre]

mmm, such as a big watchdog machine.

But many of chains are disabled (decomm) or simulated (delivery). So this mecanism is not usefull for me (and very fragile regardy automates and situations)

Was thinking about this bellow user-parameter, but again, it localy target on the User, not the DUAS

------------------------------
[DU Master][DU strategy Expert]
[Synapps]
#dollaruniverse
------------------------------

[Angus Reid]

What is being attempted? 

A PS expression can be used on remote or local servers which will calculate date/time and allow for offsets and this can be stored in a file with something like server ----- date -- time (current including local daylight)  --- timezone

Then at uproc runtime the file can be accessed and the info used in launches. As long as a launch window is longer than a day any FLA will work and depenencies will take of the rest.

Not sure if that is what you are after, will take care of world timezones relative to a local server if you are travelling.

-------------------------------------------

[Eric Delawoevre]

I understand your meaning.

The processing in on trailers. Many of them compute a restart of itself into a start AND window

everything is working perfectly (I proposed it into the $U library for broadcom, it the solution of starting looping within a session with control and same $U control)

But the problematic appears when we talk MU with TZ

Into the Uproc (linux or Windows), we absolutly don't have any information of the site time (but the execution is local for SAP)

Example

Waiting a file from 00h00 to 10h00 US time for processing IDOCS into SAP

That a real launch at 6am to 4pm with rotation of the session

On the trailer, the time is 6am, not 00h00 (caused but the tiny information into the uxshw MU (+06h00)

So, sure, the processing is to get the +06:00 and use uxtim or uxdat to compute a date time for the session rotation & control.

There is also the Laundate column into the console Task list (hidden per default) that reflect the différence. But this value is the start datetime, not the current value into the Uproc being executing

------------------------------
[DU Master][DU strategy Expert]
[Synapps]
#dollaruniverse
------------------------------