A server message will be one of these types: Change, Error, Exception, Message, or Warning. Possible individual messages are listed below.
Change Messages
(Queue Period Reporting) Idle Q AVG=0/0=0.00, Total VMsgCount=0, CUR VMsgs On Q=0, LastPeriod(LP) MaxQTime=0 occurred at Dec 31 18:00:00, LP MaxPTime=0 occurred at Dec 31 18:00:00, LP Avg Process Time=0.00, LP PEAK QUEUE HWM=0 occurred at Dec 31 18:00:00, LP Avg Queue Time=0.00, CUR Active Threads=0, LP PEAK Threads HWMk=0 occurred at Dec 31 18:00:00, LP Idle Queue Cnt=0, LP Vmsg Delta=0, LP Idle Queue Percent= 0.00
0x2603 End Of Resync recv’d for host:O14Q2, token=1075cdafaeb, VMSG=Vmsg ID: 0x2603, RawData: [B@1549cda, Parms: {sname=O14Q2, ovwds=(2,2,0,0), timereceived=Fri Nov 04 13:57:34 CST 2005, ifcs=[(TCPIP,36,36,0,0), (TCPIPB,14,14,0,0)], t1ifcs=[(JIMINY,5,5,0,0), (QUASIMOT,2,2,0,0)], tid=U5894838, token=1075cdafaeb, alrts=278, t1stks=(2,2,0,0), frams=[(TCPIP,1,1,0,0), (TCPIPB,1,1,0,0)], stacks=(2,2,0,0), appls=(27,27,0,0), eecds=(2,1,1,0), csm=1588, vmsg_id=2603}
Added agent.SDSM0150 as listener for Vmsg ID: 2000
Disabling agent: O14TRK
Persistence Cache directory cleared on server startup.
VIPSRVR Number 5 Version 4.5.0 Build:051021 Fixes: [1,2,3,4,5,6,7,8,9,10,11,12,13,14,15]
VIPServer: building – NAG Servlet
VMsgQueue: Purging all VMsgObjects from the queue for agent:O14TRK
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1101(Client=bjpn1@Unknown) VIP client: logon successful.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1101(Client=sds@Unknown) Client logged off. VIP client: logged off.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1101(Client=sds@Unknown) VIP client: logon successful.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14Q2) Detected TCP listener at 10.14.0.1:6012 for agent O14Q2
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14Q2) Received handshake, Cvtsname only, from VIP.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14Q2) TCP connection established with agent
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14Q2) TCP pipe closed because input stream is OutOfSync.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14TRK) Detected TCP listener at 10.14.0.1:5000 for agent O14TRK
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14TRK) Received handshake, Cvtsname only, from VIP.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14TRK) TCP connection established with agent
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14TRK) TCP pipe closed to honor shutdown command.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O31Q2) Detected TCP listener at 10.31.0.1:6012 for agent O31Q2
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O31Q2) Received handshake, Cvtsname only, from VIP.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O31Q2) TCP connection established with agent
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O31Q2) TCP pipe closed because input stream is OutOfSync.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1111().run() VIP communication daemon is now alive.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1117((VIP=O14Q2)).run() Attempting to trigger resynchronization
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1117((VIP=O14TRK)).run() Attempting to trigger resynchronization
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1117((VIP=O31Q2)).run() Attempting to trigger resynchronization
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1135().run() Server timer daemon is now alive.
Ver 1 Rel 0 Mod 0 Fix 04 of agent.SDSM1113(VIP=O14TRK).run() VIP keep-alive daemon is now alive.
VmsgQueue Purged 0 VMSGObjects from the Queue for pipeID -4766034024803701248 Per request. Time to Complete Operation: 0ms
adding: O14Q2
created: [/MVSCVTS/:host:]
Error Messages
Revision Level Check failed, so shutting down comunications to host=O14TRK.
Revision Level Check mismatch: host=O14TRK says: Agent and server versions are NOT compatible, communications to agent shutdown (response code = 8). VIP Server version is 4.5.0, host version is 04.06.00
VIPResynch: Entity not resynched due to: agent.VipException: SDSMVmsgStream — ERROR: Time out. Target agent O14Q2 for VMSG ID: 2601
VMsgQueue:requestThread Unable to locate VipObject for vmsObject of type: 0x2881 and pipeID = -4766239619499271936 is unknown! (VMsg agentName = O14Q2)
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1100().repository(Commit,(Client=bdjm1@Unknown)) Attempted to doubly commit: Commit
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1100().serverDoConfigVipAgent() Unable to obtain configuration information.
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1101(Client=bjpn1@Unknown) Communications to MVS System O14Q2 inactive.
Exception Messages
Agent not found: /MVSCVTS/ : D:\vip\vip450\vipdata\agents\/MVSCVTS/.CFG
VIP Exception: agent.VipException: SDSMVmsgStream — ERROR: Time out. Target agent O31Q2 for VMSG ID: 2619
General Messages
SDSM0150 — HLQ set in init() to: D:\vip\vip450\vipdata\
Successfully found ComSdsusaVipProperties.cfg file here: D:\vip\vip450\vipdata\sysvip\ComSdsusaVipProperties.cfg, vipServletRedirect=
Warning Messages
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1100().pipeDoVmsgFromVip() Received VMSG from inactive (VMSG=VM2817ID)
Ver 1 Rel 0 Mod 0 Fix 00 of agent.SDSM1103(VIP=O14TRK) VIP keep-alive daemon is now dead.
Ver 1 Rel 0 Mod 0 Fix 01 of agent.SDSM1110(VMSG=VM2809ID).isVmsgOriginatedFromVip() VMSG probably not from VIP because the header format is invalid. VMSG header = XL8’e5d4e2c700000101′ XL8’bddaed1b824ef080′ XL8’bddcd4d58f228880′ XL8’177c02012030′ XL8’e5c3c9d7280902fc’
(VIPTrafficManager)addVMsgToContainer() Container for token (nnnnnnnn) was not found, and this message will be destroyed! (Caboose came before end of data?)
Description: nnnnnnnn is the bucket ID for a particular server request, 21392473 for example.
The message indicates that data was received in response to a client request, but the buffer meant to hold that data no longer exists.
When the VIP user interface requests data that resides on a VIP agent – history data, for example – the traffic manager at the VIP server creates a “bucket” to hold the response messages as they arrive from the agent. Then the server sends the request to the agent. And the user interface reads from the bucket.
A timer is associated with each bucket. If a bucket is inactive for too long, the traffic manager destroys it. That can happen when agent-server communications are broken for some reason or when the user interface moves on and quits reading from the bucket.
If a message arrives later for a bucket that has timed out and been destroyed, the traffic manager logs this message.