URGENT - Add "NESTING DETAIL" and "NUMBER OF NESTINGS" parameters to RestAPI used by WAPL jobs in order to mitigate slow response times related to networking. this IDEA has been suggested by IBM support

UNIPOL needs to use DWC REST API queries in order to monitor his TWS scheduling infrastructure. Specifically, he wants to check the status of a jobstream in the current plan, and all the jobs it contains. In case a job is not COMPLETED, we launch a non_completed_predecessors query (getJobInstanceNonCompletedPredecessors) to identify where the chain is stuck. But in some cases, the query returns a very large number of non completed jobs (thousands), and the response time becomes very long. 

This kind of issue has already been addressed for calls coming from ISPF panels with the suggested implementation of the two parameters: "NESTING DETAIL" and "NUMBER OF NESTINGS".

This IDEA has been suggested by zWS L3 support in CASE TS019192236.

This is an extract of their suggestion out of the CASE documetation:

******Extract from CASE TS019192236 *******

this is the follow-up analysis by zWS L3 team

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

Hello, we know that ALL DEPS command is potentially very resource intensive from every interface it is run from.

For this reason a couple of Apars were done in the past in order to mitigate its use, by adding a couple of parameters when the request comes from ISPF panels. The parameters are "NESTING DETAIL" and "NUMBER OF NESTINGS".

How much time a request takes to be exploited depends also from the complexity of the network defined in customer environment. Bigger is the network more time it is needed to navigate through it, going through each dependency level.

Regarding the calls done from RestApi we have to consider that they flow through the network if the DWC and zConn doesn't reside on z/OS, and then we have to consider the network time response too and the PIF request behind them.

We cannot make comparison for the response time through ISPF panels and DWC.

Also WAPL job that exploit the same kind of requests would suffer of the same performance issue

for an ALL DEPS request.

What we can suggest is to open an IDEA so to add the parameters "NESTING DETAIL" and "NUMBER OF 

NESTINGS" in the RestApi in order to limit the processing of the call.