CA

Unicenter® TCPaccess Communications Server r6 SP5 Readme


1.0 Welcome

2.0 Operating System Support

3.0 System Requirements

4.0 Installation Considerations

5.0 General Considerations

6.0 Known Issues

7.0 International Support

8.0 Documentation
8.1 Release Numbers on Documentation

9.0 Contact Technical Support


1.0 Welcome

Welcome to Unicenter TCPaccess Communications Server r6 SP5.

This $READT01 file contains important information to help you implement the product, including operating system support information, system requirements information, and CA Technical Support contact information.

Note: This installation requires using the new Getting Started. This readme contains instructions for obtaining the guide.


2.0 Operating System Support

Unicenter TCPaccess Communications Server r6 supports the following operating systems:


3.0 System Requirements

Unicenter TCPaccess Communications Server requires CA Common Services for z/OS and OS/390 at genlevel 9901 or above, and OS2.10.


4.0 Installation Considerations

This installation requires that you follow instructions contained in the new Getting Started. This is available as a binary PDF file, on the second file of the tape. You can run member T00GSG of the control file to pull the binary PDF file off the tape to your system. FTP to your PC in binary, and open with Adobe Reader.

The Getting Started is also available from the SupportConnect web site at http://ca.com/support.

The latest HOLDDATA information for Unicenter TCPaccess Communications Server r6 is located via FIX# QO20643.


5.0 General Considerations

The following information identifies the latest fixes available on this tape. By specifying the GENLEVEL, HIGH FIX#, or Last Confirm date to search for published solutions on http://ca.com/support , you can identify those fixes that have been created since this tape was first distributed.

TAPE VOLSER CS60S5
GENLEVEL 0612
HIGH FIX#r6.0 QO84385
HIGH PTF r6.0 TP10760
LAST CONFIRM DATE r6.0 12/01/2006

This service pack also contains maintenance for the following:


6.0 Known Issues

  1. SMPPTS ALLOCATION TOO SMALL: Under certain circumstances, customers that are applying maintenance to Unicenter TCPaccess Communications Server that is currently at the original r6, or at the SP1 or SP2 level will need to increase the size of SMPPTS. This library was initially allocated with (CYL,(5,2,50)). SP5 contains over 560 PTFs for the Communications Server, Telnet Server, and FTP Server, since the original r6. These customers will be advised to create a new SMPPTS library with SPACE=(CYL,(10,4,100)), and copy their old SMPPTS to the new one.

  2. TELNET SERVER REQUIRES DIFFERENT STEPLIB FOR z/OS 1.6: Customers with currently installed Unicenter Telnet Server software could have a problem moving the Telnet Server Job to z/OS 1.6. This is because IBM has changed the name of a required Steplib data set from GSK.SGSKLOAD to SYS1.SIEALNKE. Customers using the standard RUNTLN JCL, as distributed previously in the TLNSAMP library, may not be aware of this. We have added a comment to the RUNTLN JCL that reads:
    //*  2.  Change the SSLLIB SET parameter value as follows:
    //*
    //*         z/OS 1.5 and before...'GSK.SGSKLOAD'
    //*         z/OS 1.6 and after....'SYS1.SIEALNKE'
    //*
    //*      The value *must* be changed in this way for the job to run
    //*      properly.
    ...
    //STEPLIB  DD DSN=&TRGINDX..LOAD,DISP=SHR
    //         DD DSN=&TRGINDX..TLNLOAD,DISP=SHR
    //         DD DSN=&SSLLIB,DISP=SHR
    //*
    

  3. NEW CONFIGURATION WIZARD FOR IBM CTC TRANSFERS: PTF TP10346 (SP3) requires the creation of three new target and three new distribution libraries before the PTF is applied, if you are applying maintenance. For more detailed information, refer to Informational Solution FIX# QI55355. The following JCL can be used to create the libraries and add the DDDEFS to the target and DLIB Zones:
    //T00ALLOC JOB  ...
    //*
    //*  FOR THIS JOB TO RUN, YOU MUST GLOBALLY REPLACE THE FOLLOWING
    //*  STRINGS WITH THE APPROPRIATE VALUES:
    //*
    //*     TRGINDX...HIGH-LEVEL QUALIFIER(S) FOR TARGET DATA SETS
    //*     TRGUNIT...UNIT TYPE FOR TARGET DATA SETS
    //*     TRGVOL....DISK VOLUME FOR TARGET DATA SETS
    //*     DSTINDX...HIGH-LEVEL QUALIFIER(S) FOR DLIB DATA SETS
    //*     DSTUNIT...UNIT TYPE FOR DLIB DATA SETS
    //*     DSTVOL....DISK VOLUME FOR DLIB DATA SETS
    //*     SMPINDX...High-level qualifier(s) for SMP data sets
    //*
    //*
    //* ALLOCATE NEW TARGET AND DISTRIBUTION LIBRARIES:
    //*
    //ALLOCATE EXEC PGM=IEFBR14
    //TCPEXEC  DD DSN=TRGINDX.EXEC,
    //            UNIT=TRGUNIT,VOL=SER=TRGVOL,SPACE=(TRK,(10,3,20)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //TCPMLIB  DD DSN=TRGINDX.ISPMLIB,
    //            UNIT=TRGUNIT,VOL=SER=TRGVOL,SPACE=(TRK,(3,1,5)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //TCPPLIB  DD DSN=TRGINDX.ISPPLIB,
    //            UNIT=TRGUNIT,VOL=SER=TRGVOL,SPACE=(TRK,(5,2,10)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //ATCPEXEC  DD DSN=DSTINDX.AEXEC,
    //            UNIT=DSTUNIT,VOL=SER=DSTVOL,SPACE=(TRK,(10,3,20)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //ATCPMLIB  DD DSN=DSTINDX.AISPMLIB,
    //            UNIT=DSTUNIT,VOL=SER=DSTVOL,SPACE=(TRK,(3,1,5)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //ATCPPLIB  DD DSN=DSTINDX.AISPPLIB,
    //            UNIT=DSTUNIT,VOL=SER=DSTVOL,SPACE=(TRK,(5,2,10)),
    //            DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3200,
    //            DISP=(NEW,CATLG,DELETE)
    //*
    //*  ADD NEW DDDEFS TO TARGET AND DLIB ZONES:
    //*
    //SMPE     EXEC PGM=GIMSMP,REGION=5M,TIME=120,DYNAMNBR=120,
    //         PARM='CSI=SMPINDX.CSI,PROCESS=WAIT',
    //         COND=(0,NE)
    //SMPCNTL  DD *
      SET BOUNDARY(TCPTZN).
      UCLIN.
      ADD DDDEF(TCPEXEC)  DATASET(TRGINDX.EXEC)     SHR.
      ADD DDDEF(TCPMLIB)  DATASET(TRGINDX.ISPMLIB)  SHR.
      ADD DDDEF(TCPPLIB)  DATASET(TRGINDX.ISPPLIB)  SHR.
      ADD DDDEF(ATCPEXEC) DATASET(DSTINDX.AEXEC)    SHR.
      ADD DDDEF(ATCPMLIB) DATASET(DSTINDX.AISPMLIB) SHR.
      ADD DDDEF(ATCPPLIB) DATASET(DSTINDX.AISPPLIB) SHR.
      ENDUCL.
      SET BOUNDARY(TCPDZN).
      UCLIN.
      ADD DDDEF(ATCPEXEC) DATASET(DSTINDX.AEXEC)    SHR.
      ADD DDDEF(ATCPMLIB) DATASET(DSTINDX.AISPMLIB) SHR.
      ADD DDDEF(ATCPPLIB) DATASET(DSTINDX.AISPPLIB) SHR.
      ENDUCL.
    //
    


7.0 International Support

An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products, and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency and number formats.

A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

In addition to the English release of this product, CA supports only those languages listed in the following table.

Language Internationalized Translated
Brazilian-Portuguese No No
Chinese (Simplified) Yes Yes
Chinese (Traditional) No No
French Yes Yes
German Yes Yes
Italian Yes Yes
Japanese Yes Yes
Korean Yes Yes
Spanish Yes Yes

Note: If you run the product in a language environment not listed in the table, you may experience problems.


8.0 Documentation

Updated guides for this product are available at http://ca.com/support.

The file names for the PDF guides are:

Guide Name File Name
Unicenter TCPaccess Communications Server Assembler API Concepts K022013E.PDF
Unicenter TCPaccess Communications Server Assembler API Programmer Reference Guide K022023E.PDF
Unicenter TCPaccess Communications Server C/Socket Programmer Reference Guide K022042E.PDF
Unicenter TCPaccess Communications Server Customization Guide K021964E.PDF
Unicenter TCPaccess Communications Server Getting Started K021945E.PDF
Unicenter TCPaccess Communications Server Planning Guide K021954E.PDF
Unicenter TCPaccess Communications Server Prefixed Messages K024852E.PDF
Unicenter TCPaccess Communications Server Release Summary K020973E.PDF
Unicenter TCPaccess Communications Server RPC/XDR Programmer Reference Guide K022033E.PDF
Unicenter TCPaccess Communications Server System Management Guide K021973E.PDF
Unicenter TCPaccess Communications Server Unprefixed Messages and Codes K024861E.PDF
Unicenter TCPaccess Communications Server User Guide K021984E.PDF

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.


8.1 Release Numbers on Documentation

The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, will support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r11 may still be valid for r11.1 or even r12. Documentation bookshelves always reflect the current product release number.

Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.


9.0 Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.


Copyright © 2007 CA. All rights reserved.