CICS VSAM Transparency for z/OS, Version 1.2


DIM driver generation messages

Message ID Message Text Cause Solution
VIDGD001 An attempt was made to generate DIM ddddddd, but no CICS® VT mapping information exists for that DIM. No VSAM to DB2® mapping information exists in the CICS VT system tables for the requested DIM. Manually or automatically map the requested data. If manual mapping ensure that the DIM is marked as Ready for gen.
VIDGD002 SQL CODE cccc was encountered reading the CICS VT system table VID_DSN to generate DIM ddddddd. The CICS VT generate drivers utility was unable to access the CICS VT system table VID_DSN. Use the SQL code from the message and the accompanying formatted DB2 message in the job log to determine why the table is unavailable.
VIDGD003 No data set mapping information was found for the requested DIM dddddddd. Job terminated EID=eeee. No VSAM to DB2 mapping information was found in the CICS VT system table VID_DSNMAP for the requested DIM. Ensure that the requested DIM has been completely mapped using the CICS VT mapping facility.
VIDGD004 SQL CODE cccc received reading table VID_DSNMAP for DIM dddddddd, job terminated, EID=eeee. The CICS VT generate drivers utility was unable to access the CICS VT system table VID.SEGM. Use the SQL code from the message and the accompanying formatted DB2 message in the job log to determine why the table is unavailable.
VIDGD005 While attempting to generate DIM ddddddd, SQL CODE cccc was encountered reading system table VID_FIELD The generate drivers utility was unable to access system table VID_FIELD Use the SQL code from the message to determine why the table is unavailable.
VIDGD006 Error encountered while reading the field mapping information for the data set ssssssss, EID=eeee. Either the CICS VT system table VID_FIELD is unavailable or a field is not mapped to CICS VT. Use accompanying formatted DB2 message in the job log along with the diagnostic information following this to determine the error. If the SQL code is 100, verify that all of the fields for the data set have been mapped. If EID=E015, the first field in the CICS VT data set mapping is not defined as KEY.
VIDGD007 Error retrieving column information from SYSIBM.SYSCOLUMNS for creator.table, EID =eeee The generate drivers utility was unable to retrieve information for the SYSIBM.SYSCOLUMNS table. This is because the SYSIBM.SYSCOLUMNS table is unavailable or a column name specified in the mapping does not exist. For some errors, a formatted DB2 message will appear in the job log. Use that message along with the following diagnostic information to determine the cause of the problem. If the DB2 column name in the error message is the last column in the table, you have specified a DB2 column somewhere in the segment that does not exist in the DB2 table mapped to this segment. This can occur when you have loaded rows into VID_FIELD, rather than using the CICS VT ISPF mapping dialogs.
EID=001
A column specified in the mapping does not exist in the DB2 table for this DIM. Correct the column name and rerun the generate drivers utility.
EID= E017, E018, E021, E022, E024
Check the formatted DB2 message in the job log to determine the cause of the problem.
EID=E019, E020
Verify that the table in the message has been created.
VIDGD008 While attempting to generate DIM dimname, SQL CODE cccc was encountered checking the key field Use the SQL CODE to determine cause of error. If SQL CODE is -811, then there is more than one key field defined. Ensure that only one KEY field is defined and that CICS VT system tables are accessible.
VIDGD009 While attempting to generate DIM dimname, it was determined that the key field is greater than 255 bytes The VSAM KEY defined to CICS VT is greater than 255 bytes. Correct the mapping for the key.




Last updated: November 9, 2012 20:42:41