|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
Access to the table has been denied by securityAcquire the adequate access authority from your security administrator.The named table has been created based on the CA-Datacom's Data Dictionary's definition of the data in the table.Review the defined table for compliance with any local standards.Unable to generate a unique DAT table name from CA-Datacom definition "%"The table definition generation is unable to create a unique MetaStor table name to reflect the CA-Datacom's definition of the table.Use the normal Table Definer utility to create a unique MetaStor table definition of this CA-Datacom table.Redefines not supported for DAT table definition: CA-Datacom table "%"Only one definition of a portion of a record is allowed. Table definition generation will only use the first definition found.Create a different MetaStor table definition for each of the CA-Datacom table redefinitions.The CA-Datacom field's data type does not have a corresponding MetaStor field syntax or conversion.Use the RD syntax to access the field in its raw form.Unable to generate unique DAT field name from CA-Datacom field "%"The named field name is not unique enough for the table generation facility to create the required unique MetaStor field name.Use the normal Table Definer utility to create the MetaStor definition of this CA-Datacom table, assigning your own unique field names.The named CA-Datacom table definition was not found in the extract tables.Run an extract of the CA-Datacom Data Dictionary to get the metadata for this table, or correct the spelling of this table name.Please use a security-level-1 OSB userid to generate CA-Datacom tablesYou should use a security-level-1 OSB userid to create definitions. Otherwise, other users will not be able to access the generated table definition.Switch to a userid with level-one security. If the table needs a higher security level, assign it after the definition has been generated, or use the standard Table Definer utility to create the definition using the userid with a security level higher than one.CA-Datacom extract submitted; please check output of jobThe CA-Datacom Data Dictionary extract job has been submitted.Check the output of the job for correctness. The JCL submitted must be customized before first use.A valid SERVERID must be provided before the CA-Datacom definition can be generated into a MetaStor table definition.Provide the SERVERID that this CA-Datacom table will be accessed with.Gives the table name and field name where the data could not be converted using the MetaStor and CA-Datacom definitions provided.Change the definition of this table to reflect the actual data, or correct the data in the invalid row occurrence.The maximum length for a SERVERID is 8 characters.Provide a SERVERID value of 8 characters or less.The URT associated with the table being access was found neither in the HRNEXTR library nor in the STEPLIB concatenation, or the required CA Datacom table was not found in the URT.Prepare a CA Datacom URT with DBNTRY entry point and place it the load library available to the DAT server through the STEPLIB or HRNEXTR DD statement (see the manual for details).Unexpected RC %-% from CA-Datacom while issuing command(%) against table(%), DBID(%)The CA-Datacom Gateway received an unexpected return code from CA-Datacom while executing the named command against table / DBID, as indicated.Look up the RC returned by the Gateway in the CA Datacom/DB Message Reference Guide to determine the cause of failure.Unexpected RC %-% from CA-Datacom while issuing command(%) against URT(%)Enter the data to indicate the CA-Datacom dictionary information to be extracted.Enter the CA-Datacom table name, ALL or partial* to indicate the eligible tables.The CA-Datacom metadata batch extract only works from TSO/MVSThis facility (CA-Datacom Dictionary extract) only works when initiated from the TSO environment.Exit the Execution Environment you are currently using, and use a TSO Execution Environment to initiate the CA-Datacom Dictionary extract Utility.DBID % (table %) does not have an entry in @DATACOM_URTSThe DBID for the table specified does not have a URT associated with it. The list of URTs loaded at CA-Datacom server startup time can be found in @DATACOM_URTS(serverid).Add the appropriate URT to the @DATACOM_URTS table and retry. Note that the CA-Datacom server does NOT have to be recycled.The URT with the specified name has been closed by an operator request and is unavailable until specifically opened.Wait for the URT to be opened via a OPENURT=name command.The specified URT name has been closed via a CLOUSEURT commandThe specified URT has been marked available by an OPENURT command. The URT will not be opened until the first data access.% % URT name % specified in CLOSEURT or OPENURT not foundThe URT name specified by a CLOSEURT or OPENURT was not found in the server.Look in the CA-Datacom Gateway job log for the list of URTs loaded, and specify a correct name.The named URT has been successfully loadedThe named URT could not be loaded.The URTs to load reside in a LOAD library described in the STEPLIB or HRNEXTR DD statement of the DAT server startup JCL.% % Server initialization FAILED, check the message log for possible causesThe server failed to complete its initialization process.Possible causes are indicated in the log above this message.Information message indicating that the CA-Datacom server has completed normal termination.The SERVERCOMMAND entered in the Data Object Broker is unknown.Message indicating that an indoubt transaction is outstanding for this server. This request queries the Fail Safe transaction database to determine if the indoubt transaction had completed.% % No URT modules found, server terminatingThe server could not find any URT modules to load.A URT named after the server ID or named S6BDATDB could not be found. The URT modules must reside in the load library specified either in the STEPLIB or HRNEXTR DD statement.Displays the values specified in the @SERVERDEBUG table for this gatewayUnsuccessful verification of the (USERID, PASSWORD) pair by OSB DAT Server when running with SECURITYLEVEL=1.Check the USERID and PASSWORD that your application passes to CA Datacom .CA-Datacom user security credentials unavailable or malformed.The server runs with SECURUTYLEVEL=1. The application has passed no security credentials or those passed cannot be used.Make sure the application passes the user security credentials (USERID, PASSWORD) to the DAT server by invoking the SET_DAT_SEC rule.The WHERE clause against table % is too long for the DAT server to process.
|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |