![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Table 27 describes the WTO messages.
TIBCO Mainframe Service Tracker sends a WTO message to its expected destination only if the debug level (as specified in the DBGLVLALL parameter) is equal to or greater than the Debug Level for Output value for the message.
Table 27 WTO Messages Wrong subsystem name ssid on input. Explanation: The SS name on the input message does not equal to ssid in the Subsystem Communications Vector Table (SSCVT). User Response: Contact TIBCO Support. System Action: The subsystem request is not processed. Expected Destination: JESMSGLG of any job Wrong function funct received. Explanation: The subsystem function code is not supported by the function’s module. User Response: Contact TIBCO Support. System Action: The subsystem request is not processed. Expected Destination: JESMSGLG of any job Return own version pgm version. Explanation: This message is in response to a function 15-version-request. System Action: Processing continues. Expected Destination: Tracker JESMSGLG Explanation: An input with function code funct has been received. System Action: Processing continues. Expected Destination: JESMSGLG of any job Get value Subsystem ssid failed — returned zero pointer. Explanation: The SSCTSUSE pointer is zero. User Response: Contact TIBCO Support. System Action: The subsystem request is not processed. Expected Destination: JESMSGLG of any job SSOBINDV=hex ssob Explanation: This message displays the first part of the SSOBINDV area. System Action: Processing continues. Expected Destination: JESMSGLG of any job Explanation: The function correctly returned its own address and the SMF exits. System Action: Processing continues. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: An SMF exit has returned a job-status change. System Action: Processing continues. Expected Destination: JESMSGLG of any job Explanation: A job-status change matches a MONITOR entry. System Action: Processing continues. Expected Destination: JESMSGLG of a monitored job Explanation: A Smart Client request has been received. System Action: Processing continues. Expected Destination: JESMSGLG of a Smart Client Explanation: A Smart Client message could not be sent to the processor because of a missing processor address or no buffers. User Response: Contact TIBCO Support. System Action: The message is not processed. Expected Destination: JESMSGLG of a Smart Client Explanation: A TIBCO Hawk alert request has been received. System Action: Processing continues. Expected Destination: JESMSGLG of a TIBCO Hawk alert requestor Explanation: The TIBCO Hawk alert message could not be sent to the processor because of a missing processor address or no buffers. User Response: Contact TIBCO Support. System Action: The message is not processed. Expected Destination: JESMSGLG of a TIBCO Hawk alert requestor Explanation: The input parm field has an invalid value. User Response: Contact TIBCO Support. System Action: Processing ends and the subsystem is not created. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The ESTAE failed the setup. User Response: Contact TIBCO Support System Action: The subsystem is not created. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The ESTAE has been activated but an error has occurred during the creation process. User Response: Contact TIBCO Support. System Action: The subsystem is not created. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The IEFSSVT CREATE request failed. User Response: Contact TIBCO Support. System Action: The subsystem is not created. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The Storage OBTAIN request for the common-data area failed. User Response: Contact TIBCO Support. System Action: The subsystem is not activated. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG User Response: Contact TIBCO Support. System Action: The subsystem is not activated. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The IEFSSI OPTIONS request failed. User Response: Contact TIBCO Support. System Action: The subsystem is not activated. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The IEFSSI ACTIVATE request failed. User Response: Contact TIBCO Support. System Action: The subsystem is not activated. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Tracker Subsystem ssid activated. Explanation: The subsystem is successfully activated. System Action: Processing continues. Expected Destination: TIBCO Mainframe Service Tracker JESMSGLG Explanation: The ACTRT exit is reporting a step or job end. System Action: Processing continues. Expected Destination: JESMSGLG of any job User Response: Contact TIBCO Support. System Action: The job-status change message is lost. Expected Destination: JESMSGLG of any job Explanation: The UJI exit is reporting a job start. System Action: Processing continues. Expected Destination: JESMSGLG of any job User Response: Contact TIBCO Support. System Action: The job-start message is lost.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |