How can I overcome the "QI028E File SYS1 could not be edited" message that I'm receiving when trying to create a datastore in batch for Detector and Subsystem Analyzer?
search cancel

How can I overcome the "QI028E File SYS1 could not be edited" message that I'm receiving when trying to create a datastore in batch for Detector and Subsystem Analyzer?

book

Article ID: 11078

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS 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 Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS

Issue/Introduction

When creating a datastore in a batch for CA Detector and CA Subsystem Analyzer, the job finishes with the following error message:

QI028E File SYS1 could not be edited.

Using the CA Detector online panels the datastore was created without problem.



How can I overcome the "QI028E File SYS1 could not be edited" message that I'm receiving when trying to create a datastore in batch for Detector and Subsystem Analyzer using the "Generate JCL to create the datastore as specified" option on the "Create Datastore Display"?

Environment

z/OS 1.11 and above.

Resolution

The QI028E error is usually due to the ISPF temporary datasets being pre-allocated to the TSO/ISPF logon procedure with UNIT=VIO which causes SVC99 to return a blank for the unit and the ISPF editor therefore assumes the dataset is cataloged. When the dataset cannot be found, this error is issued. In order to correct this problem change the UNIT parameter from VIO to SYSDA or whatever UNIT is appropriate for your site.

Another way to overcome this problem is to bypass the logon proc & run the PDTDSALC job in your <High.Level>.CDBASRC library to create your Datastore.