PSPSOCK Installation Instructions

This page gives installation instructions for our PSPSOCK ISeries sockets framework.

You may receive the PSPSOCK software in the following ways:
  • Direct download of PSPSOCK.zip - around 2.0MB - from a secure area of our Web site.
  • A single email attachment PSPSOCK.zip - around 2.0MB.
  • If a single email attachment of 2.0MB can not get through your firewall, a series of separate email attachments PSPSOCK.zip.001, PSPSOCK.zip.002......PSPSOCK.zip.006 each of which is around 400K in size. You concatenate these as described below to build a single PSPSOCK.zip file.

To install the software:

  • If you received separate email attachments (PSPSOCK.zip.001 through PSPSOCK.zip.006), detach these to your PC then open a Windows command prompt and enter the following command (all on one line):

    copy /B pspsock.zip.001 + pspsock.zip.002 + pspsock.zip.003 + pspsock.zip.004 + pspsock.zip.005 + pspsock.zip.006 pspsock.zip

    You should see a message like:

    PSPSOCK.zip.001 PSPSOCK.zip.002 PSPSOCK.zip.003 PSPSOCK.zip.004 PSPSOCK.zip.005 PSPSOCK.zip.006 1 file(s) copied.
  • Double-click on PSPSOCK.zip to open the file using WinZip or similar ZIP software. You will see that PSPSOCK.ZIP contains one file PSPSOCK.SAVF. Extract this file PSPSOCK.SAVF to your PC drive.
  • Transfer the SAVF up to your ISeries to end up with a SAVF called PSPSOCK (probably in QGPL library). If you use FTP to do this transfer, you need to pre-create an empty SAVF on the ISeries first then FTP into that. The FTP transfer also needs to be 'binary', not 'ascii'. If you do not want to use FTP, then you can transfer in a different way if your ISeries is mapped as a Windows network drive (please contact us if you need further help with this method).
  • On your ISeries, rename any current PSPSOCK library you may have e.g. to PSPSOCK2. This is so you can reinstate items in your current copy of the PSPSOCK library to the new copy of PSPSOCK. The PSPSOCK User Guide has more details on this.
  • On your ISeries, run RSTLIB SAVLIB(PSPSOCK) DEV(*SAVF) SAVF(QGPL/PSPSOCK)
  • If you are starting a 30-day trial of PSPSOCK: If we have not given you a license key for this (e.g. in an email), you can get one yourself here.
  • If you are already a user of PSPSOCK: Copy the contents of the PSPSLICKEY and PSPSUSR data areas from PSPSOCK2 into the new PSPSOCK library. If you ever forget/lose your license key, you can get it again yourself here.
  • Reinstate other items from the PSPSOCK2 library to the new PSPSOCK library. The PSPSOCK User Guide has more details on this.
  • Check the authority of the PSPSOCK library and the objects within it. Make sure that whoever is going to use it has enough authority.
  • A reasonable number of copies of the PSPSOCK library on offline media as part of your regular backup cycles are assumed, but you are still limited to the number of copies you have licensed - including backup and disaster recovery machines.
The SAVF contains SAVLIB LIB(PSPSOCK) with target OS/400 release of V5R2M0, so RSTLIB on that or any later release should work. If you encounter any problems using the PSPSOCK library objects, you can check the following sizes:
  • The SAVF on our source ISeries running V5R3 is 8,933,376 bytes.
  • The SAVF as transferred to our source PC via binary FTP is 8,976,000 bytes.
  • The PSPSOCK.zip file is 2,174,355 bytes.
.

IBM rebranded the AS/400 several times. Many names - i5/OS, ISeries, AS/400, AS400 - refer to exactly the same system.