Browse Prior Art Database

Running CICS* Services on Windows NT**

IP.com Disclosure Number: IPCOM000118915D
Original Publication Date: 1997-Sep-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Golledge, A: AUTHOR [+2]

Abstract

When the Transaction Server for NT is installed, it adds the install directories for CICS* and Encina and DCE to the system PATH environment variable. On Windows NT**, it is possible to have network directories in the PATH or even directories which no longer exist. Network directories will only be attached at the time when the user logs on to NT - NOT when the machine has been started. Windows NT services get their environment settings at boot time, which is before any user logs on to NT. This means that any network directories will not have been resolved at this point and will effectively be treated as directories which do not exist.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Running CICS* Services on Windows NT**

      When the Transaction Server for NT is installed, it adds the
install directories for CICS* and Encina and DCE to the system PATH
environment variable.  On Windows NT**, it is possible to have
network directories in the PATH or even directories which no longer
exist.  Network directories will only be attached at the time when
the user logs on to NT - NOT when the machine has been started.
Windows NT services get their environment settings at boot time,
which is before  any user logs on to NT.  This means that any network
directories will not have been resolved at this point and will
effectively be treated as directories which do not exist.

      When an NT service is started, NT attempts to load any
associated DLLs for the NT service executable.  It searches through
the directories contained in the PATH environment variable looking
for the DLLs.  If it comes across a directory which does not exist
before it has found the associated DLLs, it stops and gives an error
indicating that the service could not be started and returns an error
number 0xc0000022.  If a user has not seen this kind of error before,
then it can take a long time to resolve it, given the lack of
information returned by the operating system.

      In summary, the problem of NT services failing to start for
Transaction Server can be caused by the following situation:
  1.  Network directories proceeding the CICS/Encina/DCE
       directories in the system PATH.
  2.  NT not resolving network directories until a user logs in.
  3.  NT services taking their environment (including PATH) at
       boot time; hence, the network directories do not exist at
       this point.
  4.  NT truncating the PATH when it finds an invalid or
       non-existent directory.

      The described solution provides a function which checks the
PATH environment variable and reports if there are any invalid or
non-existent or network directories before the CICS/Encina/DCE
directories.  This function is included as part of a supplied
executable called "cicscheckup" which is supplied with Transaction
Server for Windows NT.

The PATH-checking function is broken down into three parts:
  1.  Get the positions of the CICS path, Encina path, and
       DCE path in the PATH string.
  2.  Search through the PATH stri...