Resolving Problems with PETs
It is axiomatic that all computer programs have bugs. Therefore, I
expect to find problems with the PETs over time, and I will
try to fix those problems if they are brought to my attention. Below
are some suggestions about troubleshooting and reporting errors.
Topics
Does Mouse-clicking Work For You?
One of the major advantages of PETs is that they interact effectively
with a workstation mouse. If you can't get mouse-clicking to work,
- your "mouse action" is not defined properly within your 3270
emulation software,
- your 3270 emulation software doesn't support configuring the mouse
action in the necessary way,
- you are not pressing the correct mouse button,
- you are single-clicking but your emulator requires you to
double-click, or
- your mouse is broken.
For further information, check the
3270 Emulators
page.
Do You Have a Writeable "A" Disk?
Some PETs need a small amount of writeable disk space for temporary
files. Others write information to logs. While CMS accounts generally
are configured with writeable "A" disks, some may not be. The current
version of PETs requires at least some writeable space configured as
an "A" disk; so if you do not have a writeable "A" disk, then you won't
be able to use the current version of PETs.
Take a Snapshot of the Screen
If you are using a pc, Macintosh, UNIX workstation, or other smart
terminal, try to take a "screen dump" or snapshot of whatever you see
on the screen which looks like a problem. Many 3270 emulators provide
a screen dump feature.
Alternatively, try to take a picture of the screen with other software
tools which are available to you. For example, if you are using
MS-Windows 95, you can press ALT + PRINT-SCREEN to copy the
contents of the currently active window to the MS-Windows clipboard.
Or you can press PRINT-SCREEN to copy the entire MS-Windows
screen to the clipboard. You can then open a program like MS-Word and
paste the window or screen image into a blank document. Print
the document.
Write Down the Things You Were Doing
In is very helpful if you record details about exactly what you were
doing when the problem occurred. Try to remember what you were doing
just prior to the failure, and just prior to that. If you can
reconstruct a little "history" of your work, that information can be
invaluable.
Try to Recreate the Problem
Try to recreate the problem by doing the same things you were doing
when you had the problem in the first place. If you can recreate the
problem successfully, try changing a few "variables" in your situation.
For example:
- Try logging off and on. Does the problem occur again?
- If you're tight on space, .
- delete any "temporary files" left by PETs (filetype =
$$TEMP$$),
- clear unneeded PETs logs,
- delete old, unneeded files,
- archive old, unneeded files, or
- ask for additional "A" disk space.
- Try logging onto a different CMS account. Do you get the error
from other accounts? If not, what is different about the two accounts?
- Try changing the amount of virtual memory allocated to your account.
Does the problem go away with more memory? and reoccur with less?
- Try accessing different files or selecting other options from the
menus. Does the problem occur with all files? With all menu options?
- Try changing the type of 3270 terminal which you are emulating.
If you are using a 24 line emulation, try a 32 line emulation. If you
are not using extended attributes, trying using an emulation mode which
supports them.
Check with Other People About Their Experiences
Are other people in your organization having the same problem? If not,
then examine the differences between what they are doing and what you
are doing.
Check to See if The Latest Versions of the PETs are Installed at
Your Site
When each program is prepared, a time and date stamp is recorded on the
first line of the program. Compare the date recorded in the program
with the date listed on the
Download Page
to see if you have the latest version of the program. If someone
else installed the software at your site, check with that person or
with your local technical support for assistance. If you don't have
the latest version of the software, download it as well as any
listed co-requisites!
Contact the Author
If all else fails, contact the author about the problem you are
experiencing. We'll work together to figure out what's wrong and
get you going again!
--rick ellis
Mail questions, comments, suggestions or inquiries to
rge@uconnvm.uconn.edu
.
Page last updated on June 19, 1998.
Copyright (C) 1998, Richard G. Ellis