Schedule file transfer log message examples

Examples of the messages that are published to the SYSTEM.FTE topic with a topic string of Log/agent_name/schedule_ID when a scheduled transfer action occurs.


Scheduled transfer log message

Every time a request for a scheduled file transfer is processed by the agent, a schedule log message is published to the coordination queue manager (on its SYSTEM.FTE/Log/agent name/schedule ID topic). This message conforms to the ScheduleLog.xsd XML schema. For example: 

<?xml version="1.0" encoding="UTF-8"?>
<schedulelog version="1.00" ID="5"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:noNamespaceSchemaLocation="ScheduleLog.xsd">
	<originator>
		<hostName>reportserver.com</hostName>
		<userID>USER1</userID>
	</originator>
	<action time="2008-11-23T21:32:01Z">submit</action>
	<schedule>
		<submit timebase="admin" timezone="Europe/London">2008-11-23T22:00</submit>
	</schedule>
	<sourceAgent agent="FTEAGENT" QMgr="QM1" />
	<destinationAgent agent="FTEAGENT" QMgr="QM1" />
	<status resultCode="0" />
	<transferSet size="1" priority="0">
		<item mode="binary" checksumMethod="MD5">
			<source recursive="false" disposition="leave">
				<file>c:\sourcefiles\source1.doc</file>
			</source>
			<destination type="file" exist="overwrite">
				<file>c:\destinationfiles\dest1.doc</file>
			</destination>
		</item>
	</transferSet>
</schedulelog>
This message is a log of the following information:

  • Who originated the request
  • When the request was submitted
  • When the scheduled transfer starts
  • The source and destination agent details
  • The transfer specification

The ID attribute of the <schedulelog> element is a unique ID for this scheduled transfer (in the source agent). This ID is used to correlate schedule entries with the actual file transfers.

The <action> element value of submit confirms the request has been received.


Scheduled transfer cancel log message

When a request to cancel a pending scheduled file transfer is received by the agent, the following message is published to the SYSTEM.FTE/Log/agent_name topic:

<?xml version="1.0" encoding="UTF-8"?>
<schedulelog version="1.00" ID="5"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:noNamespaceSchemaLocation="ScheduleLog.xsd">
	<originator>
		<hostName>reportserver.com</hostName>
		<userID>USER1</userID>
	</originator>
	<action time="2008-11-23T21:56:27Z">delete</action>
	<status resultCode="0" />
</schedulelog>
The ID attribute value corresponds to the ID of the pending transfer request ID in the schedules message.


Scheduled transfer expire log message

When the current time matches the time of the earliest pending file transfer in the schedule list (as indicated by the value of the <next> element), a schedule log message is published to indicate that the scheduled transfer entry has expired: 
<?xml version="1.0" encoding="UTF-8"?>
<schedulelog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
             version="4.00" ID="3" 
             xsi:noNamespaceSchemaLocation="ScheduleLog.xsd">   
    <originator>     
        <hostName>example.com.</hostName>     
        <userID>mqm</userID>     
        <mqmdUserID>mqm</mqmdUserID>   
    </originator>   
    <action time="2011-01-26T13:03:26Z">expire</action>   
    <sourceAgent agent="AGENT_JUPITER" QMgr="QM_JUPITER"/>   
    <status resultCode="0"/>
</schedulelog>
The <action> element value of "expire" confirms the schedule entry has now been removed from the schedule list and is being processed. A schedule message for the agent is published with the expired entry no longer present. Parent topic: Scheduled file transfer log message formats


Related reference