ScreenSafer/400 Frequently Asked Questions

Index:

• Can I expect any impact on system performance when I install ScreenSafer/400?
  
• I notice a spike in interactive processing when ScreenSafer/400 is manipulating the screen contents, what can I do to reduce this overhead?
  
• I am upgrading my system, what consideration are there for ScreenSafer/400?
  
• I have ScreenSafer/400 intalled and configured, but it does not seem to be working. How can I check that everything is set up correctly?
  
• ScreenSafer/400 sometimes takes over the screen while I'm still typing, why is this happening?
  
• My ScreenSafer/400 manual does not include instructions for installing PTFs from Kisco, how is this done?
  

  ---

  Can I expect any impact on system performance when I install ScreenSafer/400?

  Some customers who have the interactive limit maxed on their systems may see an impact on interactive performance when ScreenSafer/400 is active on a timed-out session. This impact can be limited by your choice of screen manipulation options. See the following article for more information about this issue. Also, if you are regularly running into the limit for interactive performance on your system, take a look at our GoFaster interactive accelerator product as another possible solution for this problem.

  ---

  I notice a spike in interactive processing when ScreenSafer/400 is manipulating the screen contents, what can I do to reduce this overhead?

  If you have a lot of users where ScreenSafer/400 has taken control of the session, you could see a spike in interactive utilization on your system. This will happen when the screen saver function is manipulating the screen contents. If this is an issue for you, just set your defaults to present the blank screen. Then, when ScreenSafer/400 kicks in, it will do a single operation to the screen and then go dormant. This will resolve any performance hit that you experience.

  ---

  I am upgrading my system, what consideration are there for ScreenSafer/400?

  If you are just doing an OS/400 upgrade, we recommend that you get printouts of the subsystem configuration information for all subsystems that are using ScreenSafer/400 before you do your OS upgrade. There is always a chance that configuration changes will be imposed by IBM's OS upgrade process.

  If, however, you are doing a hardware upgrade and the serial number for your system will change, then we recommend the following steps:

  1. Contact Kisco Information Systems in advance of your upgrade. You will need to provide the serial number of your new system at that time. Kisco will provide you with a new permanent install code. This should be done several days in advance of your planned upgrade to avoid delays.
  2. If you are upgrading on your existing system and will be keeping your current installed version of OS/400, you MUST deactivate ScreenSafer/400 for your QINTER subsystem before starting the upgrade. FAILURE TO DO THIS COULD RESULT IN THE INABILITY TO LOGON TO YOUR SYSTEM.
  3. Save the ScreenSafer/400 library named SCRSFR400 from your old system using the SAVLIB command.
  4. Restore this library to your new system using the RSTLIB command.
  5. Apply the new install code already received from Kisco at step #1 above.
  6. Go to the configuration menu in ScreenSafer/400 and set the system values to their ScreenSafer/400 defaults.
  7. Activate ScreenSafer/400 for the sub-system QINTER.

  At this point, ScreenSafer/400 should be active and working on your new system.

  ---

  I have ScreenSafer/400 intalled and configured, but it does not seem to be working. How can I check that everything is set up correctly?

  The following is a checklist of things you can check before contacting Kisco Information Systems for support:

  • Check System Value QINACTMSGQ. It should be set to the message queue named SCRSFR400 that is in library SCRSFR400.

  • After having a user log on to your system, display the job information and note the job number. Then, check for a message queue in library SCRSFR400 that is named SFRnnnnnn where the last six characters of the name are the job number. If the message queue is not present, this indicates that the user may not be properly enrolled in ScreenSafer/400 or the subsystem they are logged on to is not active for ScreenSafer/400.

  • Use menu option #1 on the SCRSFR menu to verify that the user profile you are testing with is enrolled to ScreenSafer/400.

  • Use the Display Subsystem Description command (DSPSBSD) for the subsystem you are working with. Select option #7 from the initial display and verify that the first item listed is an entry for program STRSCRSFR in library SCRSFR400. If not, then the product has not been activated for this subsystem.

  If ScreenSafer/400 is still not working even after you've checked the items on this list, please contact us for support.

  We have found that there are two ways to help alleviate this situation. One is to lengthen your delay time by a few extra minutes. The other is to educate your user community about exactly how ScreenSafer/400 works.

  ---

  ScreenSafer/400 sometimes takes over the screen while I'm still typing, why is this happening?

  What you are seeing is probably normal behavior and is related to the way your system senses terminal inactivity. The iSeries-AS/400 senses terminal activity only when the ENTER key or one of the funtion keys is pressed. If you have left your terminal session inactive for a few minutes and then you resume working but do not press the ENTER key or one of the function keys, then ScreenSafer/400 could interrupt what you are doing.

  We have found that there are two ways to help alleviate this situation. One is to lengthen your delay time by a few extra minutes. The other is to educate your user community about exactly how ScreenSafer/400 works.

  ---

  My ScreenSafer/400 manual does not include instructions for installing PTFs from Kisco, how is this done?

  Due to an oversight on our part, we left the PTF installation instructions out of the initial ScreenSafer/400 manual. To install a PTF received from Kisco Information Systems, do the following:

  1. Sign on a QSECOFR.
  2. Create a shared folder named KISCO. You can do this using the CRTFLR command.
  3. Move the PTF file into the shared folder. The easiest way to do this is using Operations Navigator, but you must have the right components installed. More instructions are available if you are not familiar with this operation.
  4. Go to the INSTALL menu in library SCRSFR400.
  5. Run menu option #7.
  6. Leave the first parameter as is and enter the PTF file name in the second parameter.
  7. When the PTF install runs, PTF documentation will be printed, check your spool file when you are done.

  ---

  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