CICS Transaction Server for NT Version 4.0 - service level 3
***********************************************************************
********************* IMPORTANT - READ THIS FIRST *********************
***********************************************************************
* *
* The CICS Local Terminal support delivered with this Service Level *
* (Transaction Server for Windows NT, Version 4.0, Service Level 3), *
* is not compatible with the version of the Microsoft C runtime *
* library (MSVCRT40.DLL) which was installed in '\OPT\CICS\BIN' by *
* the original CICS installation. This DLL must be deleted before *
* the new Local Terminal can be used. *
* *
* If the DLL is not deleted, an application exception will occur in *
* the Local Terminal daemon process (CICSLCLNT.EXE) when the Local *
* Terminal is started. *
* *
* Copies in other locations (such as C:\WINNT\SYSTEM32) should NOT *
* be deleted. If you do not have a copy of 'MSVCRT40.DLL' on your *
* system please contact your IBM support representative. *
* *
* To delete 'MSVCRT40.DLL' from '\OPT\CICS\BIN' do the following: *
* *
* 1. Stop any CICS regions and SFS server(s) *
* 2. Restart your system *
* 3. Install Service Level 3 *
* 4. Switch to C:\OPT\CICS\BIN (or wherever CICS is installed on *
* your system) *
* 5. DEL MSVCRT40.DLL *
* 6. Restart your system. *
* 7. Restart your SFS server(s) and CICS regions. *
* *
***********************************************************************
***********************************************************************
* The following README file has been translated into: *
* *
* German (de_DE) *
* Spanish (es_ES) *
* French (fr_FR) *
* Italian (it_IT) *
* Korean (ko_KR) *
* Japanese (ja_JP) *
* Brazilian Portuguese (pt_BR) *
* simplified Chinese (zh_CN) *
* *
* These translated versions can be found in appropriate directories *
* on the CD-ROM. *
* *
***********************************************************************
README for Installing IBM Transaction Server for Windows NT,
Version 4.0, Service Level 3
---------------------------------------------------------------
CONTENTS
--------
This readme is split into a number of sections, as follows:
Terminology
Overview
Before you install
Prerequisite software
Disk space required
Previously applied fixes
National Language Support
Service related information
HTML versions of manuals
Sequential file support using Micro Focus External File Handler
DB2 V5 Universal Data Base support
Differences in queue and file behaviour between SFS and DB2
Micro Focus COBOL runtime environment
Limitation on number of application server processes per region
Problems reported against IBM Transaction Server for AIX
Installing Service Level 3
Invoking the installation
Displaying currently installed software levels
Installation options
Install Service Level
Reinstall Service Level
Restore Backup
Silent Installation (Unattended install)
Troubleshooting
Trademarks
Disclaimers
---------------------------------------------------------------
TERMINOLOGY
-----------
The following terms are used within this README:
Transaction Server
Refers to the package containing CICS, Encina and Digital
DCE client.
Service Level
Refers to a package containing corrective service for one
or more components of the Transaction
Server. Used also as indication of the overall stack level
for the Transaction Server package.
GA level
Refers to the original GA release of the Transaction Server
of March, 1997.
Service Level 1
Refers to the update to the GA package, released in June,
1997. Service Level 1 was a full product refresh and
technically not a service delivery.
---------------------------------------------------------------
OVERVIEW
--------
This Service Level contains corrective service for the IBM
Transaction Server for Windows NT, Version 4.0 product
("Transaction Server"). It may only be applied to a system at
Service Level 1 or higher. If you have a previous level
of the Transaction Server (see note 1), you must apply Service
Level 1, before applying this level of service. Service Level 1 is
a prerequisite of the delivery mechanism used by this Service Level
(see note 2). Subsequent Service Levels will also require Service
Level 1 to be installed. To apply Service Level 1 to your system,
you should request the product CD through your IBM Representative,
and follow the instructions supplied on the CD. Note that Service
Level 1 requires that you remove CICS from your system by uninstalling
the product. All configuration information will be retained.
Since Service Level 1 is a prerequisite for installing this Service
Level, you cannot use this package to install a new system.
In addition to Service Level 1, you must also have DCE installed
at service level ec03, before you can install Service Level 2.
Support for Oracle 7.3.3
------------------------
Oracle 7.3.3 is now supported. See \opt\cics\doc\oracle7_3_3.README
for details.
Notes:
1.CICS only:
To determine whether you have Service Level 1 installed,
you can run the cicscheckup utility, supplied either in the bin
directory, or in utils\cicscheckup, for Development systems. If
cicscheckup is not present on your system, then it is very likely
that it is a GA level system. The output from cicscheckup is as
follows:
=============================================================
Transaction Server for Windows NT
CICSCHECKUP report
Command : cicscheckup -A
Time: 10:33:00
Date: Mon, Oct 20 1997
=============================================================
System Information
-----------------------------------
Machine is Intel architecture
Processor is Intel Pentium revision 20c
Number of processors on this machine: 1
Active processor mask is: 0x00000001
... Processor #0 is configured
Memory is 0% busy
Total physical memory ........... 133615616
Free physical memory available .. 74215424
Total paging file ............... 181026816
Free paging file available ...... 94208
HOSTNAME for this computer is levkas
Software stack level information
-----------------------------------
Windows NT is at version 4.0
Windows NT CSD is at version Service Pack 3
CICS Server is at version : 4.2.0
Checking CICS Server executable cics.exe in J:\nt_intel_N\bin\
Build level : Service Level 1, build s400-L970529
Product version: 4.0.1
Encina is at version : 2.2.0
DCE is at version : 1.1C
IBM SNA not installed
Microsoft SNA not installed
DB2 Server not installed
=============================================================
The Software Stack level information section shows the current
level of the Transaction Server components. In this case, CICS is
shown to be at Service Level 1, with a product version of 4.0.1.
If the cicscheckup output does not show this, or a higher level,
then the product is at GA level.
All products:
If you are familiar with the Windows NT registry editor (either
REGEDT32.EXE or REGEDIT.EXE), you can examine the individual
product keys to identify installed levels:
HKEY_LOCAL_MACHINE\Software\IBM\CICS\CurrentVersion
HKEY_LOCAL_MACHINE\Software\DigitalEquipmentCorporation\DCERuntimeServices\CurrentVersion
HKEY_LOCAL_MACHINE\Software\TransarcCorporation\Encina\CurrentVersion
and for Transaction Server component information -
HKEY_LOCAL_MACHINE\Software\IBM\TransactionServer\\CurrentVersion
where level information is shown by three values - MajorVersion,
MinorVersion and Revision.
2.Encina only:
If you are using the Transaction Server for Encina only, you must
still be at Service Level 1 or higher. Service Level 1 does not
update the Encina product component; however, it sets up generic
Transaction Server configuration information, which is then used
by subsequent Transaction Server Service Level installations.
If you have Service Level 1 installed, higher Service Levels can be
installed on your system directly, without requiring an uninstall of the
current product levels.
---------------------------------------------------------------
BEFORE YOU INSTALL
------------------
Before you install this Service Level, you should ensure that
your system is in a suitable state for service to be applied. As
described in the Overview, you must have Transaction Server Service
Level 1, or higher, installed. If you have applied any additional
service to any of the components, other than via IBM Service channels,
this Service Level installation may not deliver any service for those
components. For example, if either Encina or DCE patches have been
applied independently, the Service Level 3 installation will not
apply any service contained in this package.
This Service Level can apply service to all Transaction Server
components without the need to uninstall first. You should stop all
running regions and SFS servers, following the instructions in the
appropriate section of the Transaction Server documentation. Any
services should be stopped, either through supplied administration
tools, or through the Services Control Panel applet in the Control
Panel folder. Use the Windows NT Task Manager or Process Viewer to
check that no DCE, Encina or CICS processes are still active. This
will prevent the Service Level installation process from updating
the modules. Some commonly running processes are:
1.tsconfig.exe - the CICS Administration Utility.
2.cicslclnt.exe - the CICS Local Terminal (Named Pipe) client
daemon.
3.cicstnsvc.exe, cicsteld.exe, cicsteldi.exe - CICS Telnet
Server support.
4.dcesetup.exe - the DCE configuration utility.
Also, check that no external application has any CICS, Encina or
DCE files open. These may include editors, debuggers, IDE
applications (for example, Microsoft Developer Studio), and HTML
browsers. If you begin installing the Service Level only to discover
that an application is using a file that is to be updated, you may
exit the installation and run it again, once the application has
been stopped. See "Reinstalling a Service Level".
Prerequisite software
---------------------
The prerequisite software for this Service Level is the same as for
the Transaction Server, except that for this Service Level, you
must also have DCE installed at service level ec03. Refer to the
documentation supplied for details of supported operating system
levels. Any changes in supported compilers or databases are recorded
in the documentation supplied with the Service Level package.
Disk space required
-------------------
This Service Level is supplied as a single self-extracting executable.
Running this executable first unpacks the installation files, and
then executes the installation itself.
In order for the self-extracting executable to unpack the installation
files, approximately 50MB of temporary storage is required. The
directory pointed to by the TEMP environment variable is used to
determine the location for these files, which are removed following
installation. If the location currently pointed to by TEMP does not
contain sufficient space, you should create a new temporary directory
on a drive partition which does contain adequate free space. You can
then update the TEMP environment variable to point to this new
location, and run the self-extracting executable again.
Once invoked, the Service Level 3 installation will update product
files for CICS, Encina and DCE, if required. The additional disk space
required for the Service Level, over and above what is already in use
for the installed products, cannot be determined by the installation.
You should ensure that there is sufficient free space for an
approximately 20% increase in storage requirements for each product
being updated. In practice, it is unlikely that the disk space usage
will increase significantly following application of the Service Level.
This Service Level installation process allows you to create a backup
of the currently installed products, as described in "Installation
Options". This backup need not be on the same drive(s) as the installed
products, but requires as much free space as the total used by the
currently installed products. No compression is applied to the backup
image. The installation program calculates the required storage
dynamically.
Previously applied fixes
------------------------
This Service Level installation can apply service for all CICS, Encina
and DCE components that were originally installed as part of the
Transaction Server, Service Level 1 installation process. If any of
these components were installed independently, by some other
installation process, then they can only be updated by an appropriate
external service mechanism. For example, both Encina and DCE are
available independently, outside of the Transaction Server package.
During the Transaction Server installation, these products are
detected, and the Transaction Server does not install them. As a
consequence, this Service Level determines that these products were
not installed by Transaction Server, and does not apply any service
for them. The initial screen of the Service Level installation will
indicate which products are to be updated. (See "Installing Service
Level 3".)
In addition, any products that have had updates or fixes applied
subsequent to the Transaction Server installation, cannot be updated
by this Service Level installation. This is to ensure that the
installation only applies service to levels of each product that it
knows about.
National Language Support
-------------------------
The Service Level installation is provided in US English only.
However, the installation process detects the currently installed
language version of Transaction Server, and delivers any
language-specific updates for that language.
---------------------------------------------------------------
SERVICE RELATED INFORMATION
---------------------------
This section describes changes in support introduced as a result of
service activity and important information which has not yet been
included in the formal documentation.
HTML versions of manuals
------------------------
HTML versions of the IBM Transaction Server for Windows NT manuals
can be found on the World Wide Web at the following URL:
http://www.software.ibm.com/ts/txseries/library/manuals/nt/
Sequential file support using Micro Focus External File Handler
---------------------------------------------------------------
When using the CICS External File Handler with Micro Focus COBOL
and File Control on DB2 all file I/O is directed to the 'database
table' files on DB2. Service Level 3 introduces changes to allow
limited access to local files.
Four environment variables have been defined:
CICS_XFH_LOCAL_LINE_SEQ
CICS_XFH_LOCAL_SEQ
CICS_XFH_LOCAL_INDEXED
CICS_XFH_LOCAL_RELATIVE
If the environment variable and the COBOL file type in the file
entry in FILE-CONTROL match, the file will be handled by the Micro
Focus External File Handler (EXTFH). If not the file will be
handled by the CICS 'DB2' External File Handler, e.g.
FILE-CONTROL file entry specifies 'Access is sequential'
and
CICS_XFH_LOCAL_SEQ=1
then file will be handled by Micro Focus EXTFH
FILE-CONTROL file entry specifies 'Access is sequential'
and
CICS_XFH_LOCAL_SEQ is not set
then file will be handled by CICS 'DB2' External File Handler
DB2 V5 Universal Data Base support
----------------------------------
IBM Transaction Server for Windows NT has been tested with DB2 V5
Universal Data Base (UDB). No changes to the product were required
but during the database integration steps noted in the Administration
Guide (SC33-1881) the UDB libraries should be used instead of the DB2
V2 libraries.
Differences in queue and file behaviour between SFS and DB2
-----------------------------------------------------------
In the Application Programming Guide (SC33-1888), under the section
"Differences in queue and file behavior between SFS and DB2", bullet
4 reads as follows:
When DB2 is used as the file manager, files over 4005 bytes long
must be created with the last column of a variable type (VARCHAR,
LONGVAR, BLOB). The total length of the preceding fixed columns
cannot exceed 4005 bytes.
This bullet should also state that:
The maximum length for any char field is 254 bytes.
Micro Focus COBOL runtime environment
-------------------------------------
There is no specific action required to provide a Micro Focus COBOL
language environment for CICS. The COBOL language method file,
'cicsprCBMFNT', is provided as part of the IBM Transaction Server for
Windows NT product '\opt\cics\bin' directory.
Limitation on number of application server processes per region
---------------------------------------------------------------
For CICS regions running on the NT platform, the maximum
number of application server processes (cicsas) per region
is limited to 63. This limitation arises from a documented
restriction in the NT API call WaitForMultipleObjects regarding
the number of kernel objects which can be monitored simultaneously
by any thread. Starting a 64th application server in any region
will cause the cicsam process and all cicsas processes to exit.
Thus, the MaxServers region definition parameter must be
maintained at a value less than 64. More application servers
can be obtained using multiple regions, with up to 63 application
servers per region.
Problems reported against IBM Transaction Server for AIX
--------------------------------------------------------
The following APARs, which describe customer problems reported
against IBM Transaction Server for AIX, have been fixed for the
NT platform by Service Level 3.
IX76367 - ERT deadlock in TasLU_ForceAbend
IX73716 - Core dump in cicssfmt
---------------------------------------------------------------
INSTALLING SERVICE LEVEL 3
--------------------------
This section describes how to install the Service Level, and
what features are provided to ensure that the system is correctly
updated.
Invoking the installation
-------------------------
Service Level 3 is supplied as a self-extracting executable,
UPDATE.EXE, which can be invoked from the command line, or via
the Explorer interface.
1.It first confirms the product which is to be installed.
2.As described in Disk space required, this executable then
unpacks the installation files, which requires temporary
disk space, (which is released after installation is complete).
3.The installation process is then invoked, briefly displaying
the product logo panel before the standard installation
Welcome screen is displayed.
Displaying currently installed software levels
----------------------------------------------
The next panel of the Service Level installation contains a summary
of the software installed on your system, and what components of it
are to be updated by the Service Level installation.
The installation can therefore be invoked to show the following
information:
1.Components of the Transaction Server package that are
installed.
2.Components of the Transaction Server package which were not
installed by the Transaction Server.
3.Components of the Transaction Server that are to be updated
by this Service Level.
Note that components are only updated if they were installed by
the Transaction Server at the currently installed level, and the
Service Level contains a later version of each component (CICS,
DCE or Encina) than the currently installed level.
For each product component (CICS, Encina and DCE), the following
information is displayed:
- Current version and revision level
- Installation directory
- Installation date
- Installation configuration (for any optional install
components)
- Service Level and revision level of the product
component
- Whether or not this product component will be updated by
the Service Level installation.
Installation options
--------------------
Depending on the state of the system, the Service Level
installation provides one or more installation options:
1.Install the Service Level
2.Reinstall the Service Level (for a partially completed,
or previously unsuccessful installation)
3.Restore a backup.
The following sections describe each of these processes in turn.
Install the Service Level
-------------------------
1.The install option is presented the first time the Service
Level installation is run. Note that you cannot select a
subset of the package to install, and the destination
directories are the same as for the initial installation of
Transaction Server.
2.Once you have selected the Service Level Install option, a
message is displayed, warning you that the system will reboot
following this installation. You are then asked whether a
backup is required. Note that a backup can only be made when
installing, rather than reinstalling. This is to ensure that
the backed up image is valid.
We strongly recommend that a backup is created during the
initial installation of this Service Level. A backup can only
be created during an initial installation. Once the new Service
Level has been installed successfully and verified as correct,
if required, the backup data can be removed. The installation
stores the backup data in a default subdirectory called TSBAK002
(this can be changed during installation), on one of the drives
used for CICS, Encina or DCE. Deleting this directory means that
the Service Level installation process will report an error next
time it is run, as it finds that the backup data is missing.
If you select No, the process skips the Backup screen, and the
Service Level is installed.
3.If you select Yes, you are then asked to specify the target
directory for the backup files. You can select Browse to specify
an alternative directory to that shown. You will then return to
this screen. The files are then copied to the target directory.
(If the backup fails, or is cancelled, you are asked whether
installation should continue.)
4.Once the backup has completed, the Service Level is then
automatically installed.
At exit, the installation process confirms that the installation
succeeded. If an error has occurred, this is reported, and you should
run the installation process again, after taking any appropriate
action, as outlined in "Troubleshooting". This may mean freeing up
disk space, for example.
Reinstall the Service Level
---------------------------
Reinstalling is available for subsequent installations, and can be
used if a previous installation failed. For instance, if disk space
proves to be inadequate to apply all of the Service Level, it may be
re-applied.
1.This time when you display the currently installed software
levels, you will see that your system is already running with
Service Level 3.
2.As the installation process detects that you have installed
this Service Level before, you are only offered the option of
re-installing the Service Level, or restoring backup.
3.Select Re-install. Service Level 3 is then re-installed.
At exit, the installation process confirms that the re-installation
succeeded. If an error has occurred, this is reported, and you should
run the installation process again, after taking any appropriate
action, as outlined in "Troubleshooting".
Restore a backup
----------------
1.To restore a backup, select Restore Backup from the Service Level
Installation screen. The backup process first checks that the
correct backup files and registry entries exist.
2.Backup files and registry entries are then restored to the level
shown.
Silent Installation (Unattended install)
----------------------------------------
There is no silent install option for this service level, due to the
complexity of the checking that takes place. This involves verifying
registry, environment variable, subdirectory and individual module
information, in order to determine how to proceed. However, if you
wish to create a silent install response file, you can follow these
steps:
1.Run UPDATE.EXE as described in Invoking the installation. This
unpacks the installation files into your TEMP directory.
2.Once the files have been unpacked, copy them from the temporary
location, usually
X:\TEMP\~EXB0000
or similar, where X:\TEMP is the directory pointed to by the
TEMP environment variable.
3.Change out of this temporary directory and exit the Service
Level installation. (If the directory or any files are in use
when the installation exits, the temporary files will not be
removed).
4.Invoke
UPDATE.EXE -r
from the directory location containing the installation files
that you have just copied. This should create a silent install
response file in your Windows directory. The response file has
the file extension .ISS. Complete the installation as required.
5.Edit the response file to modify any of the settings (for example,
target locations). This response file can then be used directly
with the self-extracting executable for subsequent installations.
Invoke the installation as:
UPDATE.EXE -s -f X:\PATH\UPDATE.ISS
where X:\PATH is the path to your response file (for example
network attached drive), and UPDATE.ISS is the name of the
response file to be used.
Note: This process is based on InstallShield documentation and has not
been tested with this Service Level installation.
---------------------------------------------------------------
TROUBLESHOOTING
---------------
The Service Level installation process is split into two parts:
a validation and checking phase, followed by a file copy and system
update phase. Problems may occur at either phase, although it is more
likely that the verification process encounters problems.
The following is a list of common problem areas, and possible
explanations.
Problem Area Problem Explanation and solution
Description
General Authority -You must have local administrator authority
and to apply this Service Level.
permissions -Ensure that no active processes exist which
invalid hold locks on any of the CICS, Encina and DCE
modules, as this will prevent the Service Level
installation from updating those files.
Disk space -Ensure that you have sufficient disk space in
your TEMP location for the Service Level
installation to prepare the installation files.
-Ensure that there is a reasonable buffer zone
of free space on each of the drives that contain
Transaction Server component products.
Software Corrupt or -Each product installed by the Transaction Server
components missing installation process has two keys - its own
registry data product key, and one under
HKEY_LOCAL_MACHINE\Software\IBM\TransactionServer\.
These must contain consistent information. Ensure
that both keys are present.
Invalid -The product subdirectory may not exist on the drive
subdirectory where the installation process is looking.
-Check that any registry entries for the product
refer to the correct installation location.
-Check that any relevant environment variables (for
example ENCLOC, DCELOC) are correctly specified.
-Ensure that the current user has permission to
access all the subdirectories.
Component -Was the software component installed by the Transaction
will not be Server installation process?
updated -Have any non-IBM supplied fixes, patches or other
updates been applied to this product?
-Check that version of the product contained in this
Service Level is later than the version currently
installed.
-Check that this Service Level contains updates for
the product in question, and specifically for the
subcomponent. For example, the Service Level may
contain Encina updates for specific subcomponents only.
-Verify that you have installed Service Level 1, or higher,
of the Transaction Server, as described in the "Overview".
Installation Insufficient -The installation process cannot determine the amount
failures disk space of disk space required for the update to installed
components. Ensure that a buff
er is available on the
target drive.
-If products are installed on different driv
es, ensure
that each of these drives has a suitable amount of disk
space available.
-If this error occurs whilst updating a product, exit
the installation and free some disk space on the
target drive. Run the Service Level installation again,
and you will have the option to reinstall the Service
Level. Note that you cannot create a backup during a
reinstall.
File copy -The installation process requires local administrator
fails authority to update all CICS files (which use file
level security under NTFS).
-If target files are read-only, change them to be
writeable, and run the installation again.
-If the file is in use or locked, check that no CICS,
Encina or DCE process is currently running.
Note that CICS processes may lock Encina and DCE
modules. Other applications may have files locked,
as described above.
-Other errors may mean that the installation process
failed to unpack the installation files successfully.
Try running the self-extracting installation executable
again.
Incorrect -The installation process uses a key called
National HKEY_LOCAL_MACHINE\Software\IBM\TransactionServer\CurrentVersion\Language
Language to identify the language that was used during the
Support files initial Transaction Server installation.
installed -If this value does not exist, then it is possible
that the Service Level 1 installation has not been
carried out successfully.
-If this value is incorrect then the Service Level 1
installation may have set it to the wrong value.
The installation will default to US English if the
language identifier in the registry is missing or
invalid.
Files copied -The installation process uses the PathName entry in
to incorrect the registry for CICS and Encina. For DCE, the path
location is extracted from the value of DCELOC. If this value
is incorrectly set, use a registry editor to correct
it, and reinstall the Service Level.
---------------------------------------------------------------
TRADEMARKS
----------
The following terms, used in this file, are trademarks or service
marks of IBM Corporation in the United States or other countries:
IBM
CICS
Digital is a trademark of Digital Equipment Corporation.
Encina is a trademark of Transarc Corporation.
Microsoft, Windows, and Windows NT are trademarks of Microsoft
Corporation.
Micro Focus, and Micro Focus COBOL, are trademarks of Micro Focus Limited
---------------------------------------------------------------
DISCLAIMERS
-----------
Please read the Microsoft documentation relating to the use of
the Windows NT Registry Editor. Incorrect use of the Registry
Editor can result in the incorrect operation of Windows NT and
may require the re-installation of the operating system.
To order this PTF please contact your local IBM representative quoting the PTF number.
|
