. Kisco Home : products : ScreenSafer/400 : Support : Problem Reports .
.
Page last updated on May 13, 2011

The following is a list of problems reported for ScreenSafer/400 along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.

To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE.


ScreenSafer/400 Problem Reports

Index:


ScreenSafer/400 Problems:

The secondary timeout feature is not working on my system.

Based on a customer support call, we found that a recent performance change made to the software had inadvertently disabled the secondary timeout feature. This has now been corrected and the secondary timeout feature once again works as documented.

A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 3.05 version of ScreenSafer/400. The correction is available in PTF package SFPTF306. E-mail us and request the PTF package to correct this problem.


ScreenSafer/400 is taking over sessions that do not appear to be inactive.

We heard this question from a customer with several hundred active sessions, all of which were for users enrolled in ScreenSafer/400. What we found was that the session actually had timed out, but the session had not yet been taken over by ScreenSafer/400 before the user resumed work. Then, right after they resumed work, ScreenSafer/400 kicked in leaving the impression that the product was taking over an active session.

The solution for this was to change the background program that controls ScreenSafer/400 processing to run more efficiently. For customers who have been using ScreenSafer/400 for some time, there is a recommendation with the corrective PTF that should be reviewed.

A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 3.04 version of ScreenSafer/400. The correction is available in PTF package SFPTF305. E-mail us and request the PTF package to correct this problem.


After running fine for several years, ScreenSafer/400 has stopped all of a sudden.

A customer who had been using ScreenSafer/400 on the same system for several years reported this problem to us. In the joblog, we found a CPF2460 error which pointed to a message queue for user profile SCRSFR400 that was never getting cleared. If this happens, the immediate cure is to just clear this message queue using the CLRMSGQ command. The message queue is in the QUSRSYS library.

A fix for this has been developed and is now available as a PTF. The fix will periodically clear the message queue in question. This PTF can only be installed on a Release 3.03 version of ScreenSafer/400. The correction is available in PTF package SFPTF304. E-mail us and request the PTF package to correct this problem.


ScreenSafer/400 is failing with error CPF0818 in my session joblog.

After installing ScreenSafer/400 and performing the various configuration steps described in the user's guide, a customer found that the product was still not working. Looking in the joblog for their interactive session, they found a CPF0818 message with the description "Value cannot be converted to type implied by receiver.". This is caused when the system value QMAXSIGN is set to *NOMAX. Since, for security reasons, it is a bad idea to have your system value set to this setting, we recommend that you change this system value to IBM's recommended setting of 3. Once you make this change, then ScreenSafer/400 will start operating correctly.


Sometimes, ScreenSafer/400 takes a long time to "kick in".

Another performance issue has been identified, again for customers with a very high number of users actively being controlled by ScreenSafer/400. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.07 version of ScreenSafer/400. The correction is available in PTF package SFPTF208. E-mail us and request the PTF package to correct this problem.


ScreenSafer/400 is performing erratically.

We found a performance issue in the ScreenSafer/400 system that could cause erratic behavior on certain systems, especially those with a high number of users logged in to ScreenSafer/400. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.06 version of ScreenSafer/400. The correction is available in PTF package SFPTF207. E-mail us and request the PTF package to correct this problem.


Some of our users are reporting having their sessions cancelled while they have been quite active working with them.

We found a problem in the secondary timeout feature that was recently implemented. For certain users, especially those who tend to remain signed on for very long time periods, a false secondary timeout could happen. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.05 version of ScreenSafer/400. The correction is available in PTF package SFPTF206. E-mail us and request the PTF package to correct this problem.


When activating ScreenSafer/400 for a subsystem, it fails trying to register program SCRSFRINZ on the CHGRTGE command.

We found a problem with the configuration program that is prompting the wrong program. You can correct for this by changing the program name from SCRSFRINZ to the correct value of STRSRCSFR. A permanent fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.02 version of ScreenSafer/400. The correction is available in PTF package SFPTF203. E-mail us and request the PTF package to correct this problem.


ScreenSafer/400 is permanently installed on my system but I am still getting warning messages about my trial period expiring.

We found a problem with our software authorization program that was causing this error notice to be issued incorrectly. It does not affect operation of the product A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 1.05 version of ScreenSafer/400. The correction is available in PTF package SFPTF106. E-mail us and request the PTF package to correct this problem.


I am getting session and device errors when I try to work with the registered users in ScreenSafer/400.

We found an artificial limit of 99 users that was built into the product. If more that 99 users are registered, the update program exhibits this problem. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 1.04 version of ScreenSafer/400. The correction is available in PTF package SFPTF105. E-mail us and request the PTF package to correct this problem.


ScreenSafer/400 is not working for some of our registered users, they are unable to signon to our system.

We discovered a problem that can happen when ScreenSafer/400 is used on a system that uses a mixture of system date formats. On the system where the problem was identified, some users had a default date format of *DMY while others had *MDY. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 1.03 version of ScreenSafer/400. The correction is available in PTF package SFPTF104. E-mail us and request the PTF package to correct this problem.


The ScreenSafer/400 timeout screens are erratic in their timing, some work correctly and some take a very long time to be displayed.

We discovered a problem that can happen when ScreenSafer/400 is used on a system that is also running software from Robot Systems. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 1.02 version of ScreenSafer/400. The correction is available in PTF package SFPTF103. E-mail us and request the PTF package to correct this problem.


Some of the menu options on the SCRSFR menu have error messages when you use them.

We discovered some problems with early copies of ScreenSafer/400 when using certain menu topsions. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 1.01 version of ScreenSafer/400. The correction is available in PTF package SFPTF102. E-mail us and request the PTF package to correct this problem.


Contact Information
Kisco Information Systems
89 Church Street
Saranac Lake, NY 12983

Phone: (518) 897-5002 Fax: (518) 897-5003

E-mail your questions or suggestions: Support@Kisco.com

.
.
Kisco Information Systems 89 Church Street Saranac Lake, NY 12983
phone: 518.897.5002 | fax: 518.897.5003
sales@kisco.com about kisco kisco products product support kisco consulting services useful links