System Messages
TIBCO EMS Client for z/OS (CICS) can produce system messages.
| Code | Description |
|---|---|
| S7M1000I | S7M1000I
hh:mm:ss.mmmm - Date
MM/DD/YY
Explanation: This message indicates that the date has changed. Destination: CEET log. |
| S7M1001I | Connection Thread
address Ended
Explanation: When a Connection Thread ends, all Work Threads started by the Connection Thread also end. Destination: CEET log. |
| S7M1002I | cleanup_asmem POINT
n
Explanation: This message indicates points 1 through 10 in the cleanup process. Destination: CEET log. |
| S7M1100I | ACMEM Invalid Start ignored
Explanation: The ACMEM address passed to the Master to start a Connection Thread is invalid. Destination: CEET log. |
| S7M1101E | Could not find open Connection ASMEM Control Block
Explanation: This message indicates that the Master received start command for a connection but could not find any open connection ASMEM control blocks—the system has 16 and all are in use. User Response: Verify the number of Connection Threads that are running by using transaction S7MA. Stop Connection Threads that are no longer needed and retry transaction. Remember — when stopping a Connection Thread, all Work Threads associated with the Connection Thread terminate. System Action: The Work Thread is not started. The rest of the interface continues. Destination: CEET log. |
| S7M1102E | Invalid ACMEM pointer
Explanation: Routine entered to test for valid ACMEM control block—the address is zero. User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Master and Connection Threads. For Work Threads, the thread terminates. Destination: CEET log. |
| S7M1103E | Invalid ACSTART pointer
Explanation: Routine entered to test for valid ACMEM control block—the header ID is invalid. User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Master and Connection Threads. For Work Threads, the thread terminates. Destination: CEET log. |
| S7M1104E | Invalid ACIDE pointer
Explanation: Routine entered to test for valid ACMEM control block—the trailer ID is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Master and Connection Threads. For Work Threads, the thread terminates. Destination: CEET log. |
| S7M1200I | before Post of CICS transaction
Explanation: The trace point in Master before issuing Post. Destination: CEET log. |
| S7M1210I | before Master Wait
Explanation: The trace point in Master before Wait. Destination: CEET log. |
| S7M1301S | Missing AMMEM pointer at startup
Explanation: The parameter passed to S7M3EMSS which is to be the AMMEM address is missing or invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Master Thread terminates. Destination: CEET log. |
| S7M1451E | S7M_SUBTASK_STOP—CANNOT Find URL
Explanation: The CEET received a stop command for a Connection Thread but the URL given does not match any running Connection Threads. User Response: Must check the URL ID of the Connection Thread you want to terminate and make sure you specify the URL exactly (case sensitive). System Action: Ignore command to stop Connection Thread. Destination: CEET log. |
| S7M1452I | S7M_SUBTASK_STOPAS—CANNOT Find AS
Explanation: A master received a stop command for a Connection Thread but the ASMEM address given does not match any running Connection Threads. User Response: Must check the ASMEM address of the Connection Thread you want to terminate. System Action: Ignore command to stop Connection Thread. Destination: CEET log. |
| S7M1470E | Invalid ASMEM pointer
Explanation: Routine entered to test for valid ASMEM control block—the address is zero. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: Master ignores command. Destination: CEET log. |
| S7M1471E | Invalid ASSTART pointer
Explanation: Routine entered to test for valid ASMEM control block—the header ID is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: Master ignores command. Destination: CEET log. |
| S7M1472E | Invalid ASIDE pointer
Explanation: Routine entered to test for valid ASMEM control block—the trailer ID is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: Master ignores command. Destination: CEET log. |
| S7M1482S | Invalid AMMEM pointer
Explanation: Routine entered to test for valid AMMEM control block—the address is zero. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: Master Thread terminates. Destination: CEET log. |
| S7M1483S | Invalid AMSTART pointer
Explanation: Routine entered to test for valid AMMEM control block—the header ID is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: Master Thread terminates. Destination: CEET log. |
| S7M1484S | Invalid AMIDE pointer
Explanation: The Master Thread could not find a match in its Command Table— command was not found in command list. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Command is ignored and a return code of 8 is passed back to the User. Destination: CEET log. |
| S7M1492E | Command Not Found:
command
Explanation: The Master Thread could not find a match in its Command Table— command was not found in command list. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Command is ignored and a return code of 8 is passed back to the User. Destination: CEET log. |
| S7M1500I | Master Started AM:addr, AMS:addr EMS Ver:number Build:
timestamp
Explanation: This message is issued when the CEET (S7M3EMSS) is started. Parameters passed to S7M3EMSS are shown for reference purposes where AM is the control block in the CICS Application Environment and AMS is the control block for the Master Thread in the CEET. Also shows the current version of the EMS Client and the build time stamp (in the format Month Day Year and Time). Destination: CEET log. |
| S7M1501I | Master Thread Ended
Explanation: This message indicates that the CEET is terminating—all Connection Threads and Work Threads end. Destination: CEET log. |
| S7M1502I | time Maximum Connections:num Maximum Workers:num
Explanation: Message issued by CEET at startup to record maximum number of Connection and Worker Threads. Destination: CEET log. |
| S7M1503I | time HostCodePage:hostcodepage, NetworkCodePage:networkcodepage
Explanation: Message issued by CEET at startup to record code pages being used. Destination: CEET log. |
| S7M1504I | time Error:number, HostCodePage:hostcodepage,
NetworkCodePage:networkcodepage Explanation: Message issued by CEET at startup to indicate an error was returned from tibems_SetCodePages. The error number is the returned tibstatus. Error:74 means that one of the code pages specified is invalid. User Response: Correct the code page parameter in S7MACURT or on the S7MA –MASTERSTART command and restart the CEET. System Action: CEET terminates. Destination: CEET log. |
| S7M1900I | Function:
routine Entered
Explanation: The Master Thread entered function routine. Destination: CEET log. |
| S7M1901I | Function:
routine Exited
Explanation: The Master Thread exited function routine. Destination: CEET log. |
| S7M1999I | time Master shutdown -
number Connections Active
Explanation: This message issued at Master Thread shutdown indicates how many Connection Threads are still active. Destination: CEET log. |
| S7M2011I | work_cleanup_asmem POINT
n
Explanation: This message indicates the Work Thread cleanup program has entered trace point n in the cleanup function. Destination: CEET log. |
| S7M2013E | CONN ASMEM Invalid Start ignored
Explanation: This message indicates the Connection Thread has found an invalid Connection ASMEM pointer—the start indicator is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2014E | CONN ACMEM Invalid Start ignored
Explanation: This message indicates the Connection Thread has found an invalid Connection ACMEM pointer—the start indicator is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2020I | before Post of CICS client ecb
Explanation: This message indicates the Connection Thread is at the point just before posting the CICS transaction. Destination: CEET log. |
| S7M2022I | before wait of Connection Thread
Explanation: This message indicates the Connection Thread is at the point just before waiting for the next command. Destination: CEET log. |
| S7M2099E | time Error opening tibemsConnection
url, EMS Status:
EMS status code
Explanation: When a Connection Thread starts, it issues a tibemsConnection_Create for the URL it was started on. If that connection create fails, this message is issued. User Response: Analyze the EMS status return code and determine why the connection cannot be made. Correct the problem and retry the transaction that started the Connection Thread. System Action: The Connection Thread is terminated. |
| S7M2101I | CONN ASMEMPTR = address
Explanation: This message indicates the Connection Thread address of the ASMEM upon start of the program. Destination: CEET log. |
| S7M2201E | Work Task Monitor (join) for
address Ended rc =
RC
Explanation: This message indicates that a Work Thread monitor could not join to the Work Thread for ASMEM address. The return code from the thread_join was RC. User Response: The Work Thread must be restarted. System Action: The Work Thread terminates. Destination: CEET log. |
| S7M2210I | Work Thread Create—RC =
RC
Explanation: This message indicates the Connection Thread has entered the thread create routine and issued a thread create—RC is the return code. Destination: CEET log. |
| S7M2211I | Work Watch Create—RC =
RC
Explanation: This message indicates the Connection Thread has entered the thread create routine and issued a thread create to monitor the previously created Work Thread—RC is the return code. Destination: CEET log. |
| S7M2222E | Command Not Found:
command
Explanation: This message indicates the Connection Thread has not found the command sent in the command list. User Response: Check the syntax of the command sent to the Connection Thread. System Action: The command is ignored. Destination: CEET log. |
| S7M2223I | Cmd Address:
address
Explanation: This message indicates the Connection Thread has not found the command sent in the command list—address. Destination: CEET log. |
| S7M2224E | BAD S7M_SUBTASK_PING—Ping Received
Explanation: This message indicates the Connection Thread received a Ping command from the CICS Application Environment with a bad control block address. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2225E | BAD S7M_SUBTASK_DBGF—Debug OFF Received
Explanation: This message indicates the Connection Thread received a trace off command from CICS for all Connection Threads with invalid ACMEM address. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2226E | BAD S7M_SUBTASK_STOP—STOP Received
Explanation: This message indicates the Connection Thread received an end command from the CICS client with a bad ACMEM address parameter. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2228E | Could not find open WORK ASMEM
Explanation: This message indicates the Connection Thread has entered the thread create routine but could not find an open ASMEM to use (128 permitted). User Response: Check to see how many Work Threads are running by issuing a S7MA CICS Transaction—the system maximum is 128 Work Threads. System Action: The command is ignored for Work Thread. Destination: CEET log. |
| S7M2229E | BAD S7M_SUBTASK_START—START Received
Explanation: This message indicates the Connection Thread received a start command from the CICS Application Environment with a bad control block address. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2230E | Invalid AMMEM pointer
Explanation: This message indicates the Connection Thread has found an invalid AMMEM pointer—the address is 0. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2231E | Invalid AMSTART pointer
Explanation: This message indicates the Connection Thread has found an invalid AMMEM pointer—the start indicator is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2237E | Work Thread
WThd not found on Conn thread
CThd
Explanation: This message indicates the Connection Thread received a stop Work Thread command from the CICS Application Environment but the ASMEM WThd was not on the Connection Thread for ASMEM CThd. User Response: Check that the Command to stop the Work Thread is on the Connection Thread Chain. Only the Connection Thread that started the Work Thread can stop it. System Action: The command is ignored for Connection Threads. Destination: CEET log. |
| S7M2237I | BAD S7M_SUBTASK_DBGO—Debug ON Received
Explanation: This message indicates the Connection Thread received a trace on command from the CICS Application Environment for all Connection Threads with invalid control block address. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored. Destination: CEET log. |
| S7M2238E | Work Thread parm not present
Explanation: This message indicates the Connection Thread received a stop Work Thread command from the CICS Application Environment with an invalid control block address. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored. Destination: CEET log. |
| S7M2239E | Work Thread
thead id not found on Connection Thread
Conn thead id
Explanation: A stop Work Thread thead ID command was sent to a Connection Thread Conn thead ID and the Connection Thread could not find the Work Thread on its list of threads it has started. User Response: Use S7MA to see if the Work Thread is still active (it might have terminated before the command was processed). Use S7MA to determine which Connection Thread controls the Work Thread. Issue a S7MA –workstop or S7MA –connstop for terminating the Work Thread. System Action: The stop Work Thread command is ignored. Destination: CEET log. |
| S7M2240E | Invalid AMIDE pointer
Explanation: This message indicates the Connection Thread has found an invalid AMMEM pointer—the end indicator is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2250I | WORK ASMEM
address—ACMEM
address
Explanation: This message indicates the addresses of the ASMEM and ACMEM control blocks, just before going to Work Thread main program. Destination: CEET log. |
| S7M2310I | Connection Thread Started for URL
urlid
Explanation: This message indicates the Connection Thread is at the start point. Destination: CEET log. |
| S7M2311I | Connection Thread #
id Ended for URL
url
Explanation: When a Connection Thread is ending, this message is issued. User Response: None. System Action: The EMS Connection Thread is terminated. |
| S7M2810E | CONN ASMEM Invalid Start ignored.
Explanation: This message indicates the Connection Thread has detected an Invalid ASMEM for the Connection Thread during processing of the Work Start Command. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2811E | CONN ACMEM Invalid Start ignored
Explanation: This message indicates the Connection Thread has detected an Invalid ACMEM for the Connection Thread during processing of the Work Start Command. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Connection Threads. The Connection Thread and all its Work Threads terminate. Destination: CEET log. |
| S7M2812E | WORK ACMEM Invalid Start ignored
Explanation: This message indicates the Connection Thread has detected an Invalid Work ACMEM during processing of the Work Start Command. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The command is ignored for Work Thread. The Work Thread terminates. Destination: CEET log. |
| S7M2999I | time Connection shutdown –
number Work Threads Active
Explanation: This message issued at Connection Thread shutdown indicates how many Work Threads are still active. Destination: CEET log. |
| S7M3010I | time WORK Thread #
id Started AC:acmem, AS:asmem, PT:
thread id
Explanation: When a Work Thread is started, this message is issued. acmem is the address of the ACMEM control block for this thread. asmem is the address of the ASMEM control block for this thread. thread id is the thread ID of this Work Thread. User Response: None. System Action: The EMS Work Thread is started. |
| S7M3014E | WORK Thread #
thead id tibemsErrorContext_Create EMS status:
status
Explanation: The Work Thread issued an EMS API call for tibemsErrorContext_Create and EMS returned a nonzero status code. The tibemsErrorContext_GetLastErrorStackTrace and the tibemsErrorContext_GetLastErrorString EMS API calls do not work on this specific Work Thread since the Context Object ID is not available. User Response: Determine why EMS issued the non-zero status by looking up status in the EMS documentation. Correct the problem, then stop and start the Work Thread. System Action: The Work Thread continues to run without ErrorContext functions. Destination: CEET log. |
| S7M3030I | time WORK Thread #
id Ended AC:acmem, AS:asmem
Explanation: When a Work Thread is ending, this message is issued. acmem is the address of the ACMEM control block for this thread. asmem is the address of the ASMEM control block for this thread. User Response: None. System Action: The EMS Work Thread is terminated. |
| S7M3100I | Work Thread Started
Explanation: This message indicates the Work Thread is at the start point. Destination: CEET log. |
| S7M3101I | Initial ACMEM OK
Explanation: This message indicates the Work Thread is at the start point and has a valid ACMEM pointer. Destination: CEET log. |
| S7M3110I | Condition Handler Registration OK
Explanation: This message indicates the Work Thread is at the start point and sets a Condition Handler. Destination: CEET log. |
| S7M3200E | Condition Handler Registration Failed
Explanation: This message indicates the Work Thread is at the start point and could not set a Condition Handler. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread continues to run without a Condition Handler—any S0C(x) condition (abend) terminates the CEET—Master Thread, All Connection Threads, and All Work Threads. Destination: CEET log. |
| S7M3300I | Processing LOOP Entered
Explanation: This message indicates the Work Thread is at the main process point. Destination: CEET log. |
| S7M3400I | Processing START Function
Explanation: This message indicates the Work Thread received a start function. Destination: CEET log. |
| S7M3401I | Processing PING Function
Explanation: This message indicates the Work Thread received a ping function. Destination: CEET log. |
| S7M3404I | Processing Debug Off
Explanation: This message indicates the Work Thread should turn off the trace and debug feature. Destination: CEET log. |
| S7M3405I | Processing Debug On
Explanation: This message indicates the Work Thread should turn on the trace and debug feature. Destination: CEET log. |
| S7M3500I | Processing WTO Function
Explanation: This message indicates the Work Thread received a WTO function command. Destination: CEET log. |
| S7M3501I | Beginning Command Table Search
Explanation: This message indicates the Work Thread received a command—it is searching command table for match. Destination: CEET log. |
| S7M3550E | Function Found—Zero Address
Explanation: This message indicates the Work Thread found match for command in search table but the address of the routine to process command was missing. User Response: Function is not available—try using a different EMS function. System Action: The Work Thread ignores command and sets return code to 1016. Destination: CEET log. |
| S7M3561E | Function Not Found: command
Explanation: This message indicates the Work Thread did not find the command in the search table. User Response: The EMS API call is invalid, correct the user program. System Action: The Work Thread ignores command and sets return code to 1016. Destination: CEET log. |
| S7M3570I | Command Ignored
Explanation: This message indicates the Work Thread that the previous command was ignored. Destination: CEET log. |
| S7M3750I | EXC:
function
Explanation: This message indicates the Work Thread command the program is going to call. Destination: CEET log. |
| S7M3810E | Invalid Work Thread AS, Cannot check open EMS Connections
User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread ends and a return code is passed back to the user. Destination: CEET log. |
| S7M3900I | Client Wait Entered
Explanation: This message indicates the Work Thread is entering the post/wait routine. Destination: CEET log. |
| S7M3901I | Before WAIT for CICS Client
Explanation: This message indicates the Work Thread is just before wait routine. Destination: CEET log. |
| S7M3902I | After Wait
Explanation: This message indicates the Work Thread is just after wait routine. Destination: CEET log. |
| S7M3910I | Set Return Code to Zero
Explanation: This message indicates the Work Thread is setting zero (0) return code. Destination: CEET log. |
| S7M3920I | Set Return Code to
1004
Explanation: This trace message indicates the Work Thread is setting 1004 return code. The trace entry is preceded by message S7M3570I. This is passed back to the User Program as the Tibco_status. Destination: CEET log. |
| S7M3930I | Set Return Code to
1008
Explanation: This message indicates the Work Thread is setting 1008 return code. The return code is 1008. This is passed back to the User Program as the Tibco_status. Destination: CEET log. |
| S7M3940I | Set Return Code to
1016
Explanation: This message indicates the Work Thread is setting 1016 return code. The trace entry is preceded by either message S7M3550E or S7M3561E. This is passed back to the User Program as the Tibco_status. Destination: CEET log. |
| S7M3960E | Bad ACMEM - ACSTART
Explanation: This message indicates the Work Thread found an invalid ACMEM control block in the CICS Application Environment—the beginning of the control block as an ID that is missing. This is a major problem indicating that the Control Block has been corrupted. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread ends and a return code is passed back to the user. Destination: CEET log. |
| S7M3961E | Bad ACMEM - ACIDE
Explanation: This message indicates the Work Thread found an invalid ACMEM control block in the CICS Application Environment—the end of the control block as an ID that is missing. This is a major problem indicating that the Control Block has been corrupted. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread ends and a return code is passed back to the user. Destination: CEET log. |
| S7M3962E | Bad ASMEM - ASSTART
Explanation: This message indicates the Work Thread found an invalid ASMEM control block in the CEET—the beginning of the control block as an ID that is missing. This is a major problem indicating that the Control Block has been corrupted. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread ends and a return code is passed back to the user. Destination: CEET log. |
| S7M3963E | Bad ASMEM—ASIDE
Explanation: This message indicates the Work Thread found an invalid ASMEM control block in the CEET—the end of the control block as an ID that is missing. This is a major problem indicating that the Control Block has been corrupted. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread ends and a return code is passed back to the user. Destination: CEET log. |
| S7M3999I | Work Thread Exit
Explanation: This message indicates the Work Thread returning to the operating system. Destination: CEET log. |
| S7M4900I | S7M3COND Entered #
number
Explanation: This message indicates that a Work Thread Condition (ABEND) has occurred and the Condition Handler has been entered. This number is a count of Conditions (ABENDs). Destination: CEET log. |
| S7M4902I | token =
token S0Cx Abend
Explanation: This message indicates information given to the Condition Handler routine—The current condition token. Destination: CEET log. |
| S7M4908E | Invalid ACMEM
Explanation: This message indicates the CICS Application Environment control block or its pointer is invalid. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: The Work Thread continues to terminate. Destination: CEET log. |
| S7M4910I | Func: S7M3COND Exited Error #:Num
Explanation: This message indicates a return to the LE environment from the Condition Handler. Destination: CEET log. |
| S7M5000E | eibfn:0402 - eibresp:4, eibresp2:0
Explanation: An error occurred in S7MA on issuing a CICS command—this is the function number and response codes. User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG. System Action: This is information about the status of the CICS transaction displayed on terminal screen. |