Home
i5/OS Links
i5/OS Utilities
i5/OS ODBC
z/OS Links
ISPF Utilities
ISPF C/S & WSA
ISPF Scrnsavers
Rexx
390/ILE/LE Cobol
Screen Cams
Saved Stuff
Dish Hopper
TVersity
Audio to Dish Hopper
Miracast
Slideshows

Resume Fun

Win 7 Setup

 

 

           Up

 

ISPF C/S  

Work Station Agent (WSA) Installation  

Win 7 Home Premium

 

  1. The sole purpose of this page is  to provide  examples of the ISPF Workstation Agent  and it is to be accepted ASIS with no warranties of any kind.

  1. The executable ISPGUINX does not work for a Win 7 install.  IBM has put out APAR OA17073 PTF UA to address the Win 7 install issue. You will have to contract your system programmers to see if APAR OA17073 PTF UA has been applied before you download from your system. If the APAR has been applied and it works you should be able to follow install instructions for Win XP and install.  Also, there is a know issue on Win 7 where orphan cmd.exe *32 start up when you issue a PC command from the mainframe, but what I have experienced so far, this causes no problems and when the WSA is shutdown all the orphan cmd.exe *32 go away. Win 7 runs in 64-bit mode but can also run 32-bit programs. The current WSA is a 32-bit designed to work on the Win x86 Architecture.    

  1. If the APAR does not fix the Win 7 install issue you can do the following and WSA will run on a WIN 7. *NOTE: I have installed WSA on my 2 HP Laptops both running Win 7 Home Premium and they work. I have not tried on Win 7 Enterprise or Pro.

  1. Notice on your Win 7 there are 2 Program File directories: Program Files (64-bit) and Program Files (x86). 

 

 

  1. You will have to copy the WSA directory  from a Win XP (32-bit) to your Win 7 Program Files (x86) directory. Locate the WSA directory on your Win XP. When I installed on my Win XP, I put in C:\A_WSA\. There should be 5 main objects: DBCS.TBL , DTWSA.DLL, MSG.TBL, SBCS.TBL, and WSA.EXE . If you have configured the Workstation Tool Integration on the mainframe or added entries to the WSA System Register there will be additional objects, copy all the objects. If you do not have a Win XP version, I have included a zip wsa.zip 

 

 

  1. Locate your Win 7 on your network and find the Program Files (x86) directory. Create a directory A_WSA or whatever you want to name it in the Program Files (x86) directory and paste all the objects you copied from Step 5. If you copied everything from the Win XP, all your Workstation Tool Integration and WSA System Register settings will be ready to use. Also, I right clicked WSA.EXE and put a shortcut on my desktop for easy access.     
        

 

  1. Also, right click WSA.EXE and click Properties, click Compatibility tab, click box Run this program in Compatibility mode for: and click the drop down box and select Windows XP (Service Pack 3), click OK.   

 

  1. You are now ready to use WSA, double click the WSA.EXE or shortcut and WSA will start and be displayed on your desktop. Once you make the connection from the mainframe to WSA, all will work as it did with Win XP. 

 

  1. Like I stated at the top, for some reason when you issue commands or start apps from the mainframe using WSA with Win 7, orphan cmd.exe *32 processes start, but these have not caused any problems for me and they go away when you close the WSA. 

 

 

 

 

 

Back Up Next

 

 

Last Updated 12/08/2013 11:32 AM by Rick Silvers contact me: rsilvers@mebtel.net