I have a problem using "user defined variables".

I have two jobs, and I need to ensure that the same timestamp is used for the two jobs, so I wanted to use a variable to set the timestamp.
The jobs are as follows:

Job A sets the string variable DummyVar to the value: {DATEFORMAT(dd-MM-yyyy HH:mm)}
<8-10 minutes later>
Job B uses the DummyVar to do something

The problem is that the DummyVar variable is not considered a constant, but the value of the variable changes as time goes by.

Is this a bug? And is there a way to circumvent this issue? I really want to use the date/timestamp as a constant.

best regards,

René Truelsen
An eager user of VisualCron

A Variable is always dynamic as it is. I consider this a feature request. By the way, how did it go with the LIST problem on the MVS server?

---

Ok. I would always consider a global variable as a constant by definition.
Anyways. I will put it in feature request.

The LIST change fixed the last MVS problems we had. So it's all working now. :)

Btw, I am very satisfied with all the filecopy options in VC5 (e.g. based on modified date and file content), it has really simplified some of our procedures.

Hi,

Not sure if this would work for you, but could you use the "Last execution time" variable from the job which will be static until it runs next time ?


Graham