![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The gateway failed to connect to the specified Data Object Broker.Ensure that the Data Object Broker is up. Ensure that the correct value is specified on the TDS startup parameter.The specified DD card could not be found in the jobstep.Ensure the startup JCL contains the specified DD card.An error occurred during the attempt to open the data set associated with the specified DD card.An error occurred during the attempt to open the data set associated with the specified DD card.The specified startup parameter was not supplied the correct value.Ensure the startup parameter has an allowed value.One of the required startup parameters was not supplied.Ensure all the required startup parameters are supplied.Security parameters required with SECLEVEL=1If SECLEVEL=1, the IMS gateway requires more startup parameters in order to correctly define the security requirements.Specify one of the Resource/Class and/or DBDclass or Segclass.If SECLEVEL=1, the Resource must be coded if the Class is coded and vice versa.Ensure both Class and Resource have been coded.If SECLEVEL=1, DBDclass and Segclass are mutually exclusive.Code only one of the DBDclass or Segclass, not both.Both SEGCLASS and PSBNAME must be suppliedIf SECLEVEL=1, the PSBNAME is also required if the Segclass is coded.Number of records in IMSSEC00 exceeds the maximum allowedEnter a number that is equal to or below the maximum.An attempt to load the specified PSBNAME as specified on the startup parameter failed.Ensure the specified PSBNAME is in //IMS DD DSN=IMS.PSBLIB.The specified gateway is terminating.No action is required; part of shutdown processing.Ensure the startup parameters are correct.The Execution Environment External Data Server initializer/terminator does not recognize the gateway type. This may occur due to a version mismatch between the external data gateway and the Execution Environment.Ensure that the external data gateway and the TIBCO(r) Object Service Broker were properly installed. If the problem persists, contact TIBCO Support.TRXDB gateway startup parameter required with Fail Safe level 1.There may be a version mismatch between the different IMS Gateway modules.The PSB used to start up the gateway did not contain any database PCBs.At least one DB PCB is required for a gateway PSB.There may be a version mismatch between the different IMS Gateway modules.For the IM2 Gateway, this indicates that correct installation procedures were not followed, since the DB2 Gateway code was not linked in with the IMS Gateway code.Ensure the IMS Gateway installation was done correctly.There may be a version mismatch between the DB2 Gateway module and the IMS Gateway module.Module mismatch for the IM2 gateway.No PCB for the specified DBD could be found during FSLEVEL=1 gateway startup processing.If FSLEVEL=1 then PSB must contain PCB for the Fail Safe database.OP02-"%" TIBCO(r) Object Service Broker version mismatchA mismatch of versions was encountered.The IMS Gateway is ready to process requests.The PSB used to start up the gateway did not contain an I/O PCB.Check whether CMPAT=YES is specified in PSBGEN statement for the gateway PSB. This is required because the gateway expects the first PCB to be an I/O PCB.Echo Object Service Broker request in the following format: gateway userid, tranid, type of request, and table name.IMS table definition not found in Object Service Broker.Check table name, supply definition if required.POOLSIZE startup parameter is too small to hold the requested number of table definitions in this transaction.To rerun the transaction, the gateway must be shut down and restarted with a larger POOLSIZE value.The request issued to Object Service Broker is not supported.Requires third-level support if not version mismatch.SECLEVEL=1 and the Object Service Broker session ID is not a valid userid as far as SAF is concerned (SECURITYFAIL).Ensure the Object Service Broker session ID is defined externally (RACF, TSS, CA-ACF2).Access Denied: UID(%) RESOURCE(%) CLASS(%)The Object Service Broker session ID is not allowed access to the resource and class (SECURITYFAIL).Server startup parameter EXTERNALUSERID=GROUP was specified. In order for the gateway to use the current group ID, the group ID must not exceed 8 bytes in length.Make sure the current group value does not exceed 8 bytes if accessing the IMS gateway with SECLEVEL=1 and EXTERNALUSERID=GROUP.The gateway could not verify the Object Service Broker userid. The verification failed because SAF returned a SAF return code of 4 indicating that the userid is not defined to (RACF/ACF2/TSS/...) or that SAF could not pass the request on to (RACF/ACF2/TSS/...). SECURITYFAIL will be returned to the Object Service Broker user session that initiated the request. Userid verification is done through the RACROUTE REQUEST=VERIFY call to SAF. % = userid||group.Make sure the gateway is using the correct userid group and the userid is defined to the external security product (ACF2/TSS/RACF). Make sure the SAF router for the external security product is installed, including the correct SAFmaps and SAFprot record entries.The gateway could not verify the Object Service Broker userid access to a resource. The verification failed because SAF returned a SAF return code of 4 indicating that the specified RESOURCE/CLASS is not defined to (RACF/ACF2/TSS/...) or that SAF could not pass the request on to (RACF/ACF2/TSS/...). SECURITYFAIL will be returned to the Object Service Broker user session that initiated the request. Resource verification is done through the RACROUTE REQUEST=AUTH call to SAF.Make sure the gateway is using the correct userid group and the userid is defined to the external security product (ACF2/TSS/RACF). Make sure the SAF router for the external security product is installed including the correct SAFmaps and SAFprot record entries.The PSBNAME in the table definition is not valid.Modify the table definition and resubmit the request.The gateway was started with THREADUSAGE=TABLE and a transaction accessed two tables with different PSBs.THREADUSAGE=TABLE says that all TABLES accessed in one transaction must have the same PSB in their definition or have the PSB not specified.The plan in the table definition is not valid.Modify the table definition and resubmit the request.Scheduled "%" and requested "%" DB2 PLANs do not matchThe gateway was started with THREADUSAGE=TABLE and a transaction accessed two tables with different PSBs.THREADUSAGE=TABLE says that all tables accessed in one transaction must have the same PSB in their definition or have the PSB not specified.Debug messages during optimize update processing.Attempting to access an IMS database for which no PCB was supplied in the gateway startup PSB.Stop the gateway, add the PCB to the PSB, and restart the gateway with the modified PSB.Mode=RO gateway received an update request from the TIBCO(r) Object Service Broker.Do not attempt to update IMS data using a read-only IMS Gateway.An attempt was made to insert/replace a segment that had two or more fields mapping parts of the segment two or more times.Correct the definition so that the segment being replaced/inserted does not have overlapping fields.An attempt was made to insert a segment that was not correctly mapped by an Object Service Broker IMS table, or a replace was attempted using optimize update where the segment was not correctly defined.Correct the definition so that the segment being replaced/inserted is correctly defined. You must ensure that fields do not overlap or updates will be disallowed. The total length of the mapping fields must equal the DBD segment size if dealing with fixed segment sizes.An attempt was made to insert using secondary index access. This is not allowed in IMS.Data access call had order on selection when using optimize update.Order processing is not supported with optimize update access.REPLACE/DELETE was issued without prior GET using optimize update.Prior to a REPLACE/DELETE you must issue a GET/FORALL, if you are using optimize update.IMS Database PCB "%" is not sensitive to segment "%"For SECLEVEL=1, the PSB specified for the startup PSBNAME is not sensitive to the specified segment.Ensure the gateway PSB and startup PSBNAME are the same. If they are, make sure the PSB is sensitive to the desired segment.Non-unique segments can only be updated using optimize updateCannot replace/delete non-unique segments, if the table is not defined with optimize update on.Set optimize update=Y in the table definition in order to replace/delete non-unique segments.Gateway PSB and security PSB (PSBNAME=) do not matchThe PSB used to start up the gateway must be equal to the value specified on the gateway startup parameter PSBNAME.Change the PSBNAME parameter and restart the gateway.Gateway security initialization is starting.Security access check for userid, resource, class and type.Check Access: UID(%) RESOURCE(%) CLASS(%) TYPE(%)Security access check for userid, resource, class and type.The call to access DL/I data did not complete successfully.
• If the STATUS CODE is not blank, then look up the STATUS CODE in the IMS messages and codes/application developers guide and take appropriate action.The call to access DL/I data did not complete successfully.
• If the STATUS CODE is not blank, then look up the STATUS CODE in the IMS messages and codes/application developers guide and take appropriate action.Gateway I/O area overflow on DL/I call "%" using DBD "%"The returned amount of data from the indicated DL/I call for the indicated IMS database exceeds the gateway's I/O area.The gateway's I/O area is 32 KB. If the returned amount of data should not have exceeded this size then a version mismatch may have occurred.IMSUSRXT coded by customer failed a request.Attempt to insert multiple segments has failed.REPL/ISRT/DLET loop failed. Maximum SSA count reachedThe IM2 gateway running under the Execution Environment using the BMP interface requires that the program name be used as the PLAN name when connecting to DB2. Since the gateway's program name will always be S6BDRSSR, then prior to invoking DFSRRC00, program S6BDRSSR is identified to z/OS as the requested DB2 PLAN name. On this occasion the identification failed.The REASON is the return code from the IDENTIFY macro instruction.Converting IMS data to Object Service Broker data has failed for the indicated Object Service Broker field name. Convert2 message will follow.Make sure the IMS database contains data that matches the external syntax as defined for the Object Service Broker IMS table.DL/I (%) CALL; STATUS CODE (%); DBNAME (%) PSB (%) RC(%) USING (%) SEGMENT(;,;,;)The call to access DL/I data did not complete successfully.
• If the STATUS CODE is not blank, look up the STATUS CODE in the IMS messages and codes/application developers guide and take appropriate action.
• If the STATUS CODE is blank, then the RC value may contain more information:
• RC(TIMEOUT) - The call failed to complete within the DLITIMEOUT= value specified at gateway startup. The gateway task has terminated and any updates to DL/I should have been rolled back depending on the interface to DL/I being used USING(DLI/DBB/BMP/CICS).
• RC(Q-LIMIT) - The number of DL/I GU/GN/ calls since the last CHKP/ROLB exceeds the DLIQUERYLIMIT value specified at startup.
• RC(U-LIMIT) - The number of DL/I GHU/GHN/ISRT calls since the last CHKP/ROLB exceeds the DLIUPDATELIMIT value specified at startup.
• If USING(CICS), the last four (4) hex digits of the RC contain the CICS-DL/I User Interface Block (UIB) Return Codes.DL/I (%) CALL; STATUS CODE (%); PSB (%) RC(%) USING (%)The call to access DL/I data did not complete successfully.
• If the STATUS CODE is not blank, look up the STATUS CODE in the IMS messages and codes/application developers guide and take appropriate action:
• If the STATUS CODE is blank, then the RC value may contain more information.
• RC(TIMEOUT) - The call failed to complete within the DLITIMEOUT= value specified at gateway startup. The gateway task has terminated and any updates to DL/I should have been rolled back depending on the interface to DL/I being used USING(DLI/DBB/BMP/CICS).
• If USING(CICS), the last four (4) hex digits of the RC contain the CICS-DL/I User Interface Block (UIB) Return Codes.DL/I (;) CALL;; STATUS CODE (;);; DBNAME (;) PSB (;) RC(;) USING (;)The call to access DL/I data did not complete successfully.
• If the STATUS CODE is not blank, then look up the STATUS CODE in the IMS messages and codes/application developers guide and take appropriate action.
• If the STATUS CODE is blank, then the RC value may contain more information.
• RC(TIMEOUT) - The call failed to complete within the DLITIMEOUT= value specified at gateway startup. The gateway task has terminated and any updates to DL/I should have been rolled back depending on the interface to DL/I being used USING(DLI/DBB/BMP/CICS).
• RC(Q-LIMIT) - The number of DL/I GU/GN/ calls since the last CHKP/ROLB exceeds the DLIQUERYLIMIT value specified at startup.
• RC(U-LIMIT) - The number of DL/I GHU/GHN/ISRT calls since the last CHKP/ROLB exceeds the DLIUPDATELIMIT value specified at startup.
• If USING(CICS), the last four (4) hex digits of the RC contain the CICS-DL/I User Interface Block (UIB) Return Codes.Gateway DL/I call limit exceeded: DL/I unit of work has been rolled backOne of DLIQUERYLIMIT or DLIUPDATELIMIT was exceeded in a previous call. The gateway notified the caller of this but the caller did not request a CHKP or ROLB which are the only two allowed actions after a call limit has been exceeded. The gateway rolled back the current DL/I unit of work.Change the application so that on a Q-LIMIT or U-LIMIT from IMS Gateway does a commit/rollback.Error building IMS segments: value was not received for data parameter: "%"Error occurred in IMSREC processing.`Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building IMS segments: table definition does not contain segment: "%"Error occurred in IMSREC processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building IMS segments: table definition contains invalid segment entriesError occurred in IMSREC processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building IMS segments: maximum field size exceeded for: "%"Error occurred in IMSREC processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building IMS segments: SSA segment pointers do not match table definitionError occurred in IMSREC processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building IMS segments: conversion, internal to IMS, field: "%"Error occurred in IMSREC processing.Ensure the table definitions match the IMS databases definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure that table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error building SSA: conversion, internal to IMS, field: "%"Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Error occurred in IMSSSA processing.Ensure the table definitions match the IMS database definition. If the definitions match, contact TIBCO Support.Bad return code from selecnam. Possible definition error.Ensure selection criteria matches definition. If it does not match, contact your System Administrator.A message returned from the Data Object Broker at startup indicating the specific failure when trying to retrieve the Fail Safe table definition.As of release 3.0 PUT05 the @IMSFSTRXDB Fail Safe table definition is required to be defined in each Data Object Broker that is using FSLEVEL=1.The Fail Safe table named in the message could not be found.The @IMSFSTRXDB Fail Safe table definition is required to be defined in each Data Object Broker that is using FSLEVEL=1.The IMS DRA start up parameter table could not be found in the IMS gateway steplib.Check that a valid DRASUFFIX has been specified in the IMS gateway start up parameters.A non zero return code was returned from IMS DRA.See the current IMS Messages and Codes IBM manual for a possible explanation of the return code value.The IMS DRA interface has been successfully initialized.The IMS DRA interface has been successfully terminated.IMS/DRA Control exit entered. PAPLFUNC=#, PAPLSFNC=#The IMS DRA control exit has been entered for the reason specified by PAPLFUNC and PAPLSFNC.For an explanation of the PAPLFUNC and PAPLSFNC, see the current IMS Customization Guide.This message shows the IMS DBCTL name to which the IMS gateway is attached.An abnormal IMS system abend has been detected.See the current IMS Messages and Codes IBM manual for an explanation of the System abend codes.An IMS DRA user abend code has been detected.See the current IMS Messages and Codes IBM manual for an explanation of IMS User abend codes.A message indicating that the IMS Server termination is proceeding.Possible IMS DRA versus IMS Gateway version mismatch.A severe IMS DRA failure has occurred.See the current IMS Messages and Codes IBM manual for an explanation of possible failure.Information message indicating that the IMS/DRA interface initialization has started.DFSPRRC0 could not be found in the STEPLIBMake sure DFSPRRC0 is in one of the data sets in the STEPLIB concatenation. Either copy it from the IMS.RESLIB library or include IMS.RESLIB in the STEPLIB concatenationThe gateway received a request to shut down from the TIBCO(r) Object Service Broker The description of the reason codes follows:
• 0000 - TIBCO(r) Object Service Broker is shutting down.
• 0004 - A stopserver all*** was requested. All the gateways of this type will be terminated.
• 0008 - A stopserver gateway userid was requested. Only this gateway will be terminated.
• 0010 - The TIBCO(r) Object Service Broker resource directory is full. Contact TIBCO Support.
• 0014 - The maximum number of gateways has been exceeded. Increase the MAXDBMS parameter in the TIBCO(r) Data Object Broker and restart, or contact TIBCO Support.
• 00018 - The gateway anchor list has overflowed. Contact TIBCO Support.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |