5733XJ1 IBM i Access Client Solutions The contents of this document were last updated on: March 20, 2014 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 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 9.6 Migrating from IBM i Access for Windows 9.7 Key Management 9.8 Data Transfer Support for Excel and Calc Spreadsheets 9.9 Establishing a Console Connection to IBM i 10.0 Service Diagnostics 11.0 Frequently Asked Questions (FAQ) 12.0 Update History 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. Also available are two optional packages which include middleware for using and developing client applications for Windows and Linux: IBM i Access Client Solutions - Windows Application Package IBM i Access Client Solutions - Linux Application Package Customers using IBM i 6.1 or IBM i 7.1 can acquire IBM i Access Client Solutions by downloading it from the Entitled Software Support (ESS) website under 5761-SS1 or 5770-SS1. Customers can acquire media by ordering 5761-SS1 or 5770-SS1 refresh feature 6288. The physical media for IBM i Access Client Solutions does not contain the optional Windows and Linux Application Packages. Those packages are only available from the Entitled Software Support (ESS) website. The physical media contains a runnable version of the product which allows you to run the product directly from the CD. The physical media also includes a zip archive of the product which can be copied and extracted to a location of your choice. For additional information visit: http://www.ibm.com/systems/power/software/i/access/solutions.html For the latest information about IBM i Access Family products visit: 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 - Printer Output provides an interface that allows you to view files in the IBM i output queues and also provides the capability to download these files to your client system. - a Virtual Control Panel with a graphical interface to the IBM i operation panel - 5250 emulation for LAN, HMC and FSM consoles - consolidation for hardware management interface configurations including ASMI, IVM and HMC - launch capability to IBM Navigator for i using your default browser The optional Windows Application Package includes: - connectivity to DB2 for i using ODBC, .Net and OLE DB - Programming Toolkit for accessing IBM i system objects - Support for TLS/SSL connections - AFP printer driver The optional Linux Application Package includes an ODBC driver for accessing DB2 for i and supports full 64-bit ODBC data types. 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 SSL connections, load and apply the appropriate IBM i release specific PTF for your system: SI45601 - 5.4 SI45248 - 6.1 SI45610 - 7.1 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_Programs - 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 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 Mac_Application - directory containing an application bundle for Mac Linux_Application - directory containing an application bundle for Linux Icons - directory containing files which can be used as icons properties - directory containing product version information 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 CD or USB flash drive. Copy the zip archive to the desired location. Then, unpack the zip archive using any zip utility of your choice. Technical Note: Some archive utilities do not preserve all the saved file attributes. For example, on Mac and Linux platforms, the unzip command is usually a better choice than the jar command. For additional information, see section 6.0 File Permissions. 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 binary files or scripts 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 binary files or scripts, 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 To change the permissions of a file, you can use the following command: chmod For example: chmod a+rx ...would add read and execute permission for everyone chmod 755 ...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 binary file or script as described below, the binary file or script must be in the directory structure contained in the zip archive. For convenience, you may also copy/move the binary file(s) and/or scripts for your platform(s) to the same directory where the acsbundle.jar exists. 7.1 Starting the Product ---------------------------------------------- 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_Programs 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 - 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 - 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 Help->About The java.home path is displayed on this panel. 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 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 /acsbundle.jar where is the location to the product's executable jar file (e.g. java -Xmx1024m -jar V:/some_location/acsbundle.jar or java -jar V:/some_location/acsbundle.jar where 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 programs or scripts from the command-line. For example: /Product/Location/Start_Programs/Linux_x86-64/acslaunch_linux-64 /Product/Location/Start_Programs/Mac_i386-32_x86-64/acslaunch_mac C:\Product\Location\Start_Programs\Windows_x86-64\acslaunch_win-64.exe 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. If you do not have a configured LAN or HMC console, see section 9.9 Establishing a Console Connection to IBM i. 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=] 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= 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= 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. 9.1.4 Cfg ------------ /PLUGIN=cfg /LIST /LIST - list configured systems with their connection options /PLUGIN=cfg /SYSTEM= [/ipaddr=] [/userid=] [/ssl=] [/5250path=] [/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 If no options are specified, this function is equivalent to the following function from the main GUI: Tools->Generate Service Logs Valid options are: /heapdump - performs the above plus a dump of the JVM heap 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= 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= /USERID= /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 [/] Valid options are: /killdaemon - ends daemon threads. Same as Tools->Reset for Maintenance from main GUI /clearpwcaches - clears all cached passwords /clearjarcache - clears the product 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 If no options are specified, no actions will be performed. 9.1.11 Ping -------------- /PLUGIN=ping /SYSTEM= [] Options include: /SSL=<1/0> Turn SSL on or off /ACCEPTALLCERTS=<1/0> Whether or not to automatically add all SSL certificates to the trusted set (when using SSL). /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= 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 a list of console specific ports. /TIMEOUT= 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= [/id=] [/] This plugin starts a 5250 emulator to the specified system. This function is equivalent to 5250 Emulator from the main GUI. /id= - sets the short session id Valid options are: /name= - session name /wide=<1/0/true/false> - use a wide screen size (27x132) /fullscreen<1/0/true/false> - use the entire screen /nosave=<1/0/true/false> - do not save settings on exit /prompt=<1/0/true/false> - force the configuration dialog to appear /port= - port number /ssl=<1/0/true/false> - connect using secure sockets /sso=<1/0/true/false> - bypass signon screen /kerberos - Use kerberos /width= - initial width of the emulator window /height= - initial height of the emulator window /xpos= - initial x-coordinate position of the top-left corner of the emulator window /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 [/userid=] [/file=] [ ...] /userid - user id to use when connecting to the target system /file - file with the .dtfx extension that was created from a previous Data Transfer download. Multiple files may be specified with or without this keyword. 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 [/userid=] [/file=] [ ...] /userid - user id to use when connecting to the target system /file - file with the .dttx extension that was created from a previous Data Transfer upload. Multiple files may be specified with or without this keyword. 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.1.17 CLDownload ---------------- /PLUGIN=cldownload /system= [/userid=] {/hostfile= | /sql="statement"} {/clientfile=. | /display} /userid - user id to use when connecting to the target system /hostfile - Source library and file on the IBM i system for the download e.g. /hostfile=QIWS/QCUSTCDT /sql - specify an SQL statement e.g. /sql="select CUSNUM,LSTNAM,INIT,ZIPCOD from QIWS/QCUSTCDT" /clientfile - Target file location for the download. The format of this file will be determined by the specified extension (for example, .csv .ods .xlsx .xlsx) If the file extension is not specified or is of a type not supported, the data will be formatted as a .csv file /display - write the output to the terminal The plugin enables the user to run a simple download of an entire file from the command line. 9.1.18 Console ------------- /PLUGIN=console /SYSTEM= This plugin starts a 5250 console to the specified system. This function is equivalent to 5250 Console from the main GUI. 9.1.19 VCP ------------- /PLUGIN=vcp /SYSTEM= This plugin starts a Virtual Control Panel to the specified system. This function is equivalent to Virtual Control Panel from the main GUI. 9.1.20 L1C ------------- /PLUGIN=l1c /SYSTEM= This plugin launches a browser to IBM Navigator for i using the specified system and port 2001. This function is equivalent to Navigator for i from the main GUI. 9.1.21 SPLF ------------- /PLUGIN=splf /SYSTEM= This plugin displays the Printer Output GUI for viewing and downloading spool files from the IBM i. This function is equivalent to Printer Output from the main GUI. 9.1.22 KEYMAN ------------- /PLUGIN=keyman This plugin displays the Key Management tool. This function is equivalent to Tools->Key Management from the main GUI. 9.1.23 RMTCMD ------------- /PLUGIN=rmtcmd /SYSTEM= /CMD="" This plugin sends a CL command to the specified system. This function is only available from the command line. Hint: The CL command will need to be in quotes to avoid spaces from breaking up the command. 9.1.24 PWCHANGE ------------- /PLUGIN=pwchange /SYSTEMS= This plugin changes the password on the specified systems. It prompts the user for a userid, old and new passwords. This function may also be used from the main GUI by selecting the Passwords tab from Edit->Preferences 9.1.25 MIGRATE ------------- /PLUGIN=migrate /