Previous Topic: LPAR Agent OperationNext Topic: Administering


LPAR Agent Messages

Messages are written to the operator console and to data sets in the JES log for the started task.

The following messages can be written to the operator console. These messages are informational only.

A sample JES log (DD SYS00001 of the started task):

2014:10:09 19:05:38 - Starting via operator command.
2014:10:09 19:05:38 - LPAR Agent started. Version: V800  Compiled: Feb  7 2014 13:08:00
2014:10:09 19:05:38 - Using configuration file: //DD:CONFIG
2014:10:09 19:05:38 - ---: Name             = CA DevTest LPAR Agent
2014:10:09 19:05:38 - ---: InitialTrace     = False
2014:10:09 19:05:38 - ---: Mode             = Server
2014:10:09 19:05:38 - ---: PortClient       = 4997
2014:10:09 19:05:38 - ---: PortAgent        = 3998
2014:10:09 19:05:38 - ---: BufferSize       = 65536
2014:10:09 19:05:38 - ---: MaxBufferSize    = 65536
2014:10:09 19:05:38 - ---: AppKASeconds     = 60
2014:10:09 19:05:38 - ---: AppKALimit       = 5
2014:10:09 19:05:38 - Configuration file processing successful.
2014:10:09 19:05:38 - LPAR Agent named CA DevTest LPAR Agent
2014:10:09 19:05:38 - Agent socket ready.
2014:10:09 19:05:38 - Client socket ready.
2014:10:09 19:05:38 - Memory for message buffers allocated.
2014:10:09 19:05:38 - Known interfaces: 192.86.32.105
2014:10:09 19:05:38 - Initial configuration complete.
2014:10:09 19:06:45 - ID: 2 - Accepted agent connection from 192.168.0.100.
2014:10:09 19:06:48 - ID: 3 - Accepted agent connection from 192.168.0.100.
2014:10:09 19:06:48 - ID: 4 - Accepted client connection from 192.168.0.101.