![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This is an informational message that is displayed in the gateway's job log when the DEBUG option is used in the input control parameters. It echoes request calls to the CA-IDMS Gateway.The external gateway is beginning its startup processing.The external gateway startup process is processing the input control parameters specified in the data set identified by the DDNAME IDMSSRV0.The CA-IDMS Gateway is opening a port by using the indicated model identifier to generate a communications port name.The gateway communications port cannot be opened. Other messages accompany this message and provide more specific information.Verify that the TDS and the MDL parameters are specified correctly in the input control. Take action based on the accompanying messages that contain more specific information.The indicated number of gateway subtasks are being started.The attachment of a gateway subtask failed.Check that the CA-IDMS Gateway is authorized to use console support via the MODIFY command.The operator commands for CA-IDMS as specified in the Accessing CA-IDMS Data manual can be entered from the operator console.The external gateway for the CA IDMS database uses GETMAIN to get the internal storage pool size. The size is controlled by the POOLSIZE parameter in the input control parameters. The default is 256KB.The Object Service Broker CA-IDMS Gateway completed its initialization processing successfully and is ready for requests.The MODIFY command entered from the operator console has invalid syntax.Correct the syntax of the command and enter the command again.The MODIFY command entered from the operator console was accepted and processed accordingly.The MODIFY command entered from the operator console is invalid.For a description of a valid MODIFY command, see the Accessing CA-IDMS Data manual.The percent sign (%) indicates which gateways were shut down with the MODIFY command from the operator console.These are the headings for messages S6BID017I and S6BID018I.The gateway name and status are displayed as requested with the MODIFY command from the operator console.The percent signs (%) are replaced with the maximum number of gateways allowed in the session, the High Water Mark reached so far, and the number of gateways currently active.TIBCO(r) Object Service Broker communication CLOSEDThe communication port to the Data Object Broker is closed. The shutdown is proceeding normally.TIBCO(r) Object Service Broker request handler DELETEDCommunication routines were deleted from memory. The shutdown is proceeding normally.The module for the interface to the CA-IDMS database was removed from memory. The shutdown is proceeding normally.The Gateway shut down successfully.Gateway subtask ABNORMALLY TERMINATED> %An gateway subtask abnormally terminated with the indicated abend code.Save all dumps and circumstances that might have caused the abend and contact TIBCO Support.% connection to TIBCO(r) Object Service Broker failedThe physical connection to the Data Object Broker failed.Correct the communications identifier specified in the TDS parameter and activate the Data Object Broker.The internal request code sent from the Execution Environment is unknown to the CA-IDMS Gateway.Check that the versions of the Data Object Broker, Execution Environment, and the CA-IDMS Gateway are compatible.CA-IDMS run unit was ACTIVE - ROLLBACK performedA shutdown request was received while a transaction was active. A ROLLBACK is performed.CA-IDMS statistics displayed at transaction end if DEBUG has been specified in the Object Service Broker CA-IDMS gateway startup parameters. Statistics are retrieved via the CA-IDMS ACCEPT STATISTICS request.The current software version of the CA-IDMS Gateway is displayed.The maximum number of tables you are allowed to access in one transaction is 32. This limit has been exceeded.The indicated CA-IDMS error status for the indicated record was encountered.Check the CA-IDMS error message manual to determine the CA-IDMS error status code.CONVERSION ERROR on field % in record % DBKEY=%, %A data conversion error was detected while converting from CA-IDMS to Object Service Broker. The field name of the field in error, the CA-IDMS record name, the DBKey of the CA-IDMS record and the cause of the error are contained in the message.Use the DBKey to view and possibly correct the field in error via a CA-IDMS product (e.g., DML/O). The DBKey displayed is a 4 byte binary field display in decimal. For example DBKEY=19205121 converted to hexadecimal equals 1250C01 where 1250C is the CA-IDMS page number and 01 is the relative record number. Convert 1250C to decimal and the DBKey for DML/O becomes 75020-001.The CA-IDMS Gateway cannot decipher the selection criteria for the table accessed.The key field requested for the table access was not located in the table definition.Check the table @IDMSFIELDS for the indicated field and regenerate the table definition.The indicated error was detected by the data conversion routine converting from Object Service Broker to CA-IDMS.Verify that the table definition is correct, check for redefined fields in the table definition, and check that the version of the subschema definition loaded into Object Service Broker is correct.The I/O area used for CA-IDMS records is full.The GET or FORALL directive stored in the table @IDMSACCESS is unknown to the external gateway.Use the Table Definer to correct the definition of the Object Service Broker external table for an CA-IDMS database and retry the transaction.Internal error. A message sent to the Data Object Broker failed because of a communication error.Contact your network services department to determine the cause of the error.An Internal logic error has occurred. Possible storage corruption in the Object Service Broker CA-IDMS Gateway. Review number of Object Service Broker tables and CA-IDMS records defined in the transaction.CA-IDMS database keys are internally attached to the external table definition to provide proper replace and delete processing.Check the table definition to ensure that the database definitions exist.Internal error. An internal record pointer was corrupted.To ensure data integrity, all ELEMENTS for the lowest-level record in the access path must be defined in the table definition to do the insertion.Verify that the table definition includes all the elements from the lowest-level record (excluding FILLER elements).Due to CA-IDMS navigational constraints, nested FORALL statements on the same table are not allowed.Change your Object Service Broker rule to remove the nested FORALLs.The field specified in the selection was not found in the internal table definition.The Object Service Broker selection evaluator cannot decipher the selection criteria.Error converting FIXED to EXPANDED format for table %An error was detected when converting from the CA-IDMS format to the internal Object Service Broker format.Do one or both of the following: regenerate the table definition and/or reload the subschema definition.This is an information message indicating the Data Object Broker where the gateway is attached.This is the maximum length of the internal definition of a CA-IDMS table that can be passed to the gateway. The value is retrieved from the Data Object Broker startup parameter CTABLESIZE.No record in the table is qualified to be deleted. The last record in an access path that is an "Obtain CALC", "Obtain First in Set", or "Obtain First in Area" (see access path directives) is the record that will be deleted. None of these directives can be found in the access path.More than one record type makes up the table definition. A DELETE where the key equals a value can only be specified for tables that have one record in the access path, and that record must be a CALC record.Use a qualified GET or optimized FORALL processing to specify the record you want to delete.The specified subschema was not found in the specified dictionary.The specified DD name was not found in the JCL.Check that the data set has all the valid attributes (i.e., RECL, BLKSIZE).The SYSIN statement has invalid syntax.Correct the SYSIN statement and resubmit the job.There is not enough storage available to GETMAIN the required storage areas.Make sure that the MODE statement in member XLINKIDM in the job control library reads MODE AMODE(31),RMODE(ANY). If RMODE is ANY specify a smaller POOLSIZE (i.e., 250 (the default)) and/or specify a larger region size.Initialization of the storage pool GETMAINed at gateway startup failed.Restart the gateway with a smaller POOLSIZE (i.e., 250 (the default)).Security profile STORAGE POOL INITIALIZATION failedSecurity profile STORAGE POOL INITIALIZATION failed. Initialization for the storage pool GETMAINed to store security profiles failed.Increase the region size of the gateway startup job and retry.Insufficient space to store user's security profile.More than 1,000 different users have been signed on since the gateway was recycled. The very first time a user accesses a gateway a security control block is stored. Subsequent accesses will use the stored control block instead of recreating it every time. Recycle the gateway to force an initialize of the storage pool.CA-ACF2 security storage pool initialization has been completed.Message indicating that a security control block has been created for the specified user.The security profile control block could not be constructed. Check the indicated user security access level.The CA-IDMS gateway must be AUTHORIZED to use EXTERNALSECURITY=ACF2The CA-IDMS Gateway must run from an authorized library in order to use CA-ACF2 security (i.e., EXTERNALSECURITY=ACF2).Make sure the CA-IDMS Gateway is link-edited with SETCODE AC(1) and that the library where the gateway resides is an authorized library.PARAMETER ERRORS FOUND... Gateway terminatedOne or more parameters was found to be in error.Correct the parameters in error and restart the job.The version number of the Data Object Broker does not match the version of the CA-IDMS Gateway.Review the installation procedure to ensure that the proper version of the CA-IDMS Gateway is being executed.Parameter instance has changed... Request denied for table %The parameter value for a table cannot change between a GET or a FORALL and a REPLACE.The sort key selection provided in the access statement was too large to fit in the gateway's work area.Decrease the size of the selection specified. Contact TIBCO Support.The Fail Safe table named @IDMFSTRXDB, or the table specified in the FSTABLENAME parameter, could not be loaded.Consult the Object Service Broker CA-IDMS Installation, Operations, and Usage manual for an explanation of defining the Fail Safe database to Object Service Broker.The IDMS connect function could not be done for the indicated record and set.Message received from the Fail Safe CTABLE setup routine.Review the message content for a further explanation of the error. Review the Fail Safe processing section of the Object Service Broker CA-IDMS manual.The IDMS Gateway tried to bind a record that had already been bound but found it to have a different record length. The probable cause is that the subsequent table definition uses a different subschema than the first of those that have a record view defined.Correct the offending table definition to use the correct subschema.Insufficient storage available to store the CTABLE for %There was insufficient storage available to store the internal representation of the table being accessed (CTABLE).Increase the POOLSIZE parameter and restart the gateway.The CA-IDMS schema version for the specified subschema could not be found.Verify the CA-IDMS data dictionary definition for the given subschema. Check that the dictionary or dbname specified is correct.The CA-IDMS Gateway is not running authorizedThe IDMS Gateway is being executed from an unauthorized library or one or more of the libraries in the STEPLIB concatenation is unauthorized.Ensure that the library the IDMS Gateway executes from, and all the libraries in the STEPLIB concatenation, are authorized.The Gateway is running in authorized mode.The IDMS Gateway address space is non-swappable.The IDMS Gateway address space is swappable. In a high volume system this can degrade performance.Mixed Subschema detected: RU using %, Table % defined with %A transaction has attempted to access two or more IDMS tables defined with different subschemas. A transaction is only allowed to access one subschema and that is the first subschema referenced. Accessing subsequent tables could cause data to be mapped incorrectly.Review the application to ensure that the tables can be accessed with the subschema first referenced. Depending on the processing requirements you may wish to code the IDMS gateway parameter MIXEDSSCDETECTION to define the action that should be taken for this condition which include:The 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 |