 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WRKQRY Call LOADITMCL</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 05:26:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/#comment-117148</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Mon, 11 Mar 2013 01:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/#comment-117148</guid>
		<description><![CDATA[The message that is shown refers to another message.&#160;But that&#160;other message is apparently a CEE9901 message.
&#160;
And a CEE9901 message is a generic message that says an error occurred, and it tells you to look at the job&#039;s earlier messages to see what all happened.
&#160;
We can&#039;t tell anything until you follow the directions in the message to find the actual error. When you get to the actual error, copy it and paste it here. Be sure to include the message ID.
&#160;
The directions are included in the 2nd-level text of the message. You need to look at 2nd-level text whenever you don&#039;t get enough information from the initial 1st-level text of a message.
&#160;
Tom]]></description>
		<content:encoded><![CDATA[<p>The message that is shown refers to another message.&nbsp;But that&nbsp;other message is apparently a CEE9901 message.<br />
&nbsp;<br />
And a CEE9901 message is a generic message that says an error occurred, and it tells you to look at the job&#8217;s earlier messages to see what all happened.<br />
&nbsp;<br />
We can&#8217;t tell anything until you follow the directions in the message to find the actual error. When you get to the actual error, copy it and paste it here. Be sure to include the message ID.<br />
&nbsp;<br />
The directions are included in the 2nd-level text of the message. You need to look at 2nd-level text whenever you don&#8217;t get enough information from the initial 1st-level text of a message.<br />
&nbsp;<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philpl1jb</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/#comment-117140</link>
		<dc:creator>philpl1jb</dc:creator>
		<pubDate>Sun, 10 Mar 2013 17:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/wrkqry-call-loaditmcl/#comment-117140</guid>
		<description><![CDATA[&lt;pre&gt;We need more info ...

we know that the program LOADITMCAL is failing at statement 600 but we don&#039;t know why or how.

  1.  What is the statement that is failing

  2.  What error messages and their text that are in the joblog just before the cee9901 error.
&lt;/pre&gt;]]></description>
		<content:encoded><![CDATA[<pre>We need more info ...

we know that the program LOADITMCAL is failing at statement 600 but we don't know why or how.

  1.  What is the statement that is failing

  2.  What error messages and their text that are in the joblog just before the cee9901 error.
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/8 queries in 0.011 seconds using memcached
Object Caching 283/284 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 06:51:36 -->