Question on SPILL using LOGRCV=NEVER

Document ID : KB000111446
Last Modified Date : 05/09/2018
Show Technical Document Details
Introduction:
Customer did a CA Datacom/AD 12.0 to 15.0 upgrade for CA11. 
Question:
We have a back-up job that runs nightly against the CXX dataset. It references DBID=601, which is no longer being used with r15.
The only SPILL JCL example I could find is AX15LXXS and seems totally unrelated.
I cannot find anything about the CXX spill in the manual. Is this something we still need to do?
I did run AD15BK02 for the CXX, but that doesn't seem to be something to run daily..
Environment:
z/os - CA Datacom/AD 15.0 for CA11
Answer:
Site using MUF startup parameter LOGRCV=NEVER does not need to use SPILL.

Any attempt to SPILL will generate informational DB13082I message:
"MULTI-USER HAS LOGRCV YES/NEVER, SPILL DONE IN MULTI-USER"
Job will finish with success even  without  a valid RXX DD STATEMENT.

Again, SPILL job mentioned in CAAXSAMP(AX15LXXS) is not needed if LOGRCV=NEVER.
Additional Information:
There is nothing or job or task called "CXX SPILL".  Such task is called "LXX SPILL".

Also executing a SPILL when MUF  startup parameter LOGRCV=NEVER will generate following informational message and produce rc=0:

DB13082I
MULTI-USER HAS LOGRCV YES/NEVER, SPILL DONE IN MULTI-USER
-Reason:
A spill was requested in a system with the LOGRCV MUF startup option with YES or NEVER. If spillable data exists, it is spilled in the Multi-User Facility.
No Recovery File (RXX) is generated in this case.

-Action:
None. This message is for information only.