Closed FALLAI-Denis closed 9 months ago
@FALLAI-Denis
Is this null pointer caused by a customisation of yours to skip creating the applicationOutputsCollection
?
In ImpactUtilities.verifyCollections(), the collection will always be created.
@FALLAI-Denis
I was able to reproduce your problem. It is not about the collection, it is about the case, when the logicalFile does not exist.
I believe the new DBB toolkit is too strict here .
@dennis-behm , @FALLAI-Denis
Hi,
we already had the same problem and opened a case against DBB 2.0.
Meanwhile there is an APAR for it: PH53060.
@friedhelmmuench thanks - now I have the "link" between our conversation a few days ago.
Closing the issue. Resolved as part of the DBB toolkit ptfs
Hi,
In the
updateCollection
function of theImpactUtilities.groovy
script, actiondeletedFiles.each
, an exception is raised on the linemetadataStore.getCollection(props.applicationOutputsCollectionName).deleteLogicalFile(logicalFile)
A priori the "Outputs" Collection does not exist and the
getCollection
function returns the value null, so we cannot chain thedeleteLogicalFile
function in a chained way.Thanks.