Do subsystems that spawn UBE jobs all use the same table cache?

[johndanter]

Hi folks,

If I have a subsystem that spawns and launches UBEs, what cache does the spawned UBE use? (P98613 table cache I mean)

It's own UBE table cache made up at runtime?

Or the table cache of the subsystem when it was first launched?

Does anyone know the answer for both synchronous and asynchronous UBE calls

Thanks

John

 

[gopal122]

Running UBE multiple times in subsystem creates only 1 pdf in printqueue . its by the design that if we run any ube multiple times, it will update the same pdf .

Thanks,
Gopal

 

[gopal122]

A Subsystem Job will hold its spec cache for all the UBE iterations until it detects that a package is being deployed . Any UBE with iterated runs will be cached considering its previous runs and will be updated accordingly in a single pdf output .

Thanks,
Gopal

 

[jdelisths]

To my knowledge (don't hold me to this): For synchronous spawned UBEs, it will use the table cache of the subsystem when it was first launched. For async spawned UBEs, it will reload the cache.

 

[johndanter]

To my knowledge (don't hold me to this): For synchronous spawned UBEs, it will use the table cache of the subsystem when it was first launched. For async spawned UBEs, it will reload the cache.

I won't but it's what I believe too. Just want to make sure