CICS VSAM Transparency for z/OS, Version 1.2


DDM driver generation messages

Message ID Message Text Cause Solution
VIDGP001 Invalid control statement, job terminated An error has been found in the control statements that are input to stage 1 processing. The formats for the control statements are:
DIM=dddddddd
Where dddddddd specifies the name of the DIM for which SQL drivers are to be built
or
DDM=pppppppp
Where pppppppp specifies the name of the DDM to be generated.
There must be at least one of each type of statement in the stage 1 input.
This only occurs if you have edited the control statements generated by CICS® VT. Correct the error and resubmit the batch generation job. If the control statements were generated by CICS VT, contact IBM® Technical Support.
VIDGP002 Maximum number of DIMs or DDMs specified for generation. Run terminated. The limit of 10000 DDMs or 1000 DIMs that can be generated at one time has been exceeded. Specify more restrictive DDM selection criteria when selecting DDMs to be generated.
VIDGP003 SQL CODE cccc received deleting VID_SRC rows for data set dddddddd. Run terminated. The generate drivers utility was unable to delete VID_SRC rows for the data set. Use the SQL code from the message to determine why the delete failed.
VIDGP004 Unknown error routine called The generate drivers utility was unable to process an error. Send the dump produced by the generate utility to IBM Technical Support.
VIDGP005 SQL CODE cccc received while adding source to VID_SRC for DDM pppppppp. Job terminated. Unable to add rows to the SQL drivers source table for the DDM named in the message. Use the formatted DB2® message in the job log to determine the reason for the error. If the SQL code is -803, delete all the rows from the VID_SRC table where the column VIDSRPSB is the name of the DDM in the message, then generate the DDM again.
VIDGP006 Data set ssssssss not found in DIM dddddddd. Job terminated. This is usually due to a mapping error. Correct the CICS VT mapping for the DIM and retry this DDM SQL driver generation.
VIDGP007 Field ffffffff in data set ssssssss in DIM dddddddd not found in table VID_FIELD. Job terminated, EID=eeee. A field defined in the DIM was not found in CICS VT system table VID_FIELD. Use the formatted DB2 message in the job log to diagnose the problem.
VIDGP008 Data set ssssssss in DIM dddddddd not found in VID_DSNMAP table. Job terminated, EID=eeee. No mapping information for the data set in the message could be found in CICS VT system table VID_DSNMAP. Ensure that the DIM has been completely mapped.
VIDGP010 Error accessing SYSIBM.SYSCOLUMNS while looking up key columns for table tttttttt, EID=eeee No key columns for the table named in the message could be found in SYSIBM.SYSCOLUMNS. Ensure that the DB2 table specified for the data set primary table in the CICS VT mapping is correct and that the table has a primary index defined.
VIDGP012 An error has occurred while reading SYSIBM. SYSCOLUMNS when building the host variables for the SQL driver, EID=eeee. The SYSIBM.SYSCOLUMNS table is unavailable, or the primary table DB2 definitions are incomplete. Use the formatted DB2 message in the job log to determine why the table is unavailable. Ensure that the DB2 table definitions for the primary tables needed for the DIM are complete.
VIDGP017 An error was encountered trying to access SYSIBM.SYSCOLUMNS, EID=eeee. There is a problem with the column information for the table. Use supplementary information to determine the table in error and correct.
VIDGP018 Table tttttttt, column cccccccc, contains unsupported data type, EID=eeee The DB2 data type for the column is not supported by CICS VT. Change the data type for the column to one of the CICS VT supported data types:
  • CHAR
  • VARCHAR
  • DECIMAL
  • LONGVAR
  • NUMERIC
  • DATE
  • SMALLINT
  • BIGINT
  • TIME
  • INTEGER
  • TIMESTAMP
VIDGP019 ` SQL CODE cccc received accessing VID_SRC table for DIM dddddddd, data set ssssssss. Job terminated. The CICS VT system table VID_SRC is not available. Use the formatted DB2 message in the job log to determine why the table is unavailable.
VIDGP025 DDM ddddddd successfully processed. The source code for the SQL drivers for the DDM has been successfully built in VID_SRC table. The stage 2 for the SQL drivers should now be run. This is for information only.
VIDGP034 Unable to determine the primary key for the following primary DB2 table. The GEN utility cannot process the DB2 primary key for the table associated with this data set. Define the primary key and rerun the generation utility.
VIDGP038 SQL CODE cccc received reading table VID_FIELD for AIX® dddddddd. Job terminated. Mapping error for the alternate index path with a DIM name of ddddddd. Correct the cause of the SQL error and rerun the generation utility.
VIDGP039 SQL CODE cccc received reading table SYSIBM.SYSCOLUMNS for AIX dddddddd. Job terminated. Probable error in mapping of an alternate index path. Correct the error and rerun the generation utility.
VIDGP041 SQL CODE cccc received verifying key length for DIM dddddddd. Job terminated. An error has occurred with the mapped KEY field. If SQLCODE is -811 then there is more than one KEY field defined. Correct the mapping for the KEY field.
VIDGP042 Data set dddddddd has a key greater than 255 bytes. Job terminated. Unknown. Correct the mapping for the KEY field.
VIDGP043 Error accessing DB2 bind member name. Member not found. The member name specified in the defaults panel 1 for BIND model in SVIDSAMP does not exist in the SVIDSAMP data set. Either create the member or specify an existing member.
VIDGP044 Error accessing DB2 bind member name. Return=xx Reason=yy. There was a FIND macro error accessing member name in the defaults panel 1 for BIND model in SVIDSAMP option. Review the FIND macro completion codes for xx and yy in z/OS DFSMS Macro Instructions for Data Sets.




Last updated: December 6, 2013 20:43:8

Information Information

Feedback


Timestamp icon Last updated: Friday, 6 December 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///topics/cvtug_ddm_msgs.html