Re: Inactive time for jobs in DSPW condition

Leif,

>actually yes it is a security issue.

While I'm sure many things stored in the TDE are security issues, I'm not
convinced knowing the idle duration is any more of a security risk than many of
a job's attributes exposed by the regular work mgmt API's.

That's why I though perhaps I was just missing the boat on where I could find
the information.

>> Are there many other pieces of information
>> like this?
>
>yes, e.g. the CFINT flag :-)

But then I thought Fast400 (at least the original one?) was billed as not
needing anything but a user state program.  So were they somehow accessing and
changing another job's TDE from user state?  Or changing something else which
got reflected in the TDE?

Doug