Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : ID: CA IDMS Gateway

ID: CA IDMS Gateway
S6BID000I
%
CA IDMS Gateway
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.
No action is required.
S6BID001I
CA-IDMS Gateway initialization
CA IDMS Gateway
The external gateway is beginning its startup processing.
No action is required.
S6BID002I
Processing control input
CA IDMS Gateway
The external gateway startup process is processing the input control parameters specified in the data set identified by the DDNAME IDMSSRV0.
No action required.
S6BID004I
Opening a model port: %
CA IDMS Gateway
The CA-IDMS Gateway is opening a port by using the indicated model identifier to generate a communications port name.
No action is required.
S6BID005E
Open port failed
CA IDMS Gateway
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.
S6BID006I
Attaching % gateway subtask(s)
CA IDMS Gateway
The indicated number of gateway subtasks are being started.
No action required.
S6BID007E
CA-IDMS Gateway subtask failed
CA IDMS Gateway
The attachment of a gateway subtask failed.
Possible causes of failure are:
S6BID008E
Start CIB not freed
CA IDMS Gateway
The console support setup failed.
Check that the CA-IDMS Gateway is authorized to use console support via the MODIFY command.
S6BID009I
Console support ready
CA IDMS Gateway
The operator commands for CA-IDMS as specified in the Accessing CA-IDMS Data manual can be entered from the operator console.
No action required.
S6BID010I
Storage POOLSIZE=%
CA IDMS Gateway
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.
No action required.
S6BID011I
INITIALIZATION COMPLETE
CA IDMS Gateway
The Object Service Broker CA-IDMS Gateway completed its initialization processing successfully and is ready for requests.
No action is required.
S6BID012I
Console command REJECTED; Invalid syntax
CA IDMS Gateway
The MODIFY command entered from the operator console has invalid syntax.
Correct the syntax of the command and enter the command again.
S6BID013I
Console command ACCEPTED
CA IDMS Gateway
The MODIFY command entered from the operator console was accepted and processed accordingly.
No action required.
S6BID014I
Console command UNKNOWN
CA IDMS Gateway
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.
S6BID015I
% gateway(s) SHUTDOWN
CA IDMS Gateway
The percent sign (%) indicates which gateways were shut down with the MODIFY command from the operator console.
No action required.
S6BID016I
GATEWAY STA USERID
CA IDMS Gateway
These are the headings for messages S6BID017I and S6BID018I.
No action required.
S6BID017I
% % %
CA IDMS Gateway
The gateway name and status are displayed as requested with the MODIFY command from the operator console.
No action required.
S6BID018I
MAX=% HWM=% ACT=%
CA IDMS Gateway
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.
No action required.
S6BID019I
TIBCO(r) Object Service Broker communication CLOSED
CA IDMS Gateway
The communication port to the Data Object Broker is closed. The shutdown is proceeding normally.
No action required.
S6BID020I
TIBCO(r) Object Service Broker request handler DELETED
CA IDMS Gateway
Communication routines were deleted from memory. The shutdown is proceeding normally.
No action required.
S6BID021I
CA-IDMS interface module DELETED
CA IDMS Gateway
The module for the interface to the CA-IDMS database was removed from memory. The shutdown is proceeding normally.
No action required.
S6BID022I
FREEING storage
CA IDMS Gateway
The storage pool was freed.
No action required.
S6BID023I
CA-IDMS Gateway terminated
CA IDMS Gateway
The Gateway shut down successfully.
No action is required.
S6BID026E
Gateway subtask ABNORMALLY TERMINATED> %
CA IDMS Gateway
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.
S6BID027E
% connection to TIBCO(r) Object Service Broker failed
CA IDMS Gateway
The physical connection to the Data Object Broker failed.
Correct the communications identifier specified in the TDS parameter and activate the Data Object Broker.
S6BID028E
Unknown execution environment request code=%
CA IDMS Gateway
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.
S6BID029I
CA-IDMS run unit was ACTIVE - ROLLBACK performed
CA IDMS Gateway
A shutdown request was received while a transaction was active. A ROLLBACK is performed.
No action required.
S6BID030I
Phy I/Os: % DB calls: % Recs rqst: %
CA IDMS Gateway
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.
No action is required.
S6BID032I
CA-IDMS Gateway version %
CA IDMS Gateway
The current software version of the CA-IDMS Gateway is displayed.
None.
S6BID033E
Maximum number of tables allowed exceeded
CA IDMS Gateway
The maximum number of tables you are allowed to access in one transaction is 32. This limit has been exceeded.
Divide the transaction into smaller units.
S6BID034E
CA-IDMS ERROR status % RECORD %
CA IDMS Gateway
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.
S6BID035E
CONVERSION ERROR on field % in record % DBKEY=%, %
CA IDMS Gateway
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.
S6BID036E
Selection criteria specified invalid
CA IDMS Gateway
The CA-IDMS Gateway cannot decipher the selection criteria for the table accessed.
Correct the table selection and retry.
S6BID037E
Key field not a field in table %
CA IDMS Gateway
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.
S6BID038E
CONVERSION ERROR on field %: %
CA IDMS Gateway
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.
S6BID039E
CA-IDMS server record I/O buffer full
CA IDMS Gateway
The I/O area used for CA-IDMS records is full.
Restructure your transaction into smaller units.
S6BID040E
Unsupported GET or FORALL directive: %
CA IDMS Gateway
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.
S6BID041E
Data Object Broker communication failure
CA IDMS Gateway
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.
S6BID043E
Internal synchronization error
CA IDMS Gateway
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.
Contact TIBCO Support.
S6BID044E
Necessary DBKEY fields not defined in table %
CA IDMS Gateway
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.
S6BID045E
% record not defined in access path of table %
CA IDMS Gateway
Internal error. An internal record pointer was corrupted.
Contact TIBCO Support.
S6BID046E
INSERT failed. All elements not represented in table %
CA IDMS Gateway
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).
S6BID047E
Nested FORALL on a CA-IDMS table not allowed
CA IDMS Gateway
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.
S6BID048E
Selected field not found in table %
CA IDMS Gateway
The field specified in the selection was not found in the internal table definition.
Regenerate the table definition and retry.
S6BID049E
Internal selection evaluation error on table %
CA IDMS Gateway
The Object Service Broker selection evaluator cannot decipher the selection criteria.
Simplify the selection criteria.
S6BID050E
Error converting FIXED to EXPANDED format for table %
CA IDMS Gateway
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.
S6BID051I
Connecting % to TDS %
CA IDMS Gateway
This is an information message indicating the Data Object Broker where the gateway is attached.
No action is required.
S6BID052I
Maximum CTABLESIZE = %
CA IDMS Gateway
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 action required.
S6BID053E
No record in table % could be deleted
CA IDMS Gateway
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.
Properly define the table.
S6BID054E
DELETE where key =, Not valid for table %
CA IDMS Gateway
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.
S6BID055E
Subschema % not found in dictionary %
CA IDMS Gateway
The specified subschema was not found in the specified dictionary.
Specify a valid subschema name.
S6BID056E
No DD statement found for %
CA IDMS Gateway
The specified DD name was not found in the JCL.
Specify all the necessary DD statements.
S6BID057E
Open error encountered for %
CA IDMS Gateway
The file cannot be opened.
Check that the data set has all the valid attributes (i.e., RECL, BLKSIZE).
S6BID058E
Syntax error in request format
CA IDMS Gateway
The SYSIN statement has invalid syntax.
Correct the SYSIN statement and resubmit the job.
S6BID059E
Insufficient storage available to start gateway %
CA IDMS Gateway
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.
S6BID060E
Storage pool initialization failed for %
CA IDMS Gateway
Initialization of the storage pool GETMAINed at gateway startup failed.
Restart the gateway with a smaller POOLSIZE (i.e., 250 (the default)).
S6BID061E
Security profile STORAGE POOL INITIALIZATION failed
CA IDMS Gateway
Security 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.
S6BID062E
Insufficient space to store users security profile
CA IDMS Gateway
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.
S6BID063I
CA-ACF2 security INITIALIZATION DONE
CA IDMS Gateway
CA-ACF2 security storage pool initialization has been completed.
No action required.
S6BID064I
ACMCB built for user %
CA IDMS Gateway
ACMCB built for the specified user.
Message indicating that a security control block has been created for the specified user.
S6BID065E
ACMCB for % could not be built
CA IDMS Gateway
ACMCB for this userid could not be built.
The security profile control block could not be constructed. Check the indicated user security access level.
S6BID066E
The CA-IDMS gateway must be AUTHORIZED to use EXTERNALSECURITY=ACF2
CA IDMS Gateway
The 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.
S6BID067E
PARAMETER ERRORS FOUND... Gateway terminated
CA IDMS Gateway
One or more parameters was found to be in error.
Correct the parameters in error and restart the job.
S6BID068E
CA-IDMS Gateway version mismatch
CA IDMS Gateway
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.
S6BID069E
Parameter instance has changed... Request denied for table %
CA IDMS Gateway
The parameter value for a table cannot change between a GET or a FORALL and a REPLACE.
Correct the offending rule.
S6BID071I
Sort Key value exceeds work area size for table %
CA IDMS Gateway
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.
S6BID072E
Load of the Fail Safe table % failed
CA IDMS Gateway
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.
S6BID073E
Cannot CONNECT % to % set
CA IDMS Gateway
The IDMS connect function could not be done for the indicated record and set.
Verify that the IDMS set option is manual.
S6BID074E
%
CA IDMS Gateway
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.
S6BID075E
Two different views of record % detected
CA IDMS Gateway
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.
S6BID076E
Insufficient storage available to store the CTABLE for %
CA IDMS Gateway
There was insufficient storage available to store the internal representation of the table being accessed (CTABLE).
Increase the POOLSIZE parameter and restart the gateway.
S6BID080E
% DD statement not found
CA IDMS Gateway
Future use
No action required
S6BID081E
Schema % Version % not found
CA IDMS 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.
S6BID082I
The CA-IDMS Gateway is not running authorized
CA IDMS Gateway
The 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.
S6BID083I
The CA-IDMS Gateway is running authorized
CA IDMS Gateway
The Gateway is running in authorized mode.
None.
S6BID084I
The CA-IDMS Gateway is non-swappable
CA IDMS Gateway
The IDMS Gateway address space is non-swappable.
None.
S6BID085I
The CA-IDMS Gateway is swappable
CA IDMS Gateway
The IDMS Gateway address space is swappable. In a high volume system this can degrade performance.
None.
S6BID086I
Mixed Subschema detected: RU using %, Table % defined with %
CA IDMS Gateway
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:
S6BID401I
% Gateway shutdown requested, reason="%"
CA IDMS Gateway
The gateway received a request to shut down from the TIBCO(r) Object Service Broker The description of the reason codes follows:
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.
No further action is required.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved