Page last updated on December 30, 2011
The following is a list of problems reported for SNDTWEET along with the solutions that we
have developed for them. If you have a problem that is not covered here, ask us via
Index:
SNDTWEET Release 3 Problem Reports:
SNDTWEET Release 2 Problem Reports:
SNDTWEET Release 1 Problem Reports:
SNDTWEET Release 3 Problems:
I am getting some duplicate tweet errors from a message queue monitor
function.
We have heard from a very few customers that this issue has been ongoing. After collecting a lot
of diagnostic information, we have finally found the source of this issue and made corrective
changes.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.12
version of SNDTWEET. The correction is available in PTF package STPTF313. E-mail us and request
the PTF package using the mail link at the bottom of this page.
Remote submissions to my IBM i are not getting processed.
Several customers reported this issue to us and we have now traced it to a change implemented at
Twitter as of October 1, 2011. Along with the remote submissions no longer working, customers
also reported seeing joblog errors indicating that a parameter length of 15 was being exceeded.
We have now fixed SNDTWEET to work with the new changes from Twitter.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.10
version of SNDTWEET. The correction is available in PTF package STPTF311. E-mail us and request
the PTF package using the mail link at the bottom of this page.
The SNDTWEET Tweet Scheduler will not accept a future date.
We discovered an edit issue that was preventing entry for tweets to be issued on future days. This
has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.08
version of SNDTWEET. The correction is available in PTF package STPTF309. E-mail us and request
the PTF package using the mail link at the bottom of this page.
The SNDTWEET Watch function is not starting for me.
We found that an engineering change made with IBM's OS levels for 6.1 and higher were creating
problems when attempting to start the SNDTWEET Watch function. We have now changed the way the
watch starts so that this will not be a problem.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.07
version of SNDTWEET. The correction is available in PTF package STPTF308. E-mail us and request
the PTF package using the mail link at the bottom of this page.
Even after installing the latest PTF, I am still seeing duplicate tweet rejections
in my message queue monitor process for QSYSOPR.
The algorith used by Twitter to determine what constitutes a duplicate tweet is unpublished. While the
latest SNDTWEET PTF corrected the duplicate tweet rejection problem for most customers, some are still
seeing this issue on rare occasions. We have now made the time period for duplicate checking an
external variable that can be set by installation which should resolve the issue for customers who
are tracking a high number of events from QSYSOPR and are still running into duplicate rejections.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.05
version of SNDTWEET. The correction is available in PTF package STPTF306. E-mail us and request
the PTF package using the mail link at the bottom of this page.
Several SNDTWEET issued fixed.
SNDTWEET Release 3.04 (the release prior to this one) included a major re-engineering of the SNDTWEET
authentication method with Twitter.com. Since then, a few customers have reported some minor problems
that are now addressed.
Some customers reported that the message queue monitor process was failing with a TWI0010 error code.
This points to a problem of duplicate tweets, which SNDTWEET should have captured and dealt with before
the tweet was issued. This has now been corrected.
Some systems were producing one page nuisance spool files containing diagnostic information. These are
now suppressed.
During upgrade installation processing, customer's who had modified the ITWEET job description for their
custom applications reported loosing those special settings. This has now been changed so that the custom
job description will be preserved during upgrade installation processing.
The fix for these problems is available as a PTF. This PTF can only be installed on a Release 3.04
version of SNDTWEET. The correction is available in PTF package STPTF305. E-mail us and request
the PTF package using the mail link at the bottom of this page.
SNDTWEET is generating a lot of short spool files with diagnostic information.
In some customer installations, we found that SNDTWEET was working correctly, but diagnostic spool files
were still being created on a regular basis. We have now changed the product so that when SNDTWEET has
the debug feature turned *OFF (using the TWEETSET command), then these spool files will be suppressed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.01
version of SNDTWEET. The correction is available in PTF package STPTF302. E-mail us and request
the PTF package using the mail link at the bottom of this page.
SNDTWEET Release 2 Problems:
SNDTWEET stopped working on September 2, 2010.
With no advance notice to us, as developers, Twitter changed its method of logon authentication as of
this date. The method that had been used by SNDTWEET is no longer supported. We have now re-engineered
SNDTWEET to use the new "OAuth" authentication method now being supported by Twitter.
To use this new method, current and future customers will have to make sure certain additional components
of the IBM OS are installed. Plus, there will be some configuration work needed in order to set up your
system for use with the new authentication process. The new configuration requirements are documented
in a new release of the SNDTWEET documentation. A copy of the new documentation is being distributed with
the PTF fix.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.12
version of SNDTWEET. The correction is available in PTF package STPTF212. E-mail us and request
the PTF package using the mail link at the bottom of this page.
When I select menu option #5 from the MASTER menu, I get a CPF4101 error.
We found that this could happen if the SNDTWEET library was not in your session library list. We
have now changed the product so that the menu option will always work correctly regardless of how
your library list is configured.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.10
version of SNDTWEET. The correction is available in PTF package STPTF211. E-mail us and request
the PTF package using the mail link at the bottom of this page.
I can't start a message queue monitor and the error message does not make
any sense.
A customer contacted us while having this difficulty. The error message indicated that more than
100 message queue monitors were already running. We found that the error message was incorrect.
The customer was actually attempting to start a message queue monitor for a queue that was already
being monitored. A correct error message is now issued when this happens.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.08
version of SNDTWEET. The correction is available in PTF package STPTF209. E-mail us and request
the PTF package using the mail link at the bottom of this page.
I am finding one line QPRINT spool files that contain debugging text
on my system.
A recent version upgrade issued by us for SNDTWEET inadvertently contained some developer debugging
code left in place. This has now been removed. It does not affect the operation of the product.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.06
version of SNDTWEET. The correction is available in PTF package STPTF207. E-mail us and request
the PTF package using the mail link at the bottom of this page.
The Tweet receive process does not appear to be working.
We found that under certain circumstances, when the Twitter server is experienceing stability
issues, SNDTWEET's tweet receive process could end up freezing up and stop working altogether.
To date, we have not heard of this as an issue from any customers, but we have observed the
issue on our own test server. We have now made changes that force the receive process to
keep running when this happens.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.05
version of SNDTWEET. The correction is available in PTF package STPTF206. E-mail us and request
the PTF package using the mail link at the bottom of this page.
I am getting occasional TWI0006 error codes issued by SNDTWEET.
When the Twitter servers gets very busy, this error can be issued by SNDTWEET. With this PTF
change, we have added code to trap this error and go into automatic retry mode.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.04
version of SNDTWEET. The correction is available in PTF package STPTF205. E-mail us and request
the PTF package using the mail link at the bottom of this page.
Remote processing appears to be running over and over again.
Due to the huge success of Twitter, the message counter used to control which Twitter messages
to read when checking for directed tweets overflowed. You can fix this problem by upgrading to
a minimum release level of release 2.02.
If you need to correct this problem immediately, you can do so by first shutting down all SNDTWEET
message monitor tasks using normal procedures. Verify that the ITWEET subsystem has been ended,
then just process the following command from the command line:
When this command has been processed, you can resume normal SNDTWEET functions.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.01
version of SNDTWEET. The correction is available in PTF package STPTF202. E-mail us and request
the PTF package using the mail link at the bottom of this page.
The SNDTWEET message queue monitor ends with an MCHxxxx error after running
successfully for several days.
Due to some recent instability at Twitter.com caused by DOS attacks, response from Twitter.com has
been erratic at times. We have now made some improvements to SNDTWEET to deal properly with this
instability and avoid halting on error conditions.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.06
version of SNDTWEET. The correction is available in PTF package STPTF107. E-mail us and request
the PTF package using the mail link at the bottom of this page.
A message queue monitor tasks is running away (looping) on my system.
A customer reported this to us and we found that under certain circumstances, a message queue
monitor function could end up looping. This has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.05
version of SNDTWEET. The correction is available in PTF package STPTF106. E-mail us and request
the PTF package using the mail link at the bottom of this page.
When starting a message monitor with reply processing active, I get a
CPF0001 error.
We found an incorrectly bound program that was pointing to resources in an incorrect library.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.03
version of SNDTWEET. The correction is available in PTF package STPTF104. E-mail us and request
the PTF package using the mail link at the bottom of this page.
When I try to run SNDTWEET, I get an MCH3601 error in program SNDTWEET.
If you get this error, it probably means that your system cannot connect to the Twitter.com service. To
confirm this, run the following command from your command line:
On most systems, you should be able to fix this situation by adding a host name table entry to your system
that will resolve the required IP address. First you must determine the current numerical IP address to
use for the twitter service. You can do this from your PC where Twitter is working. Run a PING from that
PC and write down the numerical IP address that is resolved. At the time of this writing, we found that
the IP address "128.121.146.100" worked for this purpose, but you must verify it at your location.
When you have the IP address, then run the following command on your system from the command line:
Phone: (518) 897-5002 Fax: (518) 897-5003
E-mail your questions or suggestions: 
To register your
E-mail address and receive automatic notification when this page is updated,
CLICK HERE.
SNDTWEET Problem Reports
CHGDTAARA DTAARA(SNDTWT201/CONTROL (1 15)) VALUE('1005643065 ')
SNDTWEET Release 1 Problems:
PING RMTSYS(TWITTER.COM)
If this command returns and message indicating that it is an unknown host, then the MCH3601 error is
happening because of this.
ADDTCPHTE INTNETADR('128.121.146.100') HOSTNAME((TWITTER.COM))
Substitute the numerical IP address for your installation. This command will establish the needed host name
table entry on your system. Retry your Tweet and it should work at this point.
Contact Information
Kisco Information Systems
89 Church Street
Mt Kisco, New York 12983
Support@Kisco.com