LMINIT FOR '(IDB2VARS)' FAILED WITH RC = 8

Products

• Bind Analyzer for DB2 for z/OS
• SQL-Ease for DB2 for z/OS
• SYSVIEW Performance Management Option for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

Attempting to do the R18 Insight install/post installation and during the task select section for IDB2 CA SYSVIEW for DB2: DB22 specific install tasks (DB2S0550) User received  the following message after attempting to create the 0550 job:

Please wait while the JCL is being generated for the DB2 Tasks.   Note that you may be prompted for additional information needed  to generate the tasks.                                      Current Task...: CA SYSVIEW FOR DB2: DB2 SPECIFIC INSTALL TASKS   Output Data Set: 'ACSNS.CADMSDB2.R18.MSMD.CDBASAMP'        Output Member..: DB2S0550                                            

THE INITIAL PART OF THE CA SYSVIEW FOR DB2 POST INSTALL    

"EXECUTE PRODUCT SPECIFIC CUSTOMIZATION TASKS" FROM THE DB2

TOOLS INSTALLATION MAIN MENU HAS NOT BEEN COMPLETED        

SUCCESSFULLY. ONE OR MORE OF THE FOLLOWING INSTALL DATASETS

ARE MISSING OR ARE NOT AT THE CORRECT LEVEL:               

INST LEVEL: '170'                                          

 CUR LEVEL: '180'                                          

    SOURCE: 'SYS6.INSIGHT.DB2S180.SOURCE' OK               

  SECURITY: 'SYS6.INSIGHT.DB2S180.SECURITY' OK             

    TGTREQ: 'ACSNS.CADMSDB2.R18.MSMD.CDBATREQ' OK          

YOU MUST PERFORM THE PRODUCT SPECIFIC CUSTOMIZATION TASK   

FOR CA SYSVIEW FOR DB2 BEFORE YOU CAN PERFORM THE "EXECUTE 

DB2 TASKS" FOR CA SYSVIEW FOR DB2. REFER TO THE            

INSTALLATION GUIDE FOR MORE INFORMATION. 

 

Environment

Release:
Component: CIDB

Resolution

The incorrect DSNAMExx was the cause for this error. After going back  to square 1 and started the post installation process, user found that there were multiple R17 parmlib(s) set up with various members. She was  able to track the 'correct' DSNAMEE1 and successfully built the jobs for the upgrade. Pointing to the correct DSNAMExx member resolved the problem.