What can cause VISION:Report to terminate with a cc12 with no error message?

Products

• Vision:Report

Issue/Introduction

Debugging a problem is difficult when there is no error message to explain the cause of a non-zero return code. 

Normally the first place to look for clues to a non-zero return code is the information gleaned from error messages.
This SYSPRINT output didn't tell us much:

     JOBNAME=QUIKJOBT        VISION:REPORT   V16L1     USER CONTROL STATEMENTS    
     STEPNAME=STEP1                            ERROR DIAGNOSTICS APPLY TO PRECEDING CARD  
                                                                              
              *** FOR ASSISTANCE CALL CA TECHNICAL SUPPORT. 

There is no preceding card, or error diagnostic, just the condition code 12 at job termination.

In this case, the culprit is CA's Common Services licensing program, or actually, lack thereof.
VISION:Report 16.1 interfaces with the CA Licensing System using the CA TNG Framework for OS/390 Common Services CAIRIM and its CA-LMP (License Management Program) facility used to track licensed software.

The licensing software must be active at the time any related CA product begins execution, or the products will fail to function.
This Condition Code 12 termination is how VISION:Report 16.1 responds when it is not.

For more information regarding the CA TNG Framework for OS/390 Common Service CAIRIM and its CA-LMP facility, see the Unicenter TNG Framework for OS/390 Reference Guide and the Unicenter TNG Framework for OS/390 Installation and Maintenance Guide. 

Environment

Release: VSNREP00100-16.1-VISION:Report
Component: