Configuring SUN StorageTek Silo SL8500 to run with TCPaccess

Products

• TCPaccess

Issue/Introduction

Description:

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?

Solution:

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.

1. Check your DNRALCxx member in the TCPaccess PARMLIB.
   The first few entries should either be subsystem ID mapped to IP address hostname mapped to IP address
   or
   fully qualified hostname mapped to IP address

   ACSS                   147.52.82.12 STACKA.CA.COM.         147.52.82.12               or ACSS                   STACKA.CA.COM. STACKA.CA.COM.         147.52.82.12

   You 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:
   
   examples:

   SYSA                   147.52.82.12

2. You will need to configure a TCPIP.DATA (if you do not already have one) for use in the SL8500 startup JCL.
   Her us a sample that is syntactically correct. You can copy it to your mainframe as a separate FB 80 dataset or include it in the TCPaccess.PARM if you prefer.
   =================================
   TCPIPJOBNAME SNSTCP52
   ;
   ;name of your domain
   DOMAINORIGIN CA.COM
   ;
   ;IP address of domain nameserver
   ;use multiple statements if you use more than one nameserver
   ;omit if you run the stack in LOCAL mode.
   NSINTERADDR 10.253.27.133
   ;
   ;VMCFNAME if you are running IUCV, default is VMCF
   ;not needed if you are not running IUCV
   VMCFNAME VMCF
   ;
   ;TCPaccess subsystem-ID, default is ACSS
   DNRSSID ACSS
   ;
   ;hlq for set of 5 MVS datasets
   ;you may not have these set up. Set to the same hlq as this dataset.
   DATASETPREFIX SNSTCP
   ;
   ;first qualifier of the fully qualified host name of the stack
   ;HOSTNAME + DOMAINORIGIN = fully qualified hostname.
   HOSTNAME FRED
   ;
   ;the following values are the defaults used in this dataset.
   ;they may be coded or omitted.
   NSPORTADDR 53
   RESOLVEVIA UDP
   RESOLVERTIMEOUT 30
   RESOLVERUDPRETRIES 1
   =================================
   If you have unsure regarding the parameters please contact support for further information..
   
   
3. Your SL8500 startup JCL needs the following STEPLIB:

    //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

4. Add this DD statement to the SL8500 startup JCL
   //SYSTCPD DD DISP=SHR,DSN=hlq.TCPIP.DATA
   This should point to the TCPIP.DATA you created in step 2.

If you have any questions or encounter any problems, please contact Technical Support for assistance.

Environment

Release:
Component: NTCPAC