Transaction Messages

TIBCO EMS Client for z/OS (CICS) can produce CICS transactional messages.

The following table shows the details of the transaction messages.
Codes Description Explanation
S7M5100I

(time description)

Cannot Find Task ID Explanation: User issued a S7MA –connstop. The system did not find a matching –id, -addr or – url system.

User Response: Issue S7MA to display active interfaces; verify command parameters and reissue correct command.

System Action: The command is ignored.

CICS EMS Master Not Running - No TS Pointer Explanation: The CEET is not active.

User Response: This is information about the status of the CEET. To change that status see S7MA –masterstart.

System Action: The command is ignored.

CICS EMS Task Stopped Explanation: The CEET is not active. A S7MA –masterstop was issued. No new Connection Thread or Work Threads is started until a S7MA –masterstart is issued. A return code of 1044 is passed back to all EMS API calls that require a new Work Thread.

User Response: This is information about the status of the CEET. To change that status, see S7MA –masterstart

System Action: The command is ignored.

URL:urlname in CICS EMS Task cannot be reached Explanation: Means that there is no Connection Thread for the specified URL or the Connection Thread is not working properly.

User Response: This is information about the status of the CEET. Use S7MA to see status of all running threads.

System Action: The command is ignored.

S7M3ADM - Unknown parameter:parm Explanation: An unsupported S7MA sub-command had entered.

User Response: Review and correct the command and submit again.

System Action: The command is ignored.

S7M5100E

(time description)

Cannot Find Connection Thread for Work Thread id Explanation: User issued a S7MA –connstop. The system did not find a matching –id, -addr or – url item.

User Response: issue S7MA to display active interfaces; verify command parameters and reissue corrected command.

System Action: The command is ignored.

CICS EMS Task Stopped Explanation: Before issuing this command, user issued a S7MA -masterstop and the CEET interface is not running.

User Response: None.

System Action: The command is ignored.

EMS Task CB has terminated with Code Explanation: When starting the CICS EMS master program, the program terminated with the following Code Posted to the Task ECB. The Task ECB Post is from MVS and indicates why the program was terminated. The CEET interface is not running.

User Response: Contact TIBCO Support and provide system logs, CICS dumps, and Auxtrace.

System Action: The command is ignored. The CEET interface is not running.

EMS Task CB has terminated with Code Explanation: When starting the CICS EMS master program, the major control blocks (AM) were corrupted. The CEET interface is not running.

User Response: Issue a S7MA -masterstop to cleanup internal control blocks. Issue a S7MA -masterstart to restart the CEET. If failure persists, contact TIBCO Support and provide system logs, CICS dumps, and Auxtrace.

System Action: The command is ignored. The CEET interface is not running.

Invalid CONN ASMEM Thread Pointer Explanation: If user issued a S7MA -masterstop, this might be a timing situation. The system is stopping the interface while being monitored.

User Response: Issue S7MA to display interfaces status.

System Action: The command stops the CEET interface.

S7M5200I

(time description)

CICS EMS Master, Connection and Work Threads Stopped Explanation: User issued a S7MA -masterstop. All threads are stopped and none is started until a S7MA –masterstart is issued.

User Response: None.

System Action: The CEET interface is terminated.

Connection PING Issued Return Code = 0 Explanation: The Connection Thread is sent a PING command and the return code is displayed. Return code of zero (0) indicates everything is working correctly. A response of:

URL: urlName in CICS EMS Task cannot be reached

means there is no Connection Thread for the specified URL or the Connection Thread is not working properly.

User Response: This is information about the status of the Connection Thread in response to, for example:

S7MA –connping –url urlName

System Action: None.

Connection Started Error, EMS Status = number Explanation: User issued a S7MA –connstart. When trying to start an EMS connection, an error was issued from the EMS library. Check the EMS library status codes for reason. The Connection Thread terminated and is not available.

User Response: Lookup EMS status return code to determine why the connection could not be made. Correct situation and reissue command.

System Action: The Connection Thread terminated.

Connection Thread Started Explanation: The Connection Thread is now started, for example:

S7MA –CONNSTART –URL urlName

User Response: This is information about the status of the Connection Thread. To change that status, see S7MA -connstop.

System Action: The Connection Thread started.

Connection Thread and All Work Threads Stopped Explanation: The Connection Thread and all its Work Threads have stopped, for example:

S7MA –connstop {–url urlName} |{–id id}

User Response: This is information about the status of the Connection Thread. To change that status, see S7MA –connstart.

System Action: The Connection Thread and All Work Threads stopped.

Num Control Blocks Printed Explanation: The list of active threads is listed to DDNAME CEEOUT. The output is similar to the S7MA display command. It indicates how many control blocks were printed.

User Response: This is information about the status of the threads as a response to: S7MA –print

System Action: Printed CEET status to DDNAME CEEOUT.

number TCBs looked at - POSIX (ON) found Explanation: Routine looked at all attached TCBs in the CICS address space and found a TCB with the POSIX (ON) runtime option. Related information sent to screen and JES output.

User Response: None.

System Action: Display and print information on POSIX use in the CICS region.

number TCBs looked at - POSIX (ON) NOT found Explanation: Routine looked at all attached TCBs in the CICS address space and did not find a TCB with the POSIX (ON) runtime option.

User Response: None.

System Action: Display and print information on POSIX use in the CICS region.

Master Already Running Explanation: User issued a S7MA –masterstart, but the CEET was already running.

User Response: None.

System Action: The command is ignored.

Master Thread Started Explanation: The CEET is now started:

S7MA –masterstart

User Response: This is information about the status of the CEET. To change that status, see S7MA –masterstop.

System Action: The CEET started.

Master Trace On Explanation: This command turns on the trace feature on the Master Thread, all Connection Threads, and all Work Threads.

User Response: This is information about the status of all threads as a response to:

S7MA –mastertrace –on

System Action: All threads produce trace messages to the CEET log.

Master Trace Off Explanation: This command turns off the trace feature on the Master Thread, all Connection Threads, and all Work Threads.

User Response: This is information about the status of all threads as a response to:

S7MA –mastertrace –off

System Action: System no longer issues trace messages to the CEET log.

Work Started Error, EMS Status = number Explanation: User issued a S7MA –workstart. When trying to start the EMS connection, an error was issued from the EMS library. Check the EMS library status return codes for reason. The Work Thread terminated and is not available.

User Response: Lookup EMS status return code to determine why the connection could not be made. Correct situation and reissue command.

System Action: The Work Thread is not started.

Work Thread Started Explanation: The Work Thread is now started, for example:

S7MA –workstart –url urlName

User Response: This is information about the status of the Work Thread. To change that status, see S7MA –workstop.

System Action: The Work Thread started.

Work Thread: Terminated Explanation: The Work Thread is now terminated, for example:

S7MA –workstop –addr address

User Response: This is information about the status of the Work Thread. To change that status, see S7MA -workstart.

System Action: The Work Thread terminated.

S7M5300E

(time description)

Cannot Find Task ID Explanation: User issued a S7MA –connstop. The system did not find a matching –id, -addr or – url system.

User Response: Issue S7MA to display active interfaces; verify command parameters and reissue corrected command.

System Action: The command is ignored.

URL: url in CICS EMS Task cannot be reached Explanation: User issued a S7MA -connping. The system did not find a matching URL.

User Response: Issue S7MA to display active interfaces; verify command parameters and reissue corrected command.

System Action: The command is ignored.

S7M5400I

(time description)

S7MA 
S7M5400I 09:20:31 Total Thds:5 Mast Thds:1 Conn Thds:2 Work Thds:2
ID CB ADDRESS TYPE TASKID STATE URL OR LAST COMMAND
AM 000C2000 MAST CMD S7M_SUBTASK_START
0002 AC 000C2640 WORK 0000085 tibemsDestination_Destroy
0002 AS 1CB58068 WORK CMD C002 16543
C002 AC 000C2460 CONN S7M_WORK_START
C002 AS 1CB713A0 CONN CMD tcp://url-id1:7222
0001 AC 000C2280 WORK 0000074 tibemsMsgConsumer_Receive
0001 AS 1CB57E20 WORK WAIT C001 8123
C001 AC 000C20A0 CONN S7M_WORK_START
C001 AS 1CB71158 CONN CMD tcp://url-id2:7222

Explanation: This is a display of all running threads by issuing a “S7MA” with no sub-options. The user can use the PF7 and PF8 key to backward and forward page through the list.

User Response: None.

System Action: Information displayed on terminal screen.

S7M5401I time EMS Ver: number Build: timestamp

Max Connections: number Max Workers: number

IO: number Mic: number Ave: number Wait: number

Explanation: This is a display of the version and build time stamp (in the format Month Day Year and Time) of the EMS Client currently running. Also shows the Maximum number of Connection and Worker Threads. The IO number is the total number of calls to the CEET, Mic is the total wait time for a CEET call in microseconds, Ave is the average, and Wait is the number of calls that had to issue a CICS WAIT.

User Response: None.

System Action: Information displayed on terminal screen.

S7M5902I token = condition event token S0Cx Abend Explanation: A critical error condition occurred in a Work Thread causing an ABEND. The condition event token is provided by the Language Environment. A CEEDUMP is taken and the Work Thread is terminated.

User Response: Analyze the last EMS API call to this Work thread and check address pointers of parameters passed to the EMS library; the dump will help with this. Correct problem and retry the transaction.

System Action: The Work Thread is terminated.

S7M6200S EXEC CICS WRITEQ TS for Master Pointer - CICS Resp1: response 1 Resp2: response 2 Explanation: A CICS Application Environment Anchor Pointer TS record with pointers to critical data could not be written. S7M3PASS issued a “EXEC CICS WRITEQ TS ” and did not receive a “NORMAL” response. response 1 and response 2 are the CICS response codes for a EXEC CICS WRITEQ TS.

User Response: Analyze the CICS response codes, correct problem and retry transaction.

System Action: The transaction is abended with S7M4 and the CEET environment is not setup.

Destination: DDNAME CEEOUT.

S7M6201S EXEC CICS ENABLE PROGRAM(S7MATRUE) - CICS Resp1: response 1 Resp2: response 2 Explanation: The Enable for the S7MATRUE (TRUE) program failed. On the first call to the CEET after module S7M3EMSS is attached, the routine issues an ENABLE PROGRAM for S7MATRUE. If this command fails, the abend is issued.

The system issues the following information:

EXEC CICS ENABLE PROGRAM('S7MATRUE'),START,

TALENGTH(TRUEWAL),TASKSTART

Without this program properly enabled, the CEET cannot cleanup transaction terminations that use EMS API calls. response 1 and response 2 are the CICS response codes for the preceding statement.

User Response: Analyze the CICS response codes, correct problem and retry transaction.

System Action: The transaction is abended with either S7ME or S7MF and the CEET environment is not setup.

Destination: DDNAME CEEOUT.

S7M6203S EXEC CICS ADDRESS - CICS Resp1: response 1 Resp2: response 2 Explanation: S7M3PASS issued a “EXEC CICS ADDRESS ” and did not receive a “NORMAL” response. This CICS API is critical to CEET organization. response 1 and response 2 are the CICS response codes.

User Response: Analyze the CICS response codes, correct problem and retry transaction.

System Action: The CICS transaction is terminated with a S7M1 abend.

Destination: DDNAME CEEOUT.

S7M6204S No CommArea or CommArea too small Explanation: For all LINKS to S7M3PASS, a CICS COMMAREA of at least 76 characters is required. A COMMAREA of at least 76 characters was not provided. This area is critical for communications. A S7M3 abend is issued since there is no other way to indicate the problem.

User Response: If the user is accessing S7M3PASS via the S7MASTUB, then an internal problem exists. It is good practice to contact TIBCO technical support and provide system logs, CICS dumps, and Auxtrace. Check the LKED for the user program to ensure it includes S7MASTUB.

System Action: The CICS transaction is terminated with a S7M3 abend.

Destination: DDNAME CEEOUT.