Automatic Installation Guide
Installation Process
The rapid full function install process consists of the following steps.

Prerequisites
Before you start the installation process you need the prerequisite items.
Prerequisite Items |
---|
Prerequisite Items |
An aXes download file |
Mandatory PTFs applied on your IBM i server |
Port number(s) you wish to use with aXes |
Installation steps
Step 1: apply mandatory PTFs
If your IBM i server runs this SLIC version |
You must have these PTFs applied |
IBM PTF Description |
---|---|---|
V6R1 |
MF53662 5761999 |
LIC-COMM-TCPIP-UNPRED UNPREDICTABLE RESULTS WITH INCORRECTLY |
V6R1M1 |
MF53664 5761999 |
LIC-COMM-TCPIP-UNPRED UNPREDICTABLE RESULTS WITH INCORRECTLY |
V7R1 |
MF53665 5770999 |
LIC-COMM-TCPIP-UNPRED UNPREDICTABLE RESULTS WITH INCORRECTLY |
If you keep up your IBM i CUME levels then you probably have applied these PTFs already - but it is worth taking a few minutes to check. You can find PTF details using Google.
To check if a PTF is installed use DSPPTF, for example:
DSPPTF LICPGM(5722SS1) SELECT(SI35079)
Confirm that the PTF has a status of temporarily or permanently applied.
If you apply a PTF after aXes has been installed, you need to stop and restart all aXes server jobs.
Step 2: Transfer downloaded save file to your IBM i server
You will need approximately 300 MB of disk space on your PC to download:
Download the aXes package zip file containing AXINSPKG.savf to your PC and unzip it on your PC.
Transfer the package save file to your server via FTP:
2.1 Start a command prompt window.
2.2 Change to the directory containing the save file.
2.3 Start FTP to your server and transfer the save file by issuing the following commands, replacing the words ‘host-system’, ‘user-profile’, and ‘password’ with appropriate values for your environment:
FTP host-system
user-profile
password
quote site namefmt 1
cd /QSYS.LIB/QGPL.LIB
bin
prompt
put AXINSPKG.savf
quit
If the IBM i FTP server is not running, start it using the command STRTCPSVR *FTP. You must have authority to use the command.
Step 3: Set server system values
Sign on to the server as QSECOFR or a user with QSECOFR group authority.
Ensure these system values are as shown:
System Value |
Required Value |
---|---|
QFRCCVNRST |
0 |
QVFYOBJRST |
1 |
QUTCOFFSET |
Must be set to something |
QAUTOVRT |
A large number or *NOMAX |
QALWOBJRST |
*ALL |
If you need to change these values you can change them back after aXes has been installed.
There is no need to IPL the system.
Step 4: Shutdown the aXes Subsystem, if required.
If you have axes already installed please end the subsystem with these commands:
ENDSBS AXES *IMMED
ENDSBS AXESJSM *IMMED
Note the libraries names might differ based on your previous installation settings. This step is not requires is there are no previous aXes installed.
Step 5: Install aXes using the command LODRUN
Before starting the install you might have to delete the previous installation object from the aXes services JSM. For this look for the JSMINSTALL library using the command
WRKLIB JSMINSTALL
If the library is present on your system but you are unsure if it can be deleted, you can rename it.
If your Operating System is V7R1 or higher, issue these commands:
ADDLIBLE QTEMP (Only if QTEMP is not on your library list)
LODRUN DEV(*SAVF) SAVF(QGPL/AXINSPKG)
If your Operating System is V6R1, issue these commands:
RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(QGPL/AXINSPKG) RSTLIB(QTEMP)
ADDLIBLE QTEMP (Only if QTEMP is not on your library list)
QTEMP/LODAXES
Once the installer is started follow steps 5.1, 5.2 and 5.3, if appropriate.
Step 5.1 if aXes is not already installed:
A screen will be displayed with the following:
Information |
Description |
---|---|
Product library |
The name of the new product library. This library must not exist on the system. |
Home Directory |
The directory in which aXes will be installed |
Language |
Language code for the licensed program. See Table 1 |
Language library |
Name of the language library. It will only display if the current language is not *PRIMARY |
Terminal Server Port Number |
Port number for the Axes Terminal Server feature |
Services Manager Port Number |
Port number for the IBMi Services Manager |
Services Console Port Number |
Port number for the IBMi Services Console |
Services HTTP Port Number |
Port number for the HTTP server for IBMi services |
Include LongRange |
Yes or No Refer to the longrange product documentation for more details located at https://www.longrangemobile.com/ |
Include the examples |
Yes or No |
If all defaults are suitable, use F8 to commence the install.
Step 5.2 if aXes is already installed:
New release beside a previous release
Use this option if you would like to have the new version to co-exist with existing versions.
Information |
Description |
---|---|
Product library |
The name of the new product library. This library must not exist on the system. |
Home Directory |
The directory in which aXes is installed |
Language |
Language code for the licensed program. See Table 1 |
Language library |
Name of the language library. It will only display if the current language is not *PRIMARY |
Include LongRange |
Yes or No Refer to the Longrange product documentation for more details located at https://www.longrangemobile.com/ |
Include the examples |
Yes or No |
Work with existing releases
If you have the current version installed it will only display the current version and this option can be used to repair this version.
Use F8 to commence the install/Upgrade.
Step 5.3 Check your aXes license.
If this is the first time you install axes, you will be granted a 60 days grace period.
After this grace period has expired, you will be required to obtain an axes license.
After the installer has finished, it will try to start aXes. If the start is unsuccessful, aXes will display the following message: "This aXes system is not yet licensed or the grace period has expired. You will need to apply the required license keys obtained from your aXes representative."
Contact your aXes representative to obtain the required license keys.
Table 1:Language Codes
Language Code |
Language |
---|---|
2924 |
English Uppercase and Lowercase. Use when installing on a Single-Byte Character Set (SBCS) system for which no translated version of aXes is provided. |
2938 |
English Uppercase Support for Double-Byte Character Set (DBCS). Use this value when installing on a DBCS system for which no translated version of aXes is provided and the system does not support lower-case English characters (for example Katakana-Kanji). |
2950 |
English Uppercase |
2984 |
English Uppercase and Lowercase Support for Double-Byte Character Set (DBCS). Use this value when installing on a DBCS system for which no translated version of aXes is provided. |
Step 6: Verify aXes installed successfully
To verify that all the options were installed, do the following:
- From a command line, type GO LICPGM and take option 10.
- This will display the list of installed licensed programs.
- Page up or down to locate the Licensed Program name 1AXES01 and check the install status.
The list below is an example of a successful install:
Licensed |
Status |
Description |
1AXES01 |
*INSTALLED |
aXes Base |
1AXES01 |
*INSTALLED |
aXes Terminal Server |
1AXES01 |
*INSTALLED |
aXes Application Server |
1AXES01 |
*INSTALLED |
aXes Spooler File Server |
1AXES01 |
*INSTALLED |
aXes Examples |
Step 7: Clean up after the install
Delete the installation material on the server:
DLTF QGPL/AXINSPKG
Also delete the installation files on your PC.
Step 8: Start the subsystem
To use the new HTTP Services web server (Recommended)
<AXES_JSM_LIBRARY> is the aXes Services library. It is automatically generated during install where JSM is appended at the end of the <AXES_LIBRARY> you have chosen in step 5.1 or 5.2. Default is AXESJSM
Start aXes services with the command STRSBS <AXES_JSM_LIBRARY>/<AXES_JSM_LIBRARY>
Typically: STRSBS AXESJSM/AXESJSM
To use the aXesW3 webserver (previous)
<AXES_LIBRARY> is the product library you have chosen in step 5.1 or 5.2. Default is AXES
Start aXes with the command STRSBS <AXES_LIBRARY>/AXES
Typically: STRSBS AXES/AXES
Step 9: Start using an aXes 5250 Session in a browser
Once the autostart jobs have completed, launch aXes from your browser:
http://<host name>:<port number>
host name = the name of your server or its IP Address
port number = the port number required to access your server, either the aXesW3 port or the aXes HTTP Services web server
Mouse over the resulting options to investigate them.
Default passwords
All aXes versions, aXesW3 and aXesJSM
The default username /password combination is dev/dev for the development terminal session.
You should change these values using the instructions in the article Managing aXes Users.
All aXes versions, aXesW3 only
The default username/password combination for the server status options is admin/admin.
You should change these values using the instructions in the article Managing aXes Users.
aXes 4.2.1, aXesJSM only
The default password for the Management Console is admin.
You should change the default password. Use the change password option in the Management Console interface to change your password.
Try the shipped demonstration system
Try out the shipped demonstration system using the Basic Terminal Session link.
Sign on with a valid user profile and a password which is authorized for the library AXESDEMO
Add the library AXESDEMO to the library list by entering the following command on the command line:
ADDLIBLE AXESDEMO
Now start the simple demonstration application by entering the following command:
CALL XHRRPGTRN
Start enhancing 5250 screens by using the Tutorials link Extension Tutorial 00 - Getting Started - v4.2.0