What causes a u914 abend in VISION:Results?

Document ID : KB000027077
Last Modified Date : 14/02/2018
Show Technical Document Details

VISION: Results 5.0 and earlier releases verified licensed use by validating a product code applied with supplied job, CUSTMJCL.

In some cases, customers encounter the following error after a new product code is applied:

JOB TERMINATED DUE TO CPU ID xxxxx  MISMATCH.

If the request was for a permanent product code, you can review the DEFAULT OPTIONS display from the listing of a job that ran prior to the application of the new product code. The prior product code and CPU serial number are displayed so you can tell if the CPU ID value in the error is the same as the prior successful runs.

ENVIRONMENT IS MVS PRODUCT CODE(kkkk,kkkk,kkkk,kkkk,kkkk,kkkk,k) 
 CPUID 2096 sssss

(If the prior product code has not yet timed out, there is sample JCL at the end of this article you can use to generate a DEFAULT OPTIONS display, as well)

If the product code was requested for a Disaster Recovery test, the product code should be generic and good for any CPU ID.

In this case, please verify that the loadlib being used for the test is the same one the CUSTMJCL job was run against.

If the loadlib is in the linklist, a F LLA, REFRESH may be required to force the system to obtain new pointers to the LINKLIST and pull in the new copy of the module DYLPCPS.

If the job still fails, please open a Support Issue.

Please be aware VISION:Results 6.0 uses LMP keys and has been available since January 2007.

VISION:Results 5.0 will be desupported in August 2008.

All previous releases are already desupported.

SAMPLE JOB TO GENERATE A DEFAULT OPTION DISPLAY

//DISPLAY  EXEC PGM=DYL280,REGION=0M 
   //STEPLIB DD DISP=SHR,DSN=your.vision.results.loadlib 
   //SYSIN DD * 
   FILE SYSIN CARDS 
    DATAIN   12 
    LIST DATAIN 
   FIN 
   TEST DISPLAY 
   /* 
   //SYS280R DD SYSOUT=* 
   //SYS004  DD UNIT=VIO,SPACE=(TRK,(10,5)) 
   //SYSPRINT DD SYSOUT=* 
   //SYSWRK  DD UNIT=SYSDA,SPACE=(TRK,(10,5)) 
 //