Skip to main content
Status: Accepted

Theme
In this case, we would like to exclude the Lib type from ERO processing that we have set up for the package audit report.

Why
That would be interesting for us because we often have completed the area editing and testing but still have to redraw the package audit report and then insert it again through areas that have already been approved.

What has already been done
We have activated the new lib type for saving the audit report in the package as component as named LSA.
We have already adjusted the following things:
CMN$$AUD.SKL: Suppress the HTML format in the audit report.
CMN$$SEX).SKL: Routine to generate the SYSEXEC DD concatenation REXX EXEC Libs
CMNEX031.SRC: Do not audit LSA for package audit.
CMNEX032.SRC: Defined as Compressed Listing for Baseline Browse LS*.
CMNEX035.SRC: No staging or checkout for LS*. LS* is displayed as a compressed listing.
CMNEX037.SRC: Execute user defined edit macro?
CMNEX201.SRC: Do not audit LSA for area audit.
CMN30PDS.SKL: Make NULLFILE possible for Baseline -1 DSs. These baseline -1 DSs are not needed for LSA.

Idea
We would like to remove LSA from ERO processing. If we don't define LSA in the release, there will be problems in the test area because the component is not found. You can prevent check-in within the CMNEX220.SRC, but then the test release/area will still cause problems.

Can you enable a lib type to be excluded from ERO processing?

PS: We cannot currently pursue the HLLX approach.


#ERO
#ZMF
Status: Accepted

Theme
In this case, we would like to exclude the Lib type from ERO processing that we have set up for the package audit report.

Why
That would be interesting for us because we often have completed the area editing and testing but still have to redraw the package audit report and then insert it again through areas that have already been approved.

What has already been done
We have activated the new lib type for saving the audit report in the package as component as named LSA.
We have already adjusted the following things:
CMN$$AUD.SKL: Suppress the HTML format in the audit report.
CMN$$SEX).SKL: Routine to generate the SYSEXEC DD concatenation REXX EXEC Libs
CMNEX031.SRC: Do not audit LSA for package audit.
CMNEX032.SRC: Defined as Compressed Listing for Baseline Browse LS*.
CMNEX035.SRC: No staging or checkout for LS*. LS* is displayed as a compressed listing.
CMNEX037.SRC: Execute user defined edit macro?
CMNEX201.SRC: Do not audit LSA for area audit.
CMN30PDS.SKL: Make NULLFILE possible for Baseline -1 DSs. These baseline -1 DSs are not needed for LSA.

Idea
We would like to remove LSA from ERO processing. If we don't define LSA in the release, there will be problems in the test area because the component is not found. You can prevent check-in within the CMNEX220.SRC, but then the test release/area will still cause problems.

Can you enable a lib type to be excluded from ERO processing?

PS: We cannot currently pursue the HLLX approach.


#ERO
#ZMF

Hi Johan,

We can't exclude library types in ERO feeder packages from release processing as it generates too many possibilities for problems with the release, there will be many unintended consequences. What may be possible, to help with your specific issue, is to provide an option to allow compressed listing library types to be checked into a release without affecting the area/release audit RC.  In that way your latest package audit reports can be checked in after approval with no impact on the approvals already gathered. Is this something that will help ?

To be specific, the change (if indicated as required in release admin) would have checkin use the rlsmtype.list.bun service to lookup the <likeType> value for the library type and, if it is X, will not reset the audit the RC.

Cheers

All the best - Steve

Terms & ConditionsAccessibility statement