ImpactUtilities.groovy - null pointer exception in updateCollection on "Outputs" collection

[FALLAI-Denis]

Hi,

In the updateCollection function of the ImpactUtilities.groovy script, action deletedFiles.each, an exception is raised on the line

metadataStore.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 the deleteLogicalFile function in a chained way.

Thanks.

[dennis-behm]

@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.

[dennis-behm]

@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 .

[friedhelmmuench]

@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.

[dennis-behm]

@friedhelmmuench thanks - now I have the "link" between our conversation a few days ago.

[dennis-behm]

Closing the issue. Resolved as part of the DBB toolkit ptfs