Midrange News for the IBM i Community


Posted by: Bob Cozzi
Rogue Programmer
Cozzi Productions, Inc.
Chicagoland
Client Access for Mac Linux & Window 10
has no ratings.
Published: 11 Jul 2012
Revised: 23 Jan 2013 - 2826 days ago
Last viewed on: 19 Oct 2020 (13503 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

Getting Started with i Access Solutions Published by: Bob Cozzi on 11 Jul 2012 view comments



                    5733XJ1 IBM i Access Client Solutions

The contents of this document were last updated on: April 26, 2012

                           

Contents:
1.0 Introduction
2.0 Features
3.0 Prerequisites
4.0 Product Contents
5.0 Installation
5.1 Updating an Existing Installation
6.0 File Permissions
  6.1 File Permissions (Linux, Mac, AIX)
  6.2 File Permissions (Windows)
7.0 Starting the Product
  7.1 Starting the Product (using a binary file)
  7.2 Starting the Product (using a script)
  7.3 Starting the Product (using the command-line)
8.0 Configuration
  8.1 Configuration Location
9.0 Advanced Topics
  9.1 More command-line Options
  9.2 File Associations
  9.3 Changing Configuration Location
  9.4 Other Deployment Options
  9.5 Customized Packages
10.0 Service Diagnostics
11.0 Frequently Asked Questions (FAQ)


1.0 Introduction
----------------
IBM i Access Client Solutions is the newest member of the IBM i Access family of
products.  It provides a Java based platform-independent interface which runs on
most operating systems that support Java including Linux, Mac and Windows. IBM i
Access Client Solutions consolidates the most commonly used tasks for managing your
IBM i into one simplified location.

IBM i Access Client Solutions uses the same IBM i host servers as the other IBM i
Access Family products and requires the same IBM i Access Family license (XW1) in
order to use the 5250 emulation and Data Transfer features.

For the latest information about IBM i Access Family products, see:
    http://www.ibm.com/systems/i/software/access/caann.html



2.0 Features
------------
Features of IBM i Access Client Solutions include:

- a full featured 5250 display emulator based on IBM Rational Host-on-Demand. In
addition to all the 5250 display features you are accustomed to when using IBM i
Access for Windows, you may now switch your 5250 display emulator between languages
without rebooting your workstation.  In addition, you may have multiple concurrent
sessions with different host code pages.  This allows separate languages to be
displayed within different emulator sessions.
Printer emulation is also supported.

- a 5250 Session Manager modeled after IBM Personal Communications Session Manager
which can be used for managing all of your 5250 emulator sessions

- Data Transfer which provides the ability to transfer data from/to your IBM i
database to/from various file types on your workstation such as OpenDocument
spreadsheet (*.ods), Excel Workbook (*.xlsx) and other file formats

- a Virtual Control Panel with a graphical interface to the IBM i operation panel

- 5250 emulation for LAN Console

- consolidation for hardware management interface configurations including ASMI,
IVM and HMC

- launch capability to IBM Navigator for i using your default browser



3.0 Prerequisites   
-----------------

3.1 Prerequisites (workstation)
--------------------------------
IBM i Access Client Solutions will run on most operating systems that support
Java 6.0 or higher including various versions of Linux, Mac and Windows.

One way to check the version of Java installed on your system is to bring up a
prompt where a command may be entered (Command Prompt, Shell, Terminal, etc) and
then type the command:
    java -version

The following output indicates version 6.0 is installed:
    java version "1.6.0_31"
The 31 in this example refers to the update level.


The following output indicates version 7.0 is installed:
    java version "1.7.0"


Here are some web sites of Java providers.  Make sure you are running with the
most up-to-date version of Java for your platform.
    http://www.oracle.com/technetwork/java/javase/downloads/index.html
    http://www.oracle.com/technetwork/java/javase/index-137561.html
    http://java.com/en/download/manual.jsp
    http://support.apple.com/downloads
    http://support.apple.com/downloads/#macosandsoftware
    http://support.apple.com/downloads#Java
    http://openjdk.java.net/install

3.2 Prerequisites (Connectivity to IBM i)
-----------------------------------------
IBM i Access Client Solutions will connect to IBM i releases 5.4 and above.
The following features require IBM i release 6.1 or above:
    Navigator for i
    5250 Console
    Virtual Control Panel

If you will be using the 5250 Console or the Virtual Control Panel feature
for an IBM i at release 6.1, load and apply the following PTFs:
    MF55543
    MF55549
   
If you will be using the 5250 Console or the Virtual Control Panel feature
for an IBM i at release 6.1 with machine code 6.1.1, load and apply the
following PTFs:
    MF55540
    MF55547

If you will be using the 5250 Console or the Virtual Control Panel feature
for an IBM i at release 7.1, load and apply the following PTFs:
    MF55485
    MF55538
  


4.0 Product Contents
--------------------
The following files and directories are contained in the product zip archive:

acsbundle.jar       - an executable jar file of the product
AcsConfig.properties- file containing configuration settings (also exists
                      inside acsbundle.jar)
                     
Documentation       - directory containing documentation
    GettingStarted_en.txt - information for how to get started

License             - directory containing terms and conditions for usage

Notices             - directory containing notices and information 

Start_Scripts       - directory containing scripts which can be used to
                      start the product.
    Linux_Mac_Other - directory of perl scripts for starting the product
                      on any platform where perl is available.
    Windows         - directory containing a JScript for starting on Windows

Start_Binaries      - directory containing platform specific binary files which
                      can be used to start the product.
    Linux_i386-32
    Linux_x86-64
    Mac_i386-32_x86-64
    Windows_i386-32
    Windows_x86-64


5.0 Installation
----------------
Installing IBM i Access Client Solutions is as simple as unpacking the zip archive.

Determine the location where you want to install the product.  This can be any
location where the workstation (PC, Mac, etc) has read authority to access the
files.  This includes the local hard disk drive, a remote network (shared) drive
or portable media such as a USB flash drive.

Copy the zip archive to the desired location.  Then, unpack the zip archive
using any zip utility of your choice.


5.1 Updating an Existing Installation
-------------------------------------
Enhancements and fixes will be made available on a periodic basis.  These updates
are provided as a complete product installation.  When these updates are available,
you will need to update your existing installation.

Before you update your installation:
  Save any changes you have made to the AcsConfig.properties file (or rename it).
  If you have not changed this file, then you do not need to save it.

To update your existing installation, follow the steps in section 5.0 Installation
and overlay your existing installed files.

Some administrators may choose to install the updated version in a new location.  If
you use this method, make sure you delete the old installation after you have
verified the new installation.

After you have installed your updated version:
  If you saved a copy of a customized AcsConfig.properties file, restore your saved
  copy to the updated installation location.


6.0 File Permissions
--------------------
Section 7.0 Starting the Product describes several different ways to start
IBM i Access Client Solutions.  If you will be using one of the provided scripts
or binary files to start the product, you will need to make sure its file
permissions have the execute permission enabled.  The file permissions assigned
while unpacking the zip archive file are determined by several factors including
the operating system, the archive utility used to unpack the zip archive, the
authority of the user, etc.

If you have trouble using one of the provided scripts or binary files, check
the file permissions.  The following sections describe some methods for
checking the file permissions.


6.1 File Permissions (Linux, Mac, AIX)
--------------------------------------
For unix-like operating systems, you can use the following command from a shell
or terminal prompt to check the permissions of a file:
    ls -l <file>

To change the permissions of a file, you can use the following command:
    chmod <permission> <file>

For example:
    chmod a+rx <file>
...would add read and execute permission for everyone
    chmod 755 <file>
...would give the owner of the file read/write/execute permission and only
read/execute for everyone else.

Additional help for the ls and chmod commands is readily available on the
internet.


6.2 File Permissions (Windows)
------------------------------
For Windows, while viewing the file using Windows explorer, right-click the
file and select properties.  The security tab should contain the file
permissions.  Make sure you have Read & Execute permission.

On recent versions of Windows, you may also use the icacls command to view
and change the permission of a file.


7.0 Starting the Product
------------------------
There are multiple ways to start IBM i Access Client Solutions.  However,
since there are a variety of ways and locations how/where java can be
installed, some of the methods may require additional configuration.  If
one of the methods below does not work, try a different method. In some
cases, additional guidance is provided.  You may also find section
11.0 Frequently Asked Questions (FAQ) helpful.
 
When using a script or binary file as described below, the script or
binary file must be in the directory structure contained in the zip
archive.  For convenience, you may also copy/move the script and/or
binary file(s) for your platform(s) to the same directory where the
acsbundle.jar exists.


7.1 Starting the Product (using a binary file)
----------------------------------------------
To start the product from a file system browser (e.g. Windows Explorer,
Mac OS X Finder, etc) using a platform specific binary file, locate the
sub-directory in Start_Binaries that identifies your operating system and
hardware architecture.

Locate the binary file your operating system recognizes. Then double-click
it to start the product.
You may also start the product with this binary file from a Command Prompt,
Terminal, or Shell.

If you get the following error:
   "Error loading Java module."
IBM i Access Client solutions could not find a java installation in a
location it recognizes.  You may try one of the following methods in sections:
   7.1.1 Starting the Product (using a binary file) - Additional Options
   7.2 Starting the Product (using a script)
   7.3 Starting the Product (using the command-line)

7.1.1 Starting the Product (using a binary file) - Additional Options
---------------------------------------------------------------------
You may also try one of the following methods when trying to use the binary
file for your platform.  These methods allow you to identify which Java
Runtime Environment (JRE) should be used to start the product.  See section
7.1.2 Finding the Java Home Path for how to locate the Java home path on
your workstation.  These additional methods are only supported on Linux and
Windows platforms:
   1. Set the JAVA_HOME environment variable to the java home path   (OR)
   2. Use the -vm option on the binary command to specify the java home
      path.  Specify -h on the binary command for additional help    (OR)
   3. Copy a Java Runtime Environment (JRE) directory structure to the
      same directory as the binary file you are trying use. 

7.1.2 Finding the Java Home Path
--------------------------------
If you can start the product using one of the methods in section:
     7.2 Starting the Product (using a script)  (OR)
     7.3 Starting the Product (using the command-line)
then you can determine the java home path on your workstation from the
IBM i Access Client Solutions main GUI.  On the menu bar, select
     Tools->Generate Service Logs
   - An informational message will be displayed containing the location of the
     log file just generated.
   - Open this log file with a text editor.  This log file can also be found at:
     Edit->Preferences
     select the Local Settings tab
     Find the Dumps Directory and select Open
   - Search the log file for the "java.home" property

The java.home property contains the location of the java home path for your
workstation.  This is the path you will need to specify when setting the
JAVA_HOME environment variable or when using the -vm option on the command.

7.1.2.1 Finding the Java Home Path (on Windows)
----------------------------------------------- 
On Windows platforms, search for java.exe.  The java binary is normally
located in either a bin or jre/bin sub-directory below the Java home path.
The Java home path may be used when setting either the JAVA_HOME environment
variable or when using the -vm option on the command.

7.1.2.2 Finding the Java Home Path (on Linux)
----------------------------------------------- 
On linux you can use the "which" command:
    which java
This will give you a path to the java command or a symbolic link to it.

Resolve any symbolic links until you finally get to the actual binary file
for the java command.  You can resolve symbolic links by using the ls
command with the -l option:
    ls -l <file>
The java binary is normally located in either a bin or jre/bin sub-directory
below the Java home path.  The Java home path may be used when setting either
the JAVA_HOME environment variable or when using the -vm option on the command.


7.2 Starting the Product (using a script)
----------------------------------------
To start the product from a file system browser (e.g. Windows Explorer,
Mac OS X Finder, etc) using one of the supplied scripts, locate the script in
the Start_Scripts sub-directory that is compatible with your operating system.

Most non-Windows based operating systems have perl available by default.  The
Start_Scripts/Linux_Mac_Other directory contains a perl script (with three
different file extensions) which can be used to start the product on any
platform where perl is available.  Select the file that has a file extension
that your operating system will recognize as a perl script.

Windows based operating systems have JScript available by default.  The
Start_Script/Windows directory contains a JScript that can be used to start
the product on Windows operating systems.

Using a platform specific method to browse your file system (e.g. Windows
Explorer, Mac OS X Finder, etc), locate the script your operating system
recognizes.  Then, double-click it to start the product.
You may also start the product with this script from a Command Prompt,
Terminal, or Shell.


7.3 Starting the Product (using the command-line)
-------------------------------------------------
You may also start the product from the command-line from any place you can
enter a command (Command Prompt, Terminal, Shell, etc)
    java -Xmx1024m -jar <path>/acsbundle.jar
where <path> is the location to the product's executable jar file
(e.g.
    java -Xmx1024m -jar V:/some_location/acsbundle.jar
or 
    <java_path>java -jar V:/some_location/acsbundle.jar
where <java_path> is the location of the java command for JDK 6.0 or higher.
See section 7.1.2 Finding the Java Home Path for determining the complete
path to the java command.

You may also use any of the scripts or binary files from the command-line.
(e.g.
    /Product/Location/Start_Scripts/Linux_Mac_Other/acslaunch
or
    /Product/Location/Start_Binaries/Mac_i386-32_x86-64/acslaunch_mac


Technical Note:
On most platforms, the Java Virtual Machine heap space defaults to a maximum
size that is too small to utilize multiple functions within the IBM i Access
Client Solutions product.  A one gigabyte maximum heap size (-Xmx1024m) is
the recommended minimum size.  Specifying sizes smaller than one gigabyte or
using the default heap size may produce an OutOfMemoryException.


8.0 Configuration
-----------------
Add a system configuration for each IBM i system you want to use or manage.  To add
a system configuration, select System Configurations from the Management tasks. Then
select New.  On the General tab, enter the System name.  To get started, the System
name is all that is necessary for performing General tasks.

When you have finished, select OK to save the information you entered for this
system, or select Save/New if you have additional systems you would like to add to
the configuration.

You may add new systems to your configuration or update existing configurations
using the General, Connection, or the Console tabs at any time.

For Console tasks, additional configuration is required.  Console configurations are
automatically associated with the System name you entered on the General tab.  To
enter the console configuration for a system, select System Configurations from the
Management tasks.  Select New or Edit.  Then select the Console tab. 
The 5250 Console task requires a configured LAN console or a configured HMC console.
 
The Virtual Control Panel task requires a configured LAN console.
The Hardware Management Interface task requires a configured hardware management
interface.  You may enter up to two hardware management interface configurations.

When you have finished, select Close on the System Configurations panel.

Using the System drop-down box on the main IBM i Access Client Solutions panel,
select a System.  All Console tasks automatically associate the selected System
(entered on the General tab) with the console configuration (entered on the
Console tab).
 
You may now select a task for the selected system.  If you select a Console task
which does not have the corresponding information entered on the Console
configuration tab, an error message will be displayed.

8.1 Configuration Location
--------------------------
By default, each user will have their own unique location for their configuration.
The configuration root directory is determined in a platform dependent manner.  The
configuration directories will be created during the initial start-up.  To see where
the configuration directory is:
    Start the product (see section 7.0 Starting the Product)
    Edit->Preferences
    Select the Local Settings tab
    Configuration Root

The configuration location cannot be changed while the product is running.  To
change the location of the configuration, see section:
    9.3 Changing Configuration Location


9.0 Advanced Topics
---------------------

9.1 More command-line Options
-----------------------------
Many of the functions that are available from the main GUI are also available
from the command-line.  These functions may be invoked by providing the appropriate
parameters to any of the command-line options shown in:
    section 7.3 Starting the Product (using the command-line)
e.g.
    /Product/Location/Start_Scripts/Linux_Mac_Other/acslaunch parm1 parm2 ...

Only the additional parameters will be shown in the following sections:


9.1.1 Backup
---------------
/PLUGIN=backup  [/file=<filename>]
    <filename> is the name of the file to be created

This will save the current configuration to the specified file.
The resulting file may be used as input to the Restore command-line option on
the same or different workstation (regardless of operating system).

The location of the configuration to be saved is determined by the property:
    com.ibm.iaccess.AcsBaseDirectory
which is located in the AcsConfig.properties file.

This function is equivalent to File->Export from the main GUI.


9.1.2 Restore
----------------
/PLUGIN=restore /file=<filename>
    <filename> is the location of the file created by Backup

This will restore a saved configuration from the specified file. Any existing
configuration not in the specified file will be lost.

The location of the restored configuration is determined by the property:
    com.ibm.iaccess.AcsBaseDirectory
which is located in the AcsConfig.properties file.

This function is equivalent to File->Import from the main GUI.


9.1.3 Certdl
--------------
/PLUGIN=certdl  /SYSTEM=<system>

Downloads a certificate authority (CA) from the specified IBM i system and stores
it in the user's local trust store. This is required for server authentication
with SSL.

This function is found from the main GUI by selecting System Configurations, Edit,
on the General tab.


9.1.4 Cfg
------------
/PLUGIN=cfg     /SYSTEM=<system> [/ipaddr=<frequency>] [/userid=<userid>]
                                 [/ssl=<switch>]
                                 [/5250path=<path>]
                                 [/del]  [/r]

    /SYSTEM     - name of the system
    /ipaddr     - when a connection is requested, this value determines whether or
                  not a lookup of the IP address will occur. Valid frequencies
                  are:
                      ALWAYS - lookup IP address for each connection
                      HOURLY, DAILY, WEEKLY - lookup IP address if the amount of
                          time has elapsed since the last lookup
                      IP address - if an IP address is specified, the lookup
                          frequency is assumed to be NEVER
    /userid     - user id for a user
                  may also be set to the following values:
                      *PROMPTALWAYS - prompts at least once for each connection
                      *KERBEROS     - use Kerberos principal name, no prompting
    /ssl        - switch is 0 to turn SSL mode off, or 1 to turn it on
    /5250path   - path to 5250 emulation profiles
                  The /5250path may be set from the main GUI using 5250 Session
                  Manager and then File->Change Directory...
    /del deletes existing configuration
    /r   replaces existing configuration

This allows various configuration options to be set from the command-line.
These options may also be set from the main GUI using System Configurations.


9.1.5 Dump
----------
/PLUGIN=dump

Requests all running processes within the product to dump their threads.  This
information will be used by IBM service to provide problem support.

The logs generated may be accessed from the main GUI by:
    Edit-Preferences
    Local Settings tab
    Dumps Directory

This function is equivalent to Tools->Generate Service Logs from the main GUI.


9.1.6 Medic
-----------
/PLUGIN=medic

Packages up the existing logs and thread dumps into a zip file that can be sent to
IBM for service.

The resulting zip file may be accessed from the main GUI by:
    Edit-Preferences
    Local Settings tab
    Service Directory

This function is equivalent to Tools->Package Service Logs from the main GUI.


9.1.7 Log
------------
/PLUGIN=log  /LEVEL=<Level>
                <Level> is one of the following supporting logging levels:
                OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINEST

This plugin enables the user to toggle their logging level from the command-line.

The logging level may also be set from the main GUI by:
    Edit->Preferences
    General tab
    Logging level


9.1.8 Logon
--------------
/PLUGIN=logon    /SYSTEM=<system> /USERID=<userid> /PASSWORD=<password>
                    /C clears the cache [optional]

This command will cache the user id and password which can be used to prevent
password prompting.


9.1.9 props
--------------
/PLUGIN=props

Brings up the same GUI panel as Edit->Preferences from the main GUI.


9.1.10 Maint
------------
/PLUGIN=maint [/<options]

Valid options are:
    /killdaemon     - ends daemon threads.
                      Same as Tools->Reset for Maintenance from main GUI
    /clearpwcaches  - clears all cached passwords
    /clearjarcache  - clears the products jar cache
    /clearlogs      - clears the Logs Directory at Edit->Preferences
                      Local Settings tab from the main GUI
    /cleardumps     - clears the Dumps Directory at Edit->Preferences
                      Local Settings tab from the main GUI
    /clearsvcdir    - clears the Service Directory at Edit->Preferences
                      Local Settings tab from the main GUI
    /clearsettings  - clears all settings for current user




9.1.11 Ping
--------------
/PLUGIN=ping /SYSTEM=<system> [options]
    Options include:
        /SSL=<1/0>        Turn SSL on or off
        /SERVERAUTH=<1/0> Turn SSL Server authentication on or off (default is off)
                          This option is disregarded if not testing SSL
        /GUI=<1/0>        Toggle GUI window on/off (default is off if launched from
                          command-line)
        /PORTS=<port1,port2> A comma-separated list of ports to test. It can be
                numbers or service names (e.g. /PORTS=as-signon,as-sts). If not
                specified, a default set of ports is tested.
                Specifying .CONSOLE will check ports 449, 3001, 3002,
                2300 and 2323
        /TIMEOUT=<seconds>   Specify a timeout value, in seconds.

This plugin checks the connectivity to the IBM i by opening a connection to the
appropriate port.  If verifying an SSL connection, an SSL handshake is attempted.
If it is launched from the main GUI, or invoked with /GUI=1, this plugin displays
a dialog.  If launched from the command-line without /GUI=1, output is sent to
the console.

By default, the following services are checked:
    as-central, as-rmtcmd, as-database, as-dtaq, as-file, as-netprt, drda,
    as-signon

This function can be launched from the main GUI by:
    System Configurations
    select a system and then Edit
    General tab
    Verify Connection



9.1.12 Sm
------
/PLUGIN=sm

This plugin starts the 5250 Session Manager GUI.

This is equivalent to 5250 Session Manager from the main GUI.


9.1.13 5250
-------------
/PLUGIN=5250 /SYSTEM=<system> [/<options>]

This plugin starts a 5250 emulator to the specified system.
This function is equivalent to 5250 Emulator from the main GUI.

Valid options are:
    /title=<title>  - session name
    /wide           - use a wide screen size (27x132)
    /nosave         - do not save settings on exit
    /prompt         - force the configuration dialog to appear
    /port=<port>    - port number
    /ssl            - connect using secure sockets
    /sso            - bypass signon screen
    /kerberos       - Use kerberos to get a license
    /width=<width>  - initial width of the emulator window
    /height=<height>- initial height of the emulator window
    /xpos=<xpos>    - initial x-coordinate position of the top-left corner of the
                      emulator window
    /ypos=<ypos>    - initial y-coordinate position of the top-left corner of the
                      emulator window


9.1.14 DTGui
-----------
/PLUGIN=dtgui

This plugin starts the main GUI for Data Transfer.

This function is equivalent to Data Transfer from the main GUI.


9.1.15 Download
------------------
/PLUGIN=download /file=<filename> [/userid=<userid>]

    /file     - file with the .dtfx extension that was created from a previous
                Data Transfer download
    /userid   - user id to use when connecting to the target system

The plugin enables the user to run a previously saved Data Transfer download.

Data Transfer is also available from the main GUI by selecting Data Transfer.


9.1.16 Upload
----------------
/PLUGIN=upload /file=<filename> [/userid=<userid>]

    /file     - file with the .dttx extension that was created from a previous
                Data Transfer upload
    /userid   - user id to use when connecting to the target system

The plugin enables the user to run a previously saved Data Transfer upload.

Data Transfer is also available from the main GUI by selecting Data Transfer.




9.2 File Associations
---------------------
Some configuration files generated by IBM i Access Client Solutions are supported
from the command-line when they are provided as the first and only parameter.
When these files with specific file extensions are provided as the first
parameter, IBM i Access Client Solutions will associate the file with the function
to be invoked and provide the file as input to that function.

The following extensions have file association support:
    .hod    - 5250 emulator session profile
    .bchx   - multiple session emulation profile
    .dtfx   - Data Transfer download request
    .dttx   - Data Transfer upload request

Command-line examples:
    acslaunch_xxx dt_download_file.dtfx - runs the saved download operation
    acslaunch_xxx dt_upload_file.dttx   - runs the saved upload operation
    acslaunch_xxx system_lp13ut20.hod   - starts a 5250 session to the system
where acslaunch_xxx is the command-line syntax used for starting the product. See
section 7.3 Starting the Product (using the command-line).

These supported command-line file associations enable the user to manually
set up operating system (OS) specific file associations.  Since file associations
are platform dependent, the steps required depend on the OS.

The reason you may want to consider setting up file associations for your OS is so
you have the ability to double-click a file (of one of the above supported file
types) to start the designated function.

The following sections provide some examples of setting up file associations for
some operating systems.


9.2.1 File Associations (for Windows XP)
----------------------------------------
1. Locate a file you want to associate that contains a supported extension (e.g.
   .hod, .bchx, .dtfx, or .dttx)
2. Right-click the file to open it.  A dialog should appear asking you how you
   want to Open the file.  Take the option to Select a program from a list.
3. Take the option to Browse
4. Locate the IBM i Access Client Solutions binary file that is in the
   Start_Binaries sub-directory that is appropriate for your hardware
   architecture.  Double-click it or select the option to Open it.
5. Click the option to Always use the selected program to open this kind of
   file.
6. Click OK

The appropriate IBM i Access Client Solution function will now run when you
double-click files with this type.


9.2.2 File Associations (for Linux)
------------------------------------------
The steps required for setting file associations will depend on the Linux
distribution and the desktop environment being used.  In general, the steps
required will be similar to the above steps used for Windows.
1. Locate a file you want to associate that contains a supported extension (e.g.
   .hod, .bchx, .dtfx, or .dttx)
2. Right-click the file. Look for options or properties that allow you to
associate a program with the file.
3. Associate the file and/or its extension with the appropriate IBM i Access
Client Solutions launch script or binary file.


9.2.3 File Associations (for Mac OS X 10.6.8)
---------------------------------------------
In order to use File Associations on a Mac, the file type must be associated with an
application.  You will need to create an application bundle that launches IBM i
Access Client Solutions.  See section 9.2.3.1 Creating an Application Bundle.

9.2.3.1 Creating an Application Bundle (for Mac)
------------------------------------------------
One way to create an application bundle that launches IBM i Access Client Solutions
is to use the Automator application that comes with Mac OS X.  The following steps
provide an example of how to do this:
   1. Go Applications
   2. Start the Automator application
   3. Select Application for the workflow template.
   4. Under Actions select Utilities
   5. double-click Run Shell Script
      a Run Shell Script panel should appear in the workflow area
   6. for "Shell:" use /bin/bash
      for "pass input:" select "as arguments"
   7. delete all provided commands in the shell and replace with the following line:
        <path>/<launcher> "$@" &
      where <path> is the location to the script or binary file
      where <launcher> is the name of the script or binary file
      For example:
        /User/my_id/Start_Scripts/Linux_Mac_Other/acslaunch.command  "$@" &
          OR
        /Users/my_id/Start_Binaries/Mac_i386-32_x86-64/acslaunch_mac "$@" &

   8. Save the application to some location.
  
This application bundle may be used:
   1. for starting the main IBM i Access Client Solutions GUI with a double-click
   2. from the command-line to start IBM i Access Client Solutions using
      any of its supported command-line options
        e.g. open -a <application_bundle> --args <command-line options>
   3. for creating file associations (see next section)

  
9.2.3.2 Create File Associations (for Mac)
------------------------------------------
1. Use Finder to locate a file you want to associate that contains a supported
   extension (e.g. .hod, .bchx, .dtfx, or .dttx)
2. Select the file and then File->Get Info
3. Under the "Open with:" option select Other
4. Browse to the location where you saved the application bundle you created
   (see section 9.2.3.1 Creating an Application Bundle).
5. Select the application.
6. Check the box to Always Open With.  Select Add.
7. Back at "Open with:" select Change All.  Select continue to any dialog.

The appropriate IBM i Access Client Solution function will now run when you
double-click files with this type.


9.3 Changing Configuration Location
-----------------------------------
By default, each user will have their own unique location for their configuration.
The configuration location can be changed by setting the
com.ibm.iaccess.AcsBaseDirectory property in the AcsConfig.properties file.

The AcsConfig.properties file exists in two locations when the product is shipped.
It is contained inside the acsbundle.jar file.  For convenience, it is also
provided in the product zip archive file and will be in the same directory as
acsbundle.jar when the zip archive is unpacked.

During start-up, the product will only use the first AcsConfig.properties file
it finds.  It first checks the current working directory.  If AcsConfig.properties
is not found in the current working directory, it will use the one inside
acsbundle.jar.

You may choose to update AcsConfig.properties in acsbundle.jar with a custom
configuration.  If you do, make sure the current working directory does not
contain an AcsConfig.properties file or it will get used instead.

This provides the flexibility of having all users use the same AcsConfig.properties
file inside acsbundle.jar while also providing the flexibility for an individual
user to override the configuration location by having their own
AcsConfig.properties file in their current working directory.

There are primarily three ways you may choose to set the property
com.ibm.iaccess.AcsBaseDirectory within the AcsConfig.properties file:
1. local configuration for each user
2. shared configuration for multiple users
3. local configuration on portable media

Here are examples of each:

Example 1: local configuration for each user (default)
    com.ibm.iaccess.AcsBaseDirectory=
When AcsBaseDirectory is not set, the configuration defaults to a platform
dependent path for the user.
This is the default setting for IBM i Access Client Solutions.

Example 2: shared configuration for multiple users
    com.ibm.iaccess.AcsBaseDirectory=X:/Shared_Network_drive/config_directory
Setting AcsBaseDirectory to an absolute path allows the configuration to
be shared by multiple users that are using the same AcsConfig.properties
file or whose AcsConfig.properties file contains the same path.
Hint: When setting it to an absolute path, try using / as a directory separator
even on Windows operating systems.

Example 3: local configuration on portable media
    com.ibm.iaccess.AcsBaseDirectory=.
Setting AcsBaseDirectory to . sets the configuration location to the
current working directory.  This setting may be useful for cases when you
want the configuration on portable media.  Since the absolute path of the
portable media will vary depending on the system where it is being used,
this setting allows the configuration to be relative to the current working
directory.


9.4 Other Deployment Options
----------------------------
If you have several end users and would like an easy way to deploy this product
and any future updates, here are some ideas you may want to consider:
   - Install the product in a single location where it can be accessed by
     several users.
   - If you have a web server, you may want to consider using Web Start.
     See http://java.com/en/download/faq/java_webstart.xml  

9.5 Customized Packages
-----------------------
IBM i Access Client Solutions provides system administrators the capability to
create customized packages with specific functions removed.

<Details available in a future update>


10.0 Service Diagnostics
------------------------
If you encounter a problem which requires IBM service, your IBM service
representative may direct you to do one or both of the following:
From the main IBM i Access Client Solutions GUI:
   - select Tools->Generate Service Logs
     This performs the same function as the command-line option in section
     9.1.5 Dump.  This function should normally be done immediately after
     the failure.  Depending on the problem, your IBM service representative
     may direct you to do this multiple times.
   - select Tools->Package Service Logs
     This performs the same function as the command-line option in section
     9.1.6 Medic.  This function gathers details about the workstation
     environment and packages the service logs into a zip archive that can be
     sent to IBM.


11.0 Frequently Asked Questions (FAQ)
-------------------------------------

Q1    When I try to start IBM i Access Client Solutions I get the following error:
      class cannot be loaded: java.lang.UnsupportedClassVersionError
A1-1  You need to use JDK 6.0 or higher.  See section 3.0 Prerequisites

Q2    When I try to start the product using one of the provided scripts or binary
      files from a shell or terminal session, I get the following error:
         Permission denied
A2-1  Check the file permissions of the file to make sure you have execute
      permission.   See section 6.0 File Permissions.

Q3    When I double-click on one of the provided files to start the product,
      nothing happens.
A3-1  Java may not be installed.   See section 3.0 Prerequisites
A3-2  The file you are using to start the product may not have execute
      permission.  See section 6.0 File Permissions.
A3-3  There may be problems with your environment.  To see what errors may be
      occurring, try running the provided file from a command line.
      See section 7.3 Starting the Product (using the command-line).

Q4    I want to use one of the binary files to start the product, but I get the
      following error:  "Error loading Java module."
A4-1  The binary was unable to locate the home directory of the java installation.
      Please verify java is installed.   See section 3.0 Prerequisites.
A4-2  Section 7.1.1 Starting the Product (using a binary file) - Additional Options
      contains additional methods for starting the product using a binary file. 

Q5    After I set the JAVA_HOME environment variable, the binary file I use to
      start the product works from a command-line, but does not work when I
      double-click the file.
A5-1  The JAVA_HOME environment variable may not be visible from the file manager
      you are using when you double-click the file.  Setting environment variables
      varies across operating systems and so does their visibility.  Try setting
      the JAVA_HOME environment variable as a system environment variable for your
      operating system.  Your operating system may refer to system environment
      variables as global environment variables.
      After setting the JAVA_HOME environment variable, close and reopen your
      file manager and try to double-click the binary file again.

Q6    When I double-click on one of the provided files to start the product, a
      text editor displays the file.
A6-1  Make sure you are using a script that has a file extension your operating
      system recognizes.
A6-2  Try one of the other scripts.
A6-3  Change the program that opens the file.
A6-4  Check the file permissions of the file to make sure you have execute
      permission.   See section 6.0 File Permissions.

Q7    When I double-click on one of the provided files to start the product, I am
      prompted for which program should be used to open the file.
A7-1  Make sure you are using a script that has a file extension your operating
      system recognizes.
A7-2  Set the program that opens the file to something compatible with the script
      or binary file you are using.  For example, Terminal (on Mac).
A7-3  Check the file permissions of the file to make sure you have execute
      permission.   See section 6.0 File Permissions.

Q8    When I start IBM i Access Client Solutions on a Mac from Finder, a
      terminal session pops up and does not go away even after ending
      IBM i Access Client Solutions.
A8-1  To eliminate the terminal session from popping up, you will need to create
      an application bundle.
      See section 9.2.3.1 Creating an Application Bundle (for Mac).  Then start
      the product using the application bundle.
    
Q9    What is the best way to start the product?
A9-1  You may start the product with any of the three methods in section
      7.0 Starting the Product using either the scripts, binaries or the
      command-line.  Any method that works in your environment is acceptable.

Q10   Why are there both scripts (Start_Scripts) and binaries (Start_Binaries)
      for starting the product?
A10-1 The scripts are not operating system specific and provide a more generic
      way to start the product than the binary files.
A10-2 Some operating systems require binaries when defining file associations.
      For convenience, binaries have been provided for some platforms.
A10-3 Some environments may have firewalls that restrict access to portions of
      IBM i Access Client Solutions.  For convenience, binaries have been
      provided to make it easier for system administrators to authorize access.

Q11   After installing JDK 6.0 (or higher), I am still getting the following
      error:
      class cannot be loaded: java.lang.UnsupportedClassVersionError
A11-1 The default version of java being used on your workstation is prior to
      JDK 6.0.  You will need to use an option that explicitly specifies the
      path to the Java home for JDK 6.  See section 7.1.2 Finding the Java
      Home Path.  Use the Java home path for one of the methods described in
      either of the following sections:
      7.1.1 Starting the Product (using a binary file) - Additional Options
      7.3 Starting the Product (using the command-line)
     
Q12   I am not able to import customized keyboard mapping files (.kmp) from
      my Windows 5250 emulator sessions.
A12-1 IBM i Access Client Solutions does not currently support importing .kmp
      files from Windows 5250 emulator sessions.  Importing 5250 session
      profiles (.ws) is supported.

Q13   Keyboard customization for the 5250 emulator is a lot different than it
      was on Windows.  Do you have any suggestions?
A13-1 Keyboard mapping is divided into categories.  From an emulator session:
      Click Edit > Preference > Keyboard, or click the Remap button on the
         toolbar.
      Click the Key Assignment tab.
      Select a Category.  Default key mappings will appear under the
         "Host Functions" and the "Menu Commands" categories.
      Select the function you want to assign.
      Click Assign a Key.
      On your keyboard, press the key (or key combination) you want to assign
         to this function.
A13-2 For help on custom key mappings:
      Click Edit > Preference > Keyboard, or click the Remap button on the
         toolbar.
      Select the Help button.

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS