In previous releases of the product, StorageTek supported TCPaccess's old proprietary SAS/C TLI socket interface, which is different than the IBM socket interface.
The JCL configuration that was used for previous releases no longer works.
Sun / STK has removed the code for that old interface. How can the new Silo SL8500 be configured to run with TCPaccess?
In this new release, Sun STK removed the old code for TCPaccess, and is now using EZASMI (we call it HPNS).
They are still using SAS/C for RPC calls, but supply their own SAS/C runtime modules, so we do not want the TCPaccess SASLINK to get in the way of that.
There are also no longer any parameters to differentiate between IBM and TCPaccess. Differentiation is now done by using either the IBM SEZALOAD or the TCPaccess.LINK to get the correct version of the required module, EZASOH03.
Here are the necessary steps for ensuring that Silo SL8500 will connect properly to TCPaccess.
ACSS 184.108.40.206 STACKA.CA.COM. 220.127.116.11 or ACSS STACKA.CA.COM. STACKA.CA.COM. 18.104.22.168You will also want to map the SMFID of the system to the IP address somewhere in the DNRALC; location for this is less important. E xample:
//STEPLIB DD DISP=SHR,DSN=hlq.STK.SOC.SLCLINK <----Sun application code // DD DISP=SHR,DSN=hlq.STK.SOS.SLSLINK <----Sun application code // DD DISP=SHR,DSN=hlq.CA.TCPACCESS.V60.LINK <----TCPaccess LINK // DD DISP=SHR,DSN=hlq.STK.SACLINK <----Sun/SASC modules // DD DISP=SHR,DSN=hlq.STK.SSCR.CSLLINK <----Sun/SASC modules
If you have any questions or encounter any problems, please contact Technical Support for assistance.