IBM Mainframe Forum

Hi...

We use TWS Special Resource Intervals to control batch job submission, for example when planning for a scheduled outage we can pre-set SR unavailable intervals.

For some reason this function has recently stopped working - the SR exists, and Intervals are set up correctly but are being ignored. ie. batch runs! Turning the SR off/on via the CLI or batch works, but the ability to (pre)set the date/time interval is not.

I've checked the SR Max Usage Limit (0) and Used For (B), and ensured all Workstations are included (*). What am I missing???

Any help would be appreciated.
Thanks,
Jenny.

Hello Jenny and welcome to the forum,

For some reason this function has recently stopped working

Someone has changed something. . . ?

Is there a from/to date specified or is the end date infinity? Has there been a recent upgrade?

I don't have access to a system that uses tws, so i can't refer to "ours".

Hi Dick,

No, there is no end date parameter in OPC Special Resources and no, there haven't been any recent upgrades.

Yep, something has changed, but I can't find what it is... Hoping someone "out there" can provide some suggestions!

Thanks,
Jenny.

Hi Jenny,

Not what i'd call a good solution, but what happens if you define a new special resource with the same intervals defined and schedule something against it. What if the intervals were different for a test?

This might help isolate if the service has a problem or something has gone amiss with that one SR. . .

One of our brighter sparks figured it out.

"It's to do with the special resource in the current plan having the AVAILABLE field set with a value of Y (instead of blank so that it uses the default values). "

Problem fixed!

Good to hear it is working - thanks for letting us know

d