JSON datasets are not created
search cancel

JSON datasets are not created

book

Article ID: 235056

calendar_today

Updated On:

Products

Mainframe Resource Intelligence

Issue/Introduction

Under CA MAINFRAME RESOURCE INTELLIGENCE 2.5.00

Allocating and initializing JSON data set(s) return code = 4 and JSON datasets are not created:

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB1E.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB1L.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB1T.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB1U.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2A.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2B.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2D.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2F.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2H.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2I.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2M.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2N.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2O.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2W.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2X.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2Y.JSON

   Processing JSON data set...: DSN = SYSZOS.CAMRI.MRI.MTLBPLEX.H120.DB2Z.JSON

   Done. 0 new data set(s) allocated.

Environment

MAINFRAME RESOURCE INTELLIGENCE 2.5.00 for the base assessment

Resolution

MRI Toolkit Version 2.5.02 of the toolkit has been released, which should fix this issue.

While running MRI for Db2 for z/OS Toolkit, please specify a valid Storage class for the STORPARM STORCLAS= parameter to avoid using non-SMS managed datasets for your report. 

Usage of non-SMS managed datasets would require allocation of all JSON datasets manually prior to the MRIDBSET job submission.