- Requesting a free
60-day license to trial the LongRange module
How to obtain the system information required to request a free 60-day trial license for the aXes LongRange module.
- Checking which version
of aXes is installed
Instructions for checking the version of an aXes installation and instructions for checking if aXes has ever been installed on a server.
- Applying a session based license to a trial version of aXes
If you request a session based aXes license after the trial period has ended, there are some important steps that need to be followed before applying your new license.
- V6R1 CUME C1102610 will
cause aXesTS issues
aXesTS users on V6R1 have reported that after applying CUME C1102610 you will immediately encounter various TCPIP errors when using the Terminal Sessions.
- Unexpected DE2 behaviour after installing aXes 2.1 if a particular IBM PTF is not installed
There have been reports of unexpected behaviour when installing or using DE2 on V5R4M0 if a PTF has not been applied.
- CCSID considerations when registering users manually in DE2 or WS2
Using an appropriate CCSID is essential when registering users manually to avoid incorrect data in the database.
- Checking OS/400 PTF levels
To use aXes some IBM supplied OS/400 PTFs are mandated.
- Checking aXes Server Job
Often checking the job logs of aXes server jobs can reveal information about a problem.
- Using Fiddler
Fiddler runs on your PC and monitors all traffic between your Web browser and the Internet. When captured and saved this traffic can be a useful source of problem resolution information.
- Checking IBM i (OS/400)
All IBM i (OS/400) servers maintain a history log called QHST. In sites with suspect communication links, QHST will often record TCP/IP level drop outs and recoveries.
- Checking aXes CERN logs
aXes can produce CERN logs. These may reveal information about a problem and is most useful in situations where you cannot install Fiddler onto the the PC with the problem.
- Checking IFS file authority
In general aXes files stored on the OS/400 IFS should be set so that user *PUBLIC has Data Authority *R only and no other authorities.
- Checking customized OS/400
aXes imposes some limitations on how customized OS/400 sign-on screens are formatted. A problem is typified by this error message: "CPF1296 – Signon information required."
- Checking for network/browser