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


Appendix A Messages and Codes : General Messages

General Messages
Table 26 describes the general messages.
 
Table 26 General Messages 
Getmain failed for component.
Explanation: Getmain for the Component block failed.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Attach for pgmid failed rc=rc, type att-type.
Explanation: The attach subroutine for the specified program failed.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Invalid request req to Ysub.
Explanation: An invalid request was found by the support subroutine.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Component cmp still has an SRW pointer.
Explanation: An SRW area still exists during termination.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Explanation: The address space is not authorized.
User Response: Authorize the address space.
System Action: Processing ends.
Explanation: The address space cannot be swapped.
System Action: Processing continues.
Entry cmp has invalid attach type att-type.
Explanation: The attach-type value is invalid.
User Response: Correct the value of attach-type.
System Action: Processing ends.
Dynamic Component cmp created.
Explanation: A component has been created from control statements instead of being predefined.
User Response: Verify that this is the intended action.
System Action: Processing continues.
Explanation: TASK has received a message to quit processing.
User Response: Review the log for the reason for the quick-quit message.
System Action: Processing ends without cleanup.
Component cmp terminated too soon rc:rc rsn:rsn
Explanation: The named component’s task terminated before the stop command was received from the console.
User Response: Examine the log for the reason why the component terminated.
System Action: The rest of the components are signaled to terminate; TIBCO Mainframe Service Tracker terminates.
Explanation: This message is shown in response to a timeout or a SHOW TASK console command.
System Action: Processing continues.
Explanation: This message is shown in response to a timeout or a SHOW TASK console command.
System Action: Processing continues.
Component cmp shared GM error.
Explanation: A shared GetMain failed or too many shared GetMain requests have been received.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Id:cmp stat:status byte intrm:term-indic.
Explanation: This message is shown in response to a timeout or SHOW TASK console command.
System Action: Processing continues.
Component cmp sent exit too soon.
Explanation: A component sent its final message before the stop command.
User Response: Review the log for the reason behind the early termination.
System Action: Processing continues.
Explanation: A component sent its termination-phase message too late.
System Action: Processing continues.
Modify command verb, qual not supported.
Explanation: The console command is not supported by this component.
User Response: Revise and reenter the console command.
System Action: The command is not processed.
Explanation: A component sent its initialization-phase message too late.
System Action: Processing continues.
Comp cmp lost num messages.
Explanation: Since the last task dispatch, num task messages have been lost because no buffers are available.
User Response: Increase the number of buffers for cmp.
System Action: Processing continues.
Comp cmp no proc for subjsubj from cmp.
Explanation: cmp has not defined a processing routine for subject code subj.
User Response: Contact TIBCO Support.
System Action: Processing for this task message was dropped.
Comp cmp type which — no SRW area.
Explanation: cmp issued an SRW request which but had no SRW area.
User Response: Contact TIBCO Support.
System Action: The SRW request is ignored.
Cmp cmp send to cmp-addr not in list.
Explanation: cmp-addr, a pointer to the receiving component, is not on the list of active components.
User Response: Contact TIBCO Support.
System Action: Processing for this task message was dropped.
Cmp cmp send msg to cmp2 — overflow.
Explanation: The buffer definition for cmp2 is too small to accept this message.
User Response: Specify a larger buffer size for cmp2. If the condition persists, contact TIBCO Support.
System Action: Processing for this task message was dropped.
Cmp cmp receiving cmp2 has no buffers.
Explanation: cmp2 has no allocated buffers.
User Response: Contact TIBCO Support.
System Action: Processing for this task message was dropped.
Cmp cmp receiving cmp2 no bufr avail.
Explanation: cmp2 has no free buffers to receive messages.
User Response: Specify a larger number of buffers for cmp2. If the condition persists, contact TIBCO Support.
System Action: Processing for this task message was dropped.
CMP cmp shrqsend — no target.
Explanation: While processing a request to send to a shared queue, TIBCO Mainframe Service Tracker could not find the shared queue.
User Response: Contact TIBCO Support.
System Action: Processing for this task message was dropped.
Cmp cmp send reserved — overflow.
Explanation: The buffer definition for cmp2 is too small to accept this message.
User Response: Specify a larger buffer size for cmp2. If the condition persists, contact TIBCO Support.
System Action: Processing for this task message was dropped.
Cmp cmp auto-send — overflow
Explanation: The buffer definition for the receiving buffer is too small to accept this message.
User Response: Contact TIBCO Support.
System Action: Processing for this task message was dropped.
Request req invalid.
Explanation: The request code req to SRW processing was invalid.
User Response: Contact TIBCO Support.
System Action: Processing for this request was dropped.
Comp cmp — no msg area for diag.
Explanation: A diagnose request found no allocated SRW area.
User Response: Contact TIBCO Support.
System Action: The diagnose request ends.
GM buffers comp cmp failed.
Explanation: The request for allocating the message buffers failed.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Cmp cmp over max msg registered.
Explanation: cmp attempted to define too many message types.
User Response: Contact TIBCO Support.
System Action: Processing ends.
SRW: cmp has active msg from cmp2 subj subj at term.
Explanation: The specified message has not been processed at the end of the termination process.
User Response: Contact TIBCO Support.
System Action: Termination continues.
Comp cmp type which no SRW area.
Explanation: cmp attempted to process a request with code which with no SRW area allocated.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Shared queue qname not found.
Explanation: A request to initialize a shared queue could not find the queue in question.
User Response: Contact TIBCO Support.
System Action: Processing continues.
SRW: cmp has no shared queue for diag.
Explanation: A request for shared queue statistics found no defined shared queue.
User Response: Contact TIBCO Support.
System Action: Processing continues.
SRW: Shr queue qname linked to by cmp.
Explanation: cmp has linked to the shared queue qname.
System Action: Processing continues.
Shrq qnamecmp zero use during termination
Explanation: The use count for a shared queue has dropped below zero during the termination process.
User Response: Contact TIBCO Support.
System Action: Termination continues.
Shrq qname not found by processor cmp.
Explanation: The sender's shared queue does not exist.
User Response: Contact TIBCO Support.
System Action: The component terminates.
Cmp cmp has blank shareq.
Explanation: A component that expected to use a shared queue has none defined.
User Response: Contact TIBCO Support.
System Action: The component terminates.
Free error, SRW of cmp at add, leng leng sp=sp.
Explanation: The STORAGE RELEASE of the SRW area for cmp failed.
User Response: Contact TIBCO Support.
System Action: Termination continues.
CNSL: cmp Quick leave.
Explanation: The console processor has received a quick-leave command and will terminate without cleanup.
User Response: Review the log messages for the reason behind the quick-leave command.
System Action: The console terminates.
CNSL: cmp monitoring started.
Explanation: The console is now monitored for the Modify and Stop commands.
System Action: Processing continues.
CNSL: Error rc from M001.
Explanation: The console interface routine received an error code.
User Response: Contact TIBCO Support.
System Action: Console processing continues.
CNSL: Msg — stop (P).
Explanation: A stop command was received.
System Action: Termination processing starts.
CNSL: Modify: message.
Explanation: A modify message has been received.
System Action: Processing continues.
CNSL: Initialize failed — rc.
Explanation: Initialization of the console failed.
User Response: Contact TIBCO Support.
System Action: The console notifies the task of the failure.
CNSL: Multiple errors — terminating.
Explanation: The console has received multiple errors.
User Response: Contact TIBCO Support.
System Action: The console terminates.
Modify request verb, req not supported.
Explanation: The Modify command directed to the Console processor is not supported.
User Response: Correct and reenter the console command.
System Action: The console command is ignored.
Modify command cmd received.
Explanation: The console command cmd has been received.
System Action: Processing continues.
Invalid recipient rcp on modify command.
Explanation: The target name rcp on the console command is invalid.
User Response: Correct and reenter the console command.
System Action: Processing of this command ends.
Invalid verb verb on modify command.
Explanation: The first value after the target name on the modify command is invalid.
User Response: Correct the verb in the command and resubmit.
System Action: Processing of this command ends.
Extra/invalid value value on modify command.
Explanation: The last value on the modify command is invalid.
User Response: Correct the modify command and resubmit.
System Action: Processing of this command ends.
Explanation: An internal error occurred during the routing of the modify command to the proper component.
User Response: Contact TIBCO Support.
System Action: The command might not be completely processed.
Read error from pgmid: msgnomessage.
Explanation: The PDS access routine returned the error as described.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Mbr mbr premature EOF —- Missing continuation.
Explanation: A syntax error in the control member exists.
User Response: Correct the control statement that is in error.
System Action: Processing ends.
Mbr mbr scan error from pgmid: msgid - message.
Explanation: An error in a control statement exists.
User Response: Correct the control statement that is in error.
System Action: Processing ends.
Pds ddname ddn processed, rc=rc.
Explanation: The specified DDName has been processed with the return code rc.
System Action: Processing continues.
Keyword must appear under a COMPONENT= statement.
Explanation: The keyword after a valid COMPONENT statement is missing.
User Response: Correct the control statement that is in error.
System Action: Processing ends.
Explanation: TIBCO Mainframe Service Tracker is fully initialized and active.
System Action: Processing continues.
Tracker subsys ssid Release v.r.m.b start.
Explanation: TIBCO Mainframe Service Tracker has started.
System Action: Processing continues.
Explanation: TIBCO Mainframe Service Tracker has begun the termination sequence.
System Action: Termination continues.
Tracker ssid shutting down logging.
Explanation: TIBCO Mainframe Service Tracker has completed its termination and is stopping the logging processes.
System Action: Termination is almost complete.
Explanation: An error occurred during initialization.
User Response: Review the log for the error description.
System Action: The process enters termination.
Timeout awaiting TASK startup.
Explanation: The subtask manager TASK did not initialize within the initialization period.
User Response: Review the log for the previous error messages for the reason of initialization failure.
System Action: The process enters termination.
Explanation: The termination process required more than usec microseconds to complete.
User Response: Contact TIBCO Support.
System Action: The process enters final termination.
Main received msg message showing Error.
Explanation: The value of msg is either Console Answer or Task Answer. One of the early startup components signaled startup failure.
User Response: Review the log for previous error messages related to this failure.
System Action: Processing ends.
Explanation: A call to task messaging during startup failed.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Explanation: A call to task messaging during termination failed.
User Response: Contact TIBCO Support.
System Action: Processing of termination continues.
Wait in hung terminate where failed rc rc.
Explanation: An unexpected process request was returned during the timeout period of termination processing.
User Response: Contact TIBCO Support.
System Action: Termination continues.
Explanation: A call to task messaging during initialization failed.
User Response: Contact TIBCO Support.
System Action: Processing ends.
No pthread routine for Cmp cmp program-id pgmid.
Explanation: No routine has been defined for cmp, which is to be created with pthread_create.
User Response: Contact TIBCO Support.
System Action: The process is not created.
Attach failed for pgm in Cmp cmp, rc=rcpre7f.
Explanation: The attach subroutine failed for pgm.
User Response: Review the log for previous error messages.
System Action: The subtask is not created.
Pthread_create failure for cmp rc=rc - reason.
Explanation: Pthread_create failed for cmp with return code rc, explained as reason.
User Response: Contact TIBCO Support.
System Action: Pthread is not created.
Explanation: The job table’s address-send process failed.
User Response: Contact TIBCO Support.
System Action: Processing continues, but TIBCO Hawk cannot access active job status.
Oper: message.
Explanation: This is an echo of message as sent from the SHOW LOG console command.
System Action: Processing continues.
Modify verb qual info not supported.
Explanation: This routine does not support the specified Modify command.
User Response: Correct and reenter the Modify command.
System Action: Processing continues.
Explanation: The control member contains no Run Keys.
User Response: Update the control member.
System Action: Processing ends.
Run Key key valid for num more days.
Explanation: The specified Run Key will expire in num days.
User Response: If no other valid Run Key is available, contact your Tibco representative for renewal.
System Action: Processing continues.
Explanation: The control member contains no valid Run Keys.
User Response: If no other valid Run Key is available, contact your Tibco representative for renewal.
System Action: Processing ends.
Debug level for cmp changed from old debug to new debug.
Explanation: A console command changed the debug value.
System Action: Processing continues.
Debug-srw level for cmp changed from old debug to new debug.
Explanation: A console command changed the srw debug value.
System Action: Processing continues.
Explanation: One or more components failed the edit.
User Response: Review the log for the error descriptions.
System Action: Processing ends.
Value for field name cannot be blank.
Explanation: The input field field name is blank; a value is required.
User Response: Update and resubmit the control member.
System Action: Processing ends.
Error in IEFSSI QUERY call rc:rc-rsnexplanation.
Explanation: The IEFSSI QUERY call received an error with return code rc, reason rsn, explained as explanation.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
No subsystem ssid currently defined.
Explanation: The definition for the subsystem ssid is missing.
System Action: Processing continues.
Explanation: The IEFSSI QUERY indicated a good return but did not return an entry for ssid.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Subsystem ssid is not dynamic.
Explanation: The subsystem ssid is not defined as being dynamic to the system.
System Action: Processing continues.
Subsystem ssid is active; no permission to deactivate.
Explanation: The subsystem ssid is active and DEACTIVATE is not specified.
User Response: Ensure that another version of TIBCO Mainframe Service Tracker is not using the same subsystem ID.
System Action: Processing ends.
Error in IEFSSI DEACTIVATE call rc:rc-rsnexplanation.
Explanation: IEFSSI DEACTIVATE returned an error.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Subsystem ssid values: no permission to replace.
Explanation: The subsystem ssid exists and REPLACE is not specified.
User Response: Either switch to another ssid or grant the permission to replace.
System Action: Processing ends.
Subsystem ssid removed with permission.
Explanation: The subsystem ssid has been deleted.
System Action: Processing continues.
Subsystem ssid found and dynamic.
Explanation: The subsystem ssid was found and marked as being dynamic.
System Action: Processing continues.
Error in IEFSSI GET call rc:rc-rsnexplanation.
Explanation: The IEFSSI GET call returned an error.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Error in IEFSSI PUT call rc:rc-rsnexplanation.
Explanation: The IEFSSI PUT call returned an error.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Error in CMD Prefix DELETE call rc:rc-rsn - explanation.
Explanation: The CPF DELETE request returned an error.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Cannot deactivate — Tracker jobname active rc:rc rsn:rsn.
Explanation: There is an active TIBCO Mainframe Service Tracker instance with jobname on the same system LPAR.
User Response: Correct the subsystem SSID to ensure that it is unique within the same system LPAR.
System Action: Processing continues.
Explanation: This release of TIBCO Mainframe Service Tracker did not create the data structure connected to the subsystem definition structure and hence cannot delete that data structure.
System Action: Processing continues.
Error in IEFSSI ADD rc:rc-rsn - explanation.
Explanation: An error occurred in IEFSSI ADD for the subsystem.
User Response: Contact TIBCO Support.
System Action: The subsystem is not created.
Explanation: TIBCO Mainframe Service Tracker is running on the system sysid.
System Action: Processing continues.
cmp Quick leave.
Explanation: The component received a quick-leave command and is terminating without normal cleanup.
User Response: See the previous messages for the cause of quick-leave.
System Action: Termination continues.
Error getting common rc=rc, rsn=rsn - explanation.
Explanation: The IEFSSI GET request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Invalid modify msg Verb=verb,Qual=qual,Value=value.
Explanation: The console command for this component was invalid.
User Response: Correct and reenter the console command.
System Action: The command is not processed.
Job job overflowed monitor job list — rejected.
Explanation: TIBCO Mainframe Service Tracker did not add the job to be monitored to the Monitor table because the table was full.
User Response: Monitor fewer jobs with this instance of TIBCO Mainframe Service Tracker.
System Action: The job is not monitored.
Monitor job key job delete — entry not found.
Explanation: During the deletion of a job from the Monitor list, the job name was missing.
User Response: Contact TIBCO Support.
System Action: The deletion request is ignored.
Error in Command Prefix rc=rc, rsn=rsnexplanation.
Explanation: The Command Prefix call returned an error.
User Response: Contact TIBCO Support.
System Action: No command prefix is available.
cmp debug changed from db to db.
Explanation: The debug value has been changed.
System Action: Processing continues.
Explanation: The WTO debug value has been changed.
System Action: Processing continues.
Modify message verb qual value processed.
Explanation: The Modify message has been successfully processed.
System Action: Processing continues.
SS Count nnnnncount description.
Explanation: This message shows the number of calls to each of the subsystem functions.
System Action: Processing continues.
Create SSVT in ssid failed rc:rc:rsnexplanation.
Explanation: The IEFSSVT CREATE request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Exchange SSVT in ssid failed rc:rc:rsnexplanation.
Explanation: The IEFSSVT EXCHANGE request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Disable SSVT in ssid failed rc:rc:rsnexplanation.
Explanation: The IEFSSVT DISABLE request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Obtain for Subsystem ssid failed rc:rc.
Explanation: The STORAGE OBTAIN request for the common data area failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Put addr for Subsystem ssid failed rc:rc:rsnexplanation.
Explanation: The IEFSSI PUT request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Set option for Subsystem ssid failed rc:rc:rsn - explanation.
Explanation: The IEFSSI OPTIONS request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Activate Subsystem ssid failed rc:rc:rsnexplanation.
Explanation: The IEFSSI ACTIVATE request failed.
User Response: Contact TIBCO Support.
System Action: The subsystem is not activated.
Subsystem ssid activated.
Explanation: The subsystem is successfully activated.
System Action: Processing continues.
Explanation: The token returned by successful configuration of Program Call (PC) for TIBCO Mainframe Service Tracker usage does not exist, causing the product to skip the disconnect step during termination.
System Action: Processing continues.
Cmp Smart Client terminated.
Explanation: The Smart Client application has ended.
System Action: Processing of Smart Client ended.
Cmp quick leave.
Explanation: The Smart Client application has been instructed to terminate with no cleanup.
User Response: Review the log for the cause of the quick termination.
System Action: Processing ends.
Cmp activated Smart Client interface.
Explanation: The Smart Client application has started.
System Action: Processing continues.
Explanation: The request code passed to the Smart Client application is invalid.
User Response: Contact TIBCO Support.
System Action: This request is ignored.
Smart Client Modify request unknown: verb qual.
Explanation: An invalid Modify request was routed to Smart Client.
User Response: Correct and resubmit the Modify command.
System Action: Processing of this console message ends.
Table doing what: From modidmsgiderrmsg.
Explanation: An error occurred in the internal table handler. This is a display of the message from that handler.
User Response: Contact TIBCO Support.
System Action: Processing continues.
job st: status (expl) ASCB:ascb smfid:smfid Asid:asid. (xasid) sta strttime rc:rc Ab:abend end:endtime SMF:smfrec.
Explanation: This message is displayed in response to a SHOW TABLE ACTIVE command to SS, showing all the fields recorded for an active job.
System Action: Processing continues.
Job step for job asid has no Active job entry.
Explanation: An SMF step-end record has no matching Active job entry.
User Response: Contact TIBCO Support.
System Action: An entry is created for the active job.
Job job ascb term record recid has no Active entry.
Explanation: An SMF termination record has no matching Active job entry.
User Response: Contact TIBCO Support.
System Action: TIBCO Mainframe Service Tracker creates an entry for the terminated job.
Explanation: This is the heading displayed in response to a SHOW TABLE ACTIVE command.
System Action: Processing continues.
Explanation: This is the heading displayed in response to a SHOW JOBS MONITOR command.
System Action: Processing continues.
Length len Monitor job job as why.
Explanation: This is the message displayed in response to a SHOW TABLE MONITOR command, showing each job to be monitored, including the reason, such as Smart Client, Initial Load, or Job of Interest.
System Action: Processing continues.
Job term for job ascb found status stat.
Explanation: An SMF termination record found a status other than the Running in the Active table entry.
User Response: Contact TIBCO Support.
System Action: TIBCO Mainframe Service Tracker updates the entry with the current information.
Job step end for job ascb found completed job.
Explanation: An SMF step-end record found a completed status in the Active table entry.
User Response: Contact TIBCO Support.
System Action: TIBCO Mainframe Service Tracker updates the entry with the current information.
Explanation: An SMF record contains an invalid job name.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Table doing what: From tbl-proctbl-errerr_desc.
Explanation: The common table processor is reporting an error with the error message tbl-err and text err-desc.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Smart Client cmp terminate — no entry found.
Explanation: A client sent a logoff request for which no record exists.
User Response: Contact TIBCO Support.
System Action: Processing continues.
No ALET created, rc=rc from AKLESERV ADDexplanation.
Explanation: The ALESERV service failed with the specified return code. See the explanation.
User Response: Contact TIBCO Support.
System Action: Processing continues, but async notification does not function.
ALET not deleted, rc=rc from ALESERV DELETEexplanation.
Explanation: The ALESERV DELETE service failed with the specified return code. See the explanation
User Response: Contact TIBCO Support.
System Action: Processing continues.
Smart Client client request — no logon entry found.
Explanation: No entry existed for a Smart Client when it issued a request.
User Response: Change the Smart Client application to LOGON first.
System Action: Processing continues.
Smart Client client already logged on — using new data.
Explanation: During the processing of a LOGON request, an existing active entry was found. The new data now applies.
User Response: Review the Smart Client procedure for LOGON and LOGOFF processing.
System Action: Processing continues.
Smart Client XM Post response failed.
Explanation: XM Post for async data or data return failed.
User Response: Contact TIBCO Support.
System Action: Smart Client does not receive POST.
Client client already interest in job.
Explanation: Interest in job has already been registered by client.
User Response: Review the logic in Smart Client.
System Action: Processing continues.
Client clientascb terminated without logoff.
Explanation: A Smart Client terminated without first issuing a LOGOFF request.
User Response: Review the logic in Smart Client.
System Action: Processing continues with logical LOGOFF processed.
Explanation: This message is displayed in response to SHOW,TABLE,CLIENT.
System Action: Processing continues.
Explanation: This message is displayed in response to SHOW,TABLE,JOB.
System Action: Processing continues.
Job jobname interest by Smart Client client ascb.
Explanation: This message is displayed in response to SHOW,TABLE,CLIENT.
System Action: Processing continues.
Smart Client client ascb ECB:addr Data Len len at addr.
Explanation: This message is displayed in response to SHOW,TABLE,JOB.
System Action: Processing continues.
Status SEND failed rc rc.
Explanation: An internal status message SEND failed with return code rc.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Component cmp field field name has invalid value num.
Explanation: The field field name in the component cmp has an invalid value.
User Response: Update and resubmit the parmlib member.
System Action: Processing ends.
Component cmp field field name has invalid value num.
Explanation: The field field name in the component cmp has an invalid value.
User Response: Update and resubmit the parmlib member.
System Action: Processing ends.
Component cmp missing value for field field name.
Explanation: The field field name in the component cmp has no value.
User Response: Update and resubmit the parmlib member.
System Action: Processing ends.
Subtask cmp initialization failed.
Explanation: A call to task messaging during startup failed.
User Response: Review the log for the cause of the failure.
System Action: Processing for the component ends.
Hawk cntl task terminated normally.
Explanation: The TIBCO Hawk control task has terminated without serious errors.
System Action: Processing is in the act of terminating.
Hawk ami error in 'where': error rc=rc in ami-loc line ami line.
Explanation: This message describes any error that occurs in the AMI interface.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Hawk ami ERROR ami_rc ami-error.
Explanation: This message echoes an AMI error notification, including the return code and description.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Hawk ami WARN ami_rc ami-error.
Explanation: The message echoes an AMI warning notification, including the return code and description.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Explanation: The TIBCO Hawk session has terminated.
System Action: Processing continues.
Explanation: An internal communications error has occurred.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Explanation: An internal communications error has occurred.
User Response: Contact TIBCO Support.
System Action: Processing ends.
Hawk RV parms: daemon:daemon, service:service, network:network.
Explanation: This message shows the three connection parameters that connect TIBBCO Hawk processing to a TIBBCO Hawk server.
System Action: Processing continues.
Hawk session start rc rc, Name name1, Friendly:name2 Help:help.
Explanation: This message shows the TIBBCO Hawk session name, the friendly session name, and the help description for the session.
System Action: Processing continues.
Invalid modify verb verb for cmp.
Explanation: TIBCO Mainframe Service Tracker does not support the modify command directed to this component.
User Response: Revise the modify command.
System Action: The modify command is rejected.
Alert id alert id (type alert type code) request transmission: message id.
Explanation: A user requested that TIBCO Mainframe Service Tracker transmit an alert to TIBCO Hawk.
System Action: Processing continues.
Explanation: The TIBCO Hawk close request has completed normally.
System Action: Processing continues.
Hawk modify message verb qualifier processed.
Explanation: The modify message has been successfully processed.
System Action: Processing continues.
Explanation: A Full Alert with no subscription was received.
User Response: Subscribe to the Full Alert.
System Action: Processing continues.
Invalid request reqst to Hsub.
Explanation: An invalid request was made to the TIBCO Hawk support routine.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Hawk task cmp initialization failed.
Explanation: A call to task messaging during startup failed.
User Response: Review the log for the cause of the failure.
System Action: Processing for the component ends.
Hawk ami error in where: error rc=rc in ami-mod line ami-line.
Explanation: This message describes any error that occurs in the AMI interface.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Hawk Interface session name activated.
Explanation: A TIBCO Hawk session has been established.
System Action: Processing continues.
Hawk Job Table error rc=rc doing where.
Explanation: An error occurred during the access of the active-jobs table.
User Response: Contact TIBCO Support.
System Action: Processing continues.
Hawk Interface session name stopped.
Explanation: The TIBCO Hawk session has ended.
System Action: Termination continues.
Explanation: The Rendezvous connection has ended.
System Action: Termination continues.
Error in SSREQ rc=rc = explanation.
Explanation: The SSI call to return the exit addresses returned an error.
User Response: Contact TIBCO Support.
System Action: SMF exits are not loaded.
Error Dyn Add of exit rc=rc, rsn=rsnexplanation.
Explanation: The dynamic add of exit failed. See the explanation.
User Response: Contact TIBCO Support.
System Action: SMF exit is not loaded.
Error Dyn Delete of exit rc=rc,rsn=rsnexplanation.
Explanation: The dynamic delete of exit failed. See the explanation.
User Response: Contact TIBCO Support.
System Action: SMF exit continues to be active.
Dynamic Delete for exit OK.
Explanation: The SMF exit was successfully deleted.
System Action: Processing continues.
Dynamic Add for exit OK.
Explanation: The SMF exit was successfully added.
System Action: Processing continues.
SMF exit exit already active — will delete.
Explanation: The SMF exit is already active and will be deleted.
System Action: Processing continues.
Previous SMF exit exit deleted.
Explanation: The old SMF exit has been deleted.
System Action: Processing continues.
Dynamic Delete of duplicate exit rc=rcexplanation.
Explanation: The preexisting SMF exit could not be deleted.
User Response: Contact TIBCO Support.
System Action: SMF exit is not loaded.
Cannot delete exit name — did not load it rc:rc rsn:rsn.
Explanation: TIBCO Mainframe Service Tracker cannot delete the named exit because it was not loaded by this process during initialization.
System Action: Processing continues.
Invalid Related=related in Component.
Explanation: The Related value in the receiving component is not valid for this application.
User Response: Contact TIBCO Support.
System Action: The component and system are terminated.
Invalid Ident=ident in Component.
Explanation: The Identity field in the receiving component is not valid for this application.
User Response: Contact TIBCO Support.
System Action: The component and system are terminated.
Pthread_create for cmp-ep failed with rc - reason.
Explanation: The pthread_create for this entry point failed with return code rc, interpreted as reason.
User Response: Contact TIBCO Support.
System Action: The system ends.
Pthread_join for cmp-ep failed with rc - reason.
Explanation: The pthread_join for this thread failed with return code rc, interpreted as reason.
User Response: Contact TIBCO Support.
System Action: The system ends.

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