open lab - schedschd.ws/hosted_files/commons17/74/acslab_170174.pdf · open lab: hands on with ibm...

70
1 Open Lab: Hands On with IBM i Access Client Solutions Session ID: 170174 Agenda Key: 43AB & 45AB – St. Croix 1 Speaker Names: Wayne Bowers ([email protected]) 2017 COMMON Annual Meeting May 7 - 10, 2017 Orlando, FL

Upload: buitu

Post on 23-Apr-2018

237 views

Category:

Documents


11 download

TRANSCRIPT

Page 1: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

1

Open Lab:

Hands On with IBM i Access Client Solutions

Session ID: 170174

Agenda Key: 43AB & 45AB – St. Croix 1

Speaker Names:

Wayne Bowers ([email protected])

2017 COMMON

Annual Meeting

May 7 - 10, 2017

Orlando, FL

Page 2: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

2

Lab Objective

Following this lab, attendees should be able to perform the following tasks:

• Deploy and Launch the product.

• Launch and configure 5250 display sessions

• Perform basic Data Transfer tasks

• Perform migration steps for both Data Transfer and 5250

• Interact with the Printer Output and Integrated File System functions

• Introduced to the Run SQL Scripts capability

Introduction IBM i Access Client Solutions is a member of the IBM i Access family, designed to meet the

marketplace’s need for platform independence, lower maintenance costs, and a higher degree of flexibility. This lab is designed to give you a hands-on first look at this exciting offering.

Page 3: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

3

Task 1: Expand the product image

This product will be distributed from IBM in the form of a .zip file. Expanding this zip file to your file system is the first step to getting started.

1. On your lab workstation browse to C:\ACSLab\ This is where we have put a distribution of the Access Client Solutions product, along with other files that will be used during this lab.

2. Right-click on “IBMiAccess_v1r1.zip”, go to the “7-zip” submenu, and select “Extract to IBMiAccess_v1r1”

Page 4: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

4

3. Observe that a new directory is created, named “IBMiAccess_v1r1.”

4. Browse into the new “IBMiAccess_v1r1” directory. Observer the following files:

Leave this folder open as it will be used in the following tasks.

Page 5: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

5

Task 2: Deploying to the Workstation

IBM i Access Client Solutions is very flexible in how it can be deployed to and launched from the user’s desktop. We will look at several of these approaches during this Task.

First, one can launch the product from wherever it resides: IBM i Access Client Solutions provides several Operating System specific executables to launch the product. These are intended to be used by an end user to launch the product directly from wherever it may reside.

1. From the already open file browse window that should be showing you the contents of “C:\ACSLab\IBMiAccess_v1r1\”. Open the ”Start_Programs” folder.

2. Browse into the “Windows_i386-32” folder (Even though these lab workstations are using Windows 7 64bit operating system, the java runtime environment and the Microsoft office that we will be interacting with are 32bit so we will want to launch in a 32bit environment.)

3. You will find a file named “acslaunch_win-32.exe” Double-click to execute.

4. When the product is launched you will first see startup information similar to this:

Page 6: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

6

5. If this is the first time IBM i Access Client Solutions has been executed on this workstation, you will be prompted to accept a license agreement. The “Yes” button will not be active until the text of the license agreement is scrolled down to the bottom.

6. Then you will see the main product user interface window.

Page 7: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

7

7. Open Help -> About and see the location of the product is “C:\ACSLab\IBMiAccess_v1r1\ascbundle.jar” Do not do anything else with the product at this time, close the window to prepare for the next exercise.

Use the install scripts shipped with the product. These are intended to be used to help deploy the product to individual workstations. First we will look at calling the installer as a normal end user. This would be similar to your IBM i Access for Windows / Client Access users doing their own install from the DVD.

1. Open a file browse window and browse to “C:\ACSLab\IBMiAccess_v1r1\Windows_Application”

2. First we need to uninstall any IBM i Access Client Solutions deployment already on this workstation. Double click the “uninstall_acs.js” to run the uninstall script. When the message says the product has been removed, click OK.

3. Now we will install IBM i Access Client Solutions to the local Windows user. Double click the “install_acs_32.js” to run the install script.

4. The user will now be prompted for what functions they want to use like:

Select the Yes button.

Page 8: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

8

5. When prompted with the following option select the No button. If Yes is selected any Access for Windows PC5250 or Personal Communications sessions will be opened with IBM i Access Client Solutions.

6. Please note all of the functions that can be selected. For this lab please answer Yes to every option.

7. Click OK to the completion message:

8. There will now be an “IBM i Access Client Solutions” icon on the desktop. Double click that icon and the main IBM i Access Client Solutions user interface will open.

Page 9: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

9

9. Open Help -> About and see the location of the product is “C:\Users\<local windows user>\IBM\ClientSolutions\acsbundle.jar” Do not do anything else with the product at this time, close the window to prepare for the next exercise.

10. We need to uninstall any IBM i Access Client Solutions deployment we just did to prepare for the next steps. If not already open, Open a file browse window and browse to “C:\ACSLab\IBMiAccess_v1r1\Windows_Application”. Double click the “uninstall_acs.js” to run the uninstall script. When the message says “IBM i Access Client Solutions has been uninstalled.”, click OK.

Now we will look at pre-configuring the install as an Administrator. This would be similar creating a tailored install of IBM i Access for Windows that is ran on the user’s PC and they get the functions decided by the Administrator.

1. Navigate to Start -> All Programs -> Accessories, right click on Command Prompt and select Run as administrator.

2. In the Windows Command Prompt enter: cd C:\ACSLab\IBMiAccess_v1r1\Windows_Application

3. Now that we are in the correct directory we can call the install script, telling it we want to administer the image. Enter this command: install_acs_32.js /AdminConfig

4. When prompted, answer Yes to the following question:

If you respond with No, the process will be exited.

5. If the IBM i Access Client Solutions AcsConfig.properties file has already been modified you would want to respond No to the following question:

Page 10: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

10

As most will do, answer with Yes.

6. Now we must decide where the IBM i Access Client Solutions product will be ran from by answering this prompt:

Answer No to copy the product to the local Windows user at install time.

7. The administrator decides if they want to choose the functions to be deployed, or if the user will be asked at install time. Answer No to preset the install image for the functions to be deployed.

Page 11: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

11

8. Now the administrator will select the functions the users will be able to use. Press OK.

9. As before, for this lab, please answer Yes to every function. The following completion message will be received:

10. Close the Administrator: Windows Command Prompt and open another Command Prompt window. Do not “Run as administrator”

11. In the Windows Command Prompt enter: cd C:\ACSLab\IBMiAccess_v1r1\Windows_Application

12. Now that we are in the correct directory we can call the install. Enter this command: install_acs_32.js

13. You will see several commands being ran, but will not be prompted for anything and will be notified when the deployment has completed:

Page 12: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

12

14. Find the IBM i Access Client Solutions icon on the desktop and launch the Main User interface.

Page 13: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

13

Task 3: Creating a system configuration

You may want to create a stored system configuration, which will save login and connection preferences, and enable you to launch to system tasks directly from the product’s main GUI.

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Click on the “System Configurations” link in the “Management” Section

3. Wait until you see the following System Configurations dialog and Click the “New” button:

Page 14: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

14

4. On the Add New System screen, under the general tab, enter a system name “COMMON1.idevcloud.com” (or the system name provided by the lab instructor). The Description is optional. Feel free to do a Verify Connection. Do not click “OK” Yet.

Page 15: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

15

5. Select the “Connection” tab, select the option “Use default user name to prompt once for each system” and enter an user name of “acslab”. Click OK

Page 16: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

16

6. Observe that you now have a system configuration listed, and then Click Close to exit the System Configurations panel.

Page 17: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

17

Task 4: Launching/configuring a 5250 display session

There are two ways one can launch a 5250 session from the product GUI’s. First, one can launch from the main product GUI:

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3

3. In the “General” section, select “5250 Emulator”

Page 18: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

18

4. Log in if prompted using these credentials: User: acslab Password: acs17pwd

5. You should see a green screen emulation window. Close it to prepare for the next exercise. If asked to save the current configuration, Click No.

Page 19: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

19

Also, one can launch and configure sessions through the 5250 Session Manager:

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. From the “Management” section, select “5250 Session Manager”.

You will see the following:

Page 20: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

20

3. Click “New Display Session” You will see the following dialog:

4. Enter the destination address, COMMON1.idevcloud.com, in the “Destination Address” field. Click OK. Log in if prompted, using these credentials: User: acslab Password: acs17pwd

Page 21: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

21

5. Save this session, by clicking File->Save. Save the file as “COMMON1” in the default directory (do not navigate to a separate folder in the save dialog)

Page 22: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

22

6. Close the emulator window. Locate the 5250 Session Manager window. Observe that the

new session is visible in the “Configured Sessions” list, as in the following screen shot:

7. Click the saved session, click “Start” Observe that an emulator window is opened.

8. Keep this emulator open window open for the next task.

Page 23: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

23

Task 5: Configuring 5250 key mappings

They key mapping functionality of the new emulator is noticeably different from that of PC5250, especially with GUI appearance. This exercise lets you try it out

1. Open an emulator session (as in previous tasks) if you do not yet have one already open.

2. Click the “Communication” menu, and select “Configure”

3. Locate the “Keyboard” button at the bottom of the panel and click it:

Page 24: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

24

4. From the keyboard selection GUI (as shown in the following screen shot), select the “Menu Commands” category. Scroll down and select “Copy Append”.

Page 25: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

25

5. Select the “Assign a Key” button at the bottom. You will see a message asking you to “Press a Key” as in the following screen shot. Press <ctrl>+<shift>+J at the same time.

Page 26: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

26

6. Observe that the key has been mapped, as in the following screen shot.

Page 27: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

27

7. Click “Save As..” to save as either a File, or into the Current Session. Saving the updated keyboard mapping into a file provides the same function as IBM i Access for Windows PC5250. This mapping file can be shared between multiple session configurations. Saving the updated keyboard mapping into the current session makes the session more portable as it doesn’t require a separate file to have an updated keyboard mapping function. Select Current Session:

8. Close any 5250 configuration dialogs. Leave the display emulator open.

Task 6: Displaying a Session Watermark

Watermarks are a new feature introduced by the Host-On-Demand-based emulator. It allows you to have images or text displayed on the background of your emulation session.

1. Open an emulator session (as in previous tasks) if you do not yet have one already open.

2. Click the “Communication” menu, and select “Configure”

3. On the left hand navigator bar select “Screen” and then select the “Yes” radio button for Watermark in the Watermark Properties and click on the “Configure” button.

Page 28: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

28

4. Select the Text Watermark type. For Display Text enter in a text string like “ACSLab”. Select a Display text color and Font of your choice. Save your changes by selecting the “OK” button.

5. Then select the “OK” button on the Communication Configure panel. Finally, answer “Yes” session change and end communications dialog. The session will disconnect and reconnect and the watermark will be displayed as shown below.

Page 29: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

29

6. Make several changes to the Watermark configuration, especially with adjusting the Opacity. The 50% opacity shown here is likely much to obtrusive for normal use. Feel free to download, an image and setup an Image Watermark.

Page 30: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

30

Task 7: Using the Mouse Wheel

The ability to use the Mouse Wheel is a new feature introduced by the Host-On-Demand-based emulator.

1. Open an emulator session (as in previous tasks) if you do not yet have one already open.

2. Sign on to the session if not already signed on and enter the WRKACTJOB command which will display several pages of information.

3. Roll the mouse wheel and note that this now Pages Up/Down on the screen! This is enabled by default with the ACS 5250 emulator.

4. Let’s look at the Mouse Wheel configuration Options. From the Edit -> Preferences menu select “Mouse Wheel”.

5. As already experienced, the Mouse Wheel is enabled by default and the Wheel Up/Down by default are set to perform Page Up/Down. Rolling the Mouse Wheel with the Shift or Control keys held can be mapped to different options like Next/Previous Tab or a Function key for example.

6. Change the Shift and Control Wheel Up/Down functions to other functions and press “OK” and test those functions.

Page 31: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

31

Task 8: Using the Screen History feature

Screen history is a new feature introduced by the Host-On-Demand-based emulator . It allows you to see previous display screens from your display session

1. Open an emulator session (as in previous tasks) if you do not yet have one already open.

2. Click the “Communication” menu, and select “Configure”

3. On the left hand navigator bar select “Preferences” and then near the bottom of the main panel turn on “Screen History” as shown. Make sure that “History Screen Type” is “Traditional(Screen)”. Click OK to exit the 5250 Display configuration panel.

Page 32: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

32

4. Answer Yes to changing and ending the current session. Log in to the IBM i and perform tasks. Observe screen history at the bottom of the display, as in the following screen shot:

5. Interact with the Screen History Board. Double click on one of the screens. See that you can arrow through the recorded screen history. You can copy information off of the history screens.

6. Close the emulator window. Do not save.

Task 9: Using Tabbed 5250 sessions

Version 1 Release 1 Modification level 4 of IBM i Access Client Solutions released February 2015 added the ability to interact with multiple sessions in a tabbed view of a single emulator window and Version 1 Release 1 Modification level 5 released December 2015 made tabbed sessions the default view.

1. Open the 5250 Session Manager, if you have not already done so.

2. Select the saved COMMON1 session and click Start.

Page 33: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

33

3. Once the Signon Screen is displayed, from the “File” menu select “Run the Same” and note that the new session did not open in a new window, but instead now a tab bar is displayed and the 2 sessions are displayed in separate tabs.

4. From the “Edit” menu select “Preferences” and then “Tab Setup” as shown.

Page 34: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

34

5. From the Tab Setup panel, note that the option for “Open new sessions in a new tab” is selected by default. Also select “Always display the tab bar” as shown, and Press OK.

6. Click the red “x” on one of the tabs to close that session, and answer “Yes” to save the session. The 5250 screen will now always display a Tab bar as shown, even with just 1 session open.

Page 35: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

35

7. Click on the small tab with a + symbol in it to start another tabbed session.

8. If the number of tabs that are open will not fit on the tab bar, navigation arrows are displayed along with a number key for the number of sessions that are not displayed.

Page 36: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

36

9. More tabs can be interacted with at one time if the tabs are configured to be displayed on the side of the session instead of the top or bottom, but the session display area is compressed.

10. This is configured via the Tab Setup panel.

11. Session tabs can be undocked to be a standalone session by simply clicking the tab and dragging it outside of the current session window to the desktop. Note that the New Session tab is still displayed so new tabs can be started in this session Window. Undocked sessions can be docked again by clicking on the tab and dragging it to another tabbed window.

Page 37: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

37

Similarly, sessions can be attached or detached as a Tabs from the “Action” menu, “Tab” and “Attach As Tab” or “Detach Tab”.

12. Click the x in the upper right corner of the entire screen to close the tab group. Note the warning message that is displayed.

Select OK. Now you will be asked if the sessions should be saved. Select No to All.

Page 38: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

38

Task 10: Importing legacy 5250 profiles

The new Host-on-Demand emulator cannot directly run legacy workstation profiles (.WS profiles) that were created with PC5250 or IBM Personal Communications. However, it does provide an “import” function to migrate the legacy profiles to the new format

1. Open the 5250 Session Manager, if you have not already done so.

2. From the “Tools” menu, click “Profile Migration” (as in the following screen shot):

3. From the 5250 Emulator Profile Migration click on Add and browse to “C:\ACSLab\” and select “Common2.ws”. Double-click, or select the file and click “Open”.

Page 39: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

39

After the legacy session is added to the Files to Migrate, leave the Output Directory as the default of “Save to Session Manager directory” and press OK.

4. Observe that the session has been imported. It may be necessary to refresh the View.

5. Close all 5250 panels, leave the main user interface panel open.

Page 40: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

40

Task 11: Launching Data Transfer

This task will walk you through starting Data Transfer, and opening/running a saved request.

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3.

3. Under the “General” section, select “Data Transfer” (as in the following screen shot):

4. From the Data Transfer GUI, go to the “File” menu and select “Open…” Browse to and select “C:\ACSLab\Download_QCustCDT_Display.dtfx”. The request will be opened.

Page 41: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

41

5. Click “Start Transfer”

Page 42: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

42

6. Observe that your database information is displayed. Click “Cancel” to close the display:

7. Keep the Data Transfer window open for the next task

Page 43: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

43

Task 12: Migrating (and running) legacy Data Transfer request files

This task …

1. Launch Data Transfer (if you did not leave it running after the last task.)

2. From the “Actions” menu, select “Data Transfer Migration”, which will bring you to the following screen:

3. Click the “Add” button:

Page 44: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

44

4. In the file open dialog, browse to “C:\ACSLab” and select both “dtf_biff5.dtf” and “dtf_biff8.dtf”. Use the <shift> or <ctrl> key to select multiple files.

Page 45: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

45

5. Click “Open” (on the file open dialog from the previous step). Both .dtf files are now listed in the migration list (as in the following screen shot):

6. Leave the output directory option to the default (same as source directory) and click “OK”.

Page 46: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

46

7. You will see a message stating “Migration Complete”. Click “OK” for that message, leaving you with a migration summary, as shown in the following screen shot:

Page 47: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

47

8. The “green checkmark gear” icon indicates success. The “red x gear” indicates failure. Click the ‘+’ next to the failed file for more details. IBM i Access Client Solutions Data Transfer does not support the Biff5 file type.

9. Click “OK” to dismiss this dialog.

Page 48: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

48

10. Click “Cancel” to dismiss the “Data Transfer Migration” dialog. This should bring you to the Data Transfer window (as in the following screen shot):

Page 49: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

49

11. The “C:\ACSLab\dtf_biff8.dtf” file has now been migrated to “C:\ACSLab\dtf_biff8.dtfx”. Select the “File” menu and “Open..” Browse to “C:\ACSLab\dtf_biff8.dtfx”. If asked to save the old request, click “No”. The active tab should show the migrated download request, as in the following screen shot:

8. Note that the output device is a File. If desired, Click the “Details” button (to the right of the “Output device” field) to observe that the file type is “Microsoft Excel 97-2003 (.xls)”. Do not change file properties. Close the details dialog (if open).

Page 50: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

50

9. Click “Start Transfer”. Log on if necessary. You should see the success message shown in

the following screen shot. Select “Open File…” to view the file in Excel

10. Close Excel and Data Transfer. If asked to save any requests, click “No”

Task 13: Data Transfer to an Active Spreadsheet

The IBM i Access Client Solutions product allows for performing a Data Transfer where the results can be sent directly to, or the input can be read directly from an active Spreadsheet application. This task does a simple introduction to this capability.

1. Open a Microsoft Office -> Excel Spreadsheet or Book. Click to select a cell near the upper left hand corner, like B-4 for example.

2. If you have not already done so, launch the product using the IBM i Access Client solutions icon as outlined at the end of Task 2.

3. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3.

Page 51: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

51

4. Under the “General” section, select “Data Transfer” (as in the following screen shot):

5. When the Data Transfer user interface is displayed, select the ”From IBM i“ tab. Enter the File name of ”QIWS/QCUSTCDT”. Select the Output device of ”Active Excel Spreadsheet”.

Page 52: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

52

6. Click Start Transfer. You will receive an inquiry message when the data transfer has completed.

7. Click OK button on the inquiry message, then go and look at the open Microsoft Excel Book and you will see that the results from the Data Transfer were loaded into Excel. Note: This capability will only be supported with Microsoft Excel on the Microsoft Windows OS. The Open Office Calc Spreadsheet will be supported on Microsoft Windows and Linux OS.

8. Close Excel and Data Transfer. If asked to save any requests, click “No”

Task 14: Work with Printer Output

The IBM i Access Client Solutions product allows for user interaction with spooled files, including downloading to their local workstation. This task overviews these capabilities.

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3.

Page 53: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

53

3. Click on the “Printer Output” option under the “General” section in the left hand navigation area.

4. At this time the Printer Output interaction panel will be displayed. You will see that there are

a few spooled files that have been pre-created for this exercise.

Page 54: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

54

5. Under the “View” menu select the option to “View Active Tasks pane”

Page 55: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

55

6. Right click on one of the spooled files and select the option to “Download and View”

Page 56: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

56

7. Note the download progress on the right hand side in the Active tasks pane.

Page 57: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

57

8. When the download is completed the PDF file of the printed output will be displayed.

9. By default, when connecting to IBM i OS r7.1 or later, and the IBM Transform Services for i (5770TS1) product is installed, IBM i Access Client Solutions will default to downloading printer output in a PDF format. This can be changed to a Text format.

Page 58: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

58

10. Go to the “Edit” menu and select Preferences. Uncheck the “Use PDF format if available” option. Click the “OK” button.

Page 59: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

59

11. Right Click on a spooled file again and choose the option to “Download and View” again. You will see that the data is now presented in a text file format.

Page 60: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

60

12. Back on the Access Client Solutions Printer Output window, you will note on the bottom panel that the file was create as .txt.

Task 15: Integrated File System

The IBM i Access Client Solutions product Version 1 Release 1 Modification Level 6 released in August 2016 introduced a new Integrated File System function to provide an alternative to the IBM Navigator for i Integrated File System interaction.

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3.

Page 61: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

61

3. Click on the “Integrated File System” option under the “General” section in the left hand navigation area.

4. At this time the Integrated File System interaction panel will be displayed.

Page 62: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

62

5. Navigate to the directory /ACSLab and double click to open it. The following files will be listed:

6. Highlight one of the files by left clicking on it, then right click and select Download.

Page 63: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

63

7. Note the default Destination. Click Cancel.

8. Select Edit -> Preferences and change the Download Location from ‘Downloads folder’ to ‘Specify a location’ and either browse and select or type in C:\ACSLab. Click OK.

Page 64: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

64

9. Select and the right click on one of the files and select Download and note that the Destination is now the specified ‘C:\ACSLab’. Click OK to download the file. Note the messages indicating the successful download. Feel free to go and open the downloaded file.

10. Double click to open the upload folder. Then right click and select the option for ‘New Folder…’. Enter an unique folder name starting with ‘ACS_’, like the Example shown. Click OK.

Page 65: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

65

11. Double click to open your newly created ‘ACS_’ folder. Then right click and select Upload.

Specify to upload the same file that was previously just downloaded and click OK.

12. Note that the file was successfully uploaded.

Close the Integrated File System window.

Page 66: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

66

Task 16: Run SQL Scripts

The IBM i Access Client Solutions product Version 1 Release 1 Modification Level 5 released in December 2015 introduced a new Run SQL Scripts function to provide this commonly used capability as it is not available in the IBM Navigator for i interface that IBM i ACS relies on.

1. If you have not already done so, launch the product using the IBM i Access Client solutions icon on the desktop as outlined at the end of Task 2.

2. Select system “COMMON1.idevcloud.com” from the system dropdown menu. If the system is not present in the dropdown, configure it as outlined in Task 3.

3. Click on the “Run SQL Scripts” option under the “Database” section in the left hand navigation area.

4. At this time the Run SQL Scripts interaction panel will be displayed. Note the

informational messages on the Data Access connection information.

Page 67: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

67

5. Enter the following SQL Select statement: SELECT * FROM QIWS.QCUSTCDT And press the “Run Selected” ‘hourglass’ icon on the toolbar and note the results as shown here:

6. Another query you can attempt is: SELECT * FROM SYSTOOLS.GROUP_PTF_CURRENCY

Page 68: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

68

Congratulations! You have finished all of the tasks in this lab Exercise. Please let the Lab Instructors know that you are finished with this lab when you vacate your workstation so that they can clean it up for use by another team of participants.

Page 69: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

69

Special Notices This document was developed for IBM offerings in the United States as of the date of publication. IBM may

not make these offerings available in other countries, and the information is subject to change without notice.

Consult your local IBM business contact for information on the IBM offerings available in your area.

Information in this document concerning non-IBM products was obtained from the suppliers of these

products or other public sources. Questions on the capabilities of non-IBM products should be addressed to

the suppliers of those products.

IBM may have patents or pending patent applications covering subject matter in this document. The

furnishing of this document does not give you any license to these patents. Send license inquires, in writing,

to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA.

All statements regarding IBM future direction and intent are subject to change or withdrawal without notice,

and represent goals and objectives only.

The information contained in this document has not been submitted to any formal IBM test and is provided

"AS IS" with no warranties or guarantees either expressed or implied.

All examples cited or described in this document are presented as illustrations of the manner in which some

IBM products can be used and the results that may be achieved. Actual environmental costs and

performance characteristics will vary depending on individual client configurations and conditions.

IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other

IBM subsidiaries and divisions worldwide to qualified commercial and government clients. Rates are based

on a client's credit rating, financing terms, offering type, equipment type and options, and may vary by

country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal

without notice.

IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies.

All prices shown are IBM's United States suggested list prices and are subject to change without notice;

reseller prices may vary.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our

warranty terms apply.

Any performance data contained in this document was determined in a controlled environment. Actual

results may vary significantly and are dependent on many factors including system hardware configuration

and software design and configuration. Some measurements quoted in this document may have been made

on development-level systems. There is no guarantee these measurements will be the same on generally-

available systems. Some measurements quoted in this document may have been estimated through

extrapolation. Users of this document should verify the applicable data for their specific environment.

IBM, the IBM logo, ibm.com AIX, AIX (logo), AIX 6 (logo), AS/400, BladeCenter, Blue Gene,

ClusterProven, DB2, ESCON, i5/OS, i5/OS (logo), IBM Business Partner (logo), IntelliStation,

LoadLeveler, Lotus, Lotus Notes, Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld,

PowerPC, pSeries, Rational, RISC System/6000, RS/6000, THINK, Tivoli, Tivoli (logo), Tivoli

Management Environment, WebSphere, xSeries, z/OS, zSeries, AIX 5L, Chiphopper, Chipkill, Cloudscape,

DB2 Universal Database, DS4000, DS6000, DS8000, EnergyScale, Enterprise Workload Manager, General

Purpose File System, , GPFS, HACMP, HACMP/6000, HASM, IBM Systems Director Active Energy

Manager, iSeries, Micro-Partitioning, POWER, PowerExecutive, PowerVM, PowerVM (logo), PowerHA,

Power Architecture, Power Everywhere, Power Family, POWER Hypervisor, Power Systems, Power

Systems (logo), Power Systems Software, Power Systems Software (logo), POWER2, POWER3, POWER4,

POWER4+, POWER5, POWER5+, POWER6, POWER6+, System i, System p, System p5, System Storage,

System z, Tivoli Enterprise, TME 10, Workload Partitions Manager and X-Architecture are trademarks or

registered trademarks of International Business Machines Corporation in the United States, other countries,

or both. If these and other IBM trademarked terms are marked on their first occurrence in this information

with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks

Page 70: Open Lab - Schedschd.ws/hosted_files/commons17/74/ACSLab_170174.pdf · Open Lab: Hands On with IBM i Access Client ... Browse into the “ Windows_i386-32 ” folder (Even though

70

owned by IBM at the time this information was published. Such trademarks may also be registered or

common law trademarks in other countries. A current list of IBM trademarks is available on the Web at

"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml

The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are

trademarks and service marks licensed by Power.org.

UNIX is a registered trademark of The Open Group in the United States, other countries or both.

Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.

Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United

States, other countries or both.

Intel, Itanium, Pentium are registered trademarks and Xeon is a trademark of Intel Corporation or its

subsidiaries in the United States, other countries or both.

AMD Opteron is a trademark of Advanced Micro Devices, Inc.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States,

other countries or both.

TPC-C and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).

SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc,

SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs are trademarks of the Standard Performance

Evaluation Corp (SPEC).

NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.

AltiVec is a trademark of Freescale Semiconductor, Inc.

Cell Broadband Engine is a trademark of Sony Computer Entertainment Inc.

InfiniBand, InfiniBand Trade Association and the InfiniBand design marks are trademarks and/or service

marks of the InfiniBand Trade Association.

Other company, product and service names may be trademarks or service marks of others.