Copyright International Business Machines Corporation 2003. All rights
reserved.
Note to U.S. Government Users -- Documentation related to restricted
rights -- Use, duplication, or disclosure is subject to restrictions set
forth in GSA ADP Schedule contract with IBM Corp.
Note: For information about obtaining and installing the TXSeries CICS 4.3.0.8 PTF, see the READPTF_Lang.htm file for the PTF.
Contents of the TXSeries CICS 4.3.0.8 PTF
Contents of previous PTF releases
Contents of the TXSeries CICS 4.3.0.7 PTF
Contents of the TXSeries CICS 4.3.0.6 PTF
Contents of the TXSeries CICS 4.3.0.5 PTF
Contents of the TXSeries CICS 4.3.0.4 PTF
Contents of the TXSeries CICS 4.3.0.3 PTF
Contents of the TXSeries CICS 4.3.0.2 PTF
The following are important notes about TXSeries on the AIX, Solaris, and Windows systems.
If you are using a PPC Gateway Server with SNA to connect to the mainframe version of CICS Transaction Server version 1.3 or later, you must also install TXSeries Encina 4.2 PTF 15.
This section lists the defects fixed in this PTF, organized in order of
their APAR numbers.
This section lists the APARs fixed in the previous TXSeries PTF releases:
Contents of the TXSeries CICS 4.3.0.7 PTF
Contents of the TXSeries CICS 4.3.0.6 PTF
Contents of the TXSeries CICS 4.3.0.5 PTF
Contents of the TXSeries CICS 4.3.0.4 PTF
Contents of the TXSeries CICS 4.3.0.3 PTF
Contents of the TXSeries CICS 4.3.0.2 PTF
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
| APAR Number | Abstract |
| IY15663 | Java API error: The EIB response was not reset on an EXEC CICS LINK command. |
| IY20737 | (Windows systems only) CMF timing data reported on NT systems was missing or incorrect. |
| IY22309 | (Windows systems only) The error ERZ058415E was generated in the Windows 2000 Event Viewer Log when Windows management instrumentation was used. |
| IY22369 | (UNIX systems only) When a CICS region was removed with the cicscp destroy command, all programs that were pointed to in the region's path were removed. |
| IY22405 | When the cicsadd, cicsupdate, and cicsdelete commands were used, attempts to autoinstall a terminal with an invalid device resulted in the errors ERZ011004I/1301. |
| IY24160 | It was impossible to start a second SFS server if the seventh character in its name was the same as the seventh character in the name of the first SFS server. An incorrect entry was selected from the binding file. |
| IY24360 | A CEMT transaction issued to place an abnormally terminated terminal out of service caused the CCIN transaction to stop abnormally. |
| IY24912 | A CICS region terminated abnormally with the ABEND code U1001 and EXC_E_ILLADDR while cleaning up the conversation ID (CONVID) handle. |
| IY26467 | ( Windows systems only) It was impossible to set user exit 33 in the Program Definitions window of the IBM TXSeries Administration Tool. |
| IY26663 | For files with no key, the INQUIRE FILE commands returned KEYLENGTH (-1), KEYPOSITION (-1), RECORDSIZE(-1). |
| IY26724 | User exit 33 did not provide enough information to identify a FEPI connection for an INSTALL or DISCARD command. |
| IY27159 | The command SET TRANSACTION TCLASS(0) set the value of TCLASS to 32. |
| IY27201 | If the log daemon was not ready, a CICS region terminated abnormally during an initialization. |
| IY27252 | The INQUIRE TASK(xxxx) command returned an incorrect transaction class name if the value of the TCLASS option was changed by using a SET TRANSACTION command. |
| IY27450 | The FEPI INQUIRE PROPERTYSET command returned the value FORMAT(DATASTREAM) when the value of the DEVICE option was LUP resources. |
| IY27655 | The error ERZ048008E/0303 U4802 occurred during an attempt to free region pool storage. |
| IY28080 | PL/I transactions ran successfully if the level of protection against corruption was set to NONE. If the level was set to NORMAL, the transactions waited indefinitely or terminated abnormally with the code A158. |
| IY28335 | After a task was canceled, a CICS region waited indefinitely with the error ERZ034114E/0731 UNSUCCESSFUL ATTEMPT TO UNINSTALL ENTRY '@JRL'. |
| IY28342 | An attempt to start an SFS server failed with the message NO SUCH FILE SYSTEM. |
| IY29056 | When an unexpected signal was caught during the compiling of PL/I programs, the programs terminated abnormally with the code A158. |
| IY29110 | An error occurred in creating the switchload file for DB2 single-phase commit. |
| IY29113 | The cicsas process did not run the FEPI commands properly unless the CICSLU (LUO listener) was properly initialized. |
| IY29114 | In FEPI, performance enhancements have been made in managing mutexes, catching exceptions, and the logic for retrying connections. |
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
| APAR Number | Abstract |
| IY22710 | When the cicsexport command was run against a region with a symbolic link that was not resolved, the system displayed the message ERZ046002E Unable to access region. This message was misleading because the problem was with the link, not the region |
| IY22408 | An abend 57A occurred when a CICS RECEIVE MAP command was executed. The abend was accompanied by the message ERZ05002e/0012 cics internal error (assert) data length is less than TerBM_Buffer length. |
| IY22382 | The CICS Universal Client disconnected and reconnected after another terminal tried to connect to the region with the same netname. |
| IY20991 | After PTF 4 was applied on Solaris and Windows NT systems, running the CSTD transaction and selecting option 7 caused an ASRA abend. The problem resulted from a defect that was added for AIX at PTF 4, which inadvertently changed the internal table processing for Windows NT and Solaris systems. |
| IY20203 | When the special names paragraph of a COBOL program did not contain a user-coded statement, the cicstran command did not generate a period (.) on the statement it adds. The statement added without a period, call-convention 8 is litlink, then caused an error in the compiler |
| IY19498 | After upgrading the CICS Universal Client to the 3.1.2 level, a customer received the error message ERZ0280215E Incorrectly formatted. |
| IY18586 | After PTF 3 was applied, the CEDF debugger did not work if the terminal being debugged was associated with the locale ja_JP (Japanese). The error ERZ019009E Display could not be created resulted. |
| IY18477 | When a customer used the EXEC CICS INQUIRE TSQ(tsq_name) command and the name of the TSQ contained fewer than eight characters, a QIDERR(eibresp44) queue not found error was received even though the queue existed |
| IY17814 | When a customer used the EXEC CICS INQUIRE TSQ(tsq_name) command and the name of the TSQ contained fewer than eight characters, a QIDERR(eibresp44) queue not found error was received even though the queue existed. |
| IY17192 | The cicstran command stripped parameters from SQL statements if the statement was coded over a number of lines. If the statement was coded on one line, the problem did not occur |
| IY17186 | For short-lived threads, such as those found in FEPI (SNA LU0 Listener), the linked list of stash pointers was not cleaned up properly, resulting in a memory leak |
| IY16830 | Customers running CICS with a Japanese locale sometimes received the message ERZ057032E Buffer OVERFLOW. This message is generated when a message being translated overflows the internal message buffer |
| IY13475 | (AIX only) When the System Management Interface Tool (SMIT) utility was used to start a Peer-to-Peer Communications (PPC) Gateway server, the operation failed with the message Invalid Format. The error occurred because the command was generated with parameters in the wrong order |
| IY11841 | Customers attempting to use the Micro Focus COBOL Workbench with TXSeries 4.3 received an APCT abend because the Workbench was not supported in TXSeries 4.3 |
| IY06869 | When the CEMT I PROG(prog_name) command was executed with the NEW parameter to force a new copy of a program into the run time, an error stating Invalid Change was returned. This command had worked in version 4.2 |
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
| APAR Number | Abstract |
| IY17195 | An U5701 abnormal termination error occurred when the ComSU_XPOpen function attempted to free an intercommunication control block (ICB) entry that was on the send queue in a wait-sleep state. During the wait-sleep state, the thread processing in the send queue returned ICB entry to the free list. When the ComSU_ClearAndFreeICB function woke, it also freed the first ICB entry, which caused duplicate IDs for the same ICB entry. |
| IY17190 | When the CICS Communications Definition Install (CCIN) transaction attempted to logon using a terminal ID whose netname was already in use, the reuse of the netname caused the hard install of the terminal to fail. The CCIN transaction continued with the autoinstall process using the existing ID while it attempted to ping the client to ensure that the duplicate ID was not an orphan process. The client never replied to the ping because it was busy attempting to install the new terminal ID. When the CCIN process failed to receive a reply to its ping, it called a processing loop that attempted to shut down all the terminal entries for the client. When the loop reached the duplicate terminal ID, it failed to complete because the ID was in use. As a result, the autoinstall process never completed |
| IY17187 | The Front End Processing Interface (FEPI) start process did not release and detach threads when it finished using them. This caused a memory leak in the CICS logical Unit (CICSLU) process when FEPI LU0 calls were made, and resulted in the abnormal termination of the region. |
| IY16959 | The region ended abnormally and reported an A57A error code during the processing of an intercommunication control element (ICE) chain. The process was attempting to place a mutex lock on an ICE entry which had already been freed |
| IY16796 |
TXSeries CICS needed modifications to accommodate changes made in the mainframe product, CICS Transaction Server (CTS) 2.1. |
| IY16523 | When a CICS region on an AIX machine acted as the Application Owning Region (AOR) to the gateway region, it was possible for duplicate terminal IDs to occur. When two of the Terminal Owning Regions (TORs) generated the same terminal ID, the gateway passed the duplicate IDs to the AOR on the AIX machine. The gateway region was not affected by the duplicate terminal IDs because it assigned alias names to terminals coming in through an Intersystem communication (ISC) connection. The original terminal IDs were passed when the transactions were shipped to the next region, in this case the AIX AOR region. TXSeries CICS did not assign alias names to shipped terminals |
| IY16480 | When Systems Network Architecture (SNA) was used to connect to a mainframe, CICS had problems if network errors caused the SNA sessions to be dropped. When CICS attempted to reallocate the sessions, an exc_e_illaddr exception, indicating an illegal address, was displayed and the region was shut down |
| IY16479 | The cicslu.exe process leaked memory when the Front-End Programming Interface (FEPI) LU0 connection was unavailable. The problem occurred because the schedule work call was not checking the return code on FEPI calls; as a result, memory was not deallocated for calls that failed |
| IY16478 | CICS processes and regions sometimes ended unexpectedly and the error message Error closing handle -6 was displayed. The fatal error occurred because CICS attempted to use an invalid handle for cleaning up the mutex. |
| IY16477 | TXSeries CICS incorrectly reported the error ERZ042011E Netname does not exist in the Terminal Definitions (WD). This message occurred when a logon request that included only the netname was submitted for use by an autoinstall process. If the netname and the device type are included with the logon request, suppression of the error message is expected |
| IY16476 | In the mainframe version of CICS 1.3, the function management header (FMH43) was changed to use a previously undefined value in the fifth byte of a remote schedule task header. TXSeries CICS did not accept this byte setting for a remote schedule task, and ended a transaction whenever that byte setting was encountered. |
| IY16475 | The Region Definition attribute MaxTaskCPU was not in effect for any transaction running under the mirror transaction CPMI. As a result, the transaction exceeded the time allowed for CPU utilization |
| IY16474 | If CICS received a signal 30 response from SNA after opening a SNA device, all of the CICS application servers abnormally ended and all processing incorrectly shut down |
| IY16473 | External Call Interface (ECI) clients that failed to attach to a region were timing out with the message ECI_ERR_NO_SESSIONS. This error occurred because the value for the CICSECIMAXLUW environment variable had been reached. The value for the CICSECIMAXLUW variable was being exceeded because the logical unit of work (LUW) state was not set correctly to the LUW_Timedout attribute when a client timed out. |
| IY16472 | A FORCE PURGE operation performed on a conversational task caused the region to hang indefinitely. |
| IY16471 | The error message ERZ058916E/0001: Unexpected signal 11 caught was reported when the cicstcl command was run with more than 255 LDFLAGS settings. |
| IY16470 | Dynamic Transaction Routing (DTR) requests failed when the local transaction had a blank program name definition. The program name definition is an optional variable; therefore, the DTR request needed to be able to handle a blank program name. |
| IY16469 | Receiving the error ERZ010023E Cannot attach shared memory incorrectly caused the region to terminate with the U1002 abnormal termination code |
| IY16468 | An unexpected exit occurred when the region attempted to perform a forced purge of a CICS application server (cicsas) after the terminal was deleted. This was caused by an attempt to free a mutex that had already been freed |
| IY15871 | When the number of entries for the Display inactive files attribute exceeded the value set in the internal array for the CSTD (collect statistics) transaction, a blank screen was displayed. |
| IY15100 | During the processing of the POST and WAIT commands, an error message indicated that the internal call list table was full. Corresponding to every POST command, CICS added a callback function to the internal call list table that was intended to be used in the case of an abnormal failure. The problem occurred because the process that clears the internal call list table expected only a single entry, rather than an entry for every POST command |
| IY14063 | When CICS was used on the Solaris platform, the error code A583 was reported when the XCTL Application Programming Interface (API) command was issued while the Micro Focus Animator utility was active. Animator's unload function was not called. |
| IY13756 | The CSTD transaction abnormally ended with an ASRA abnormal termination when the internal array limit, which was set to 4000 entries, was reached. |
| IY13762 | During the processing of the ComSU_WaitForAny function, the region failed showing a U5701 abnormal termination code. The problem occurred when the internal send thread picked up a second instance of a pointer to the intercommunications buffer before completing the processing on the first pointer instance |
| IY13382 | The cicsmkcobol command failed to support the Merant COBOL runtime option FOLD_CALL_NAME(lower). The compile process failed when customers used lower-case wrappers for their COBOL calls |
| IY13161 | When CICS was used on a Solaris system, the uxa1_README sample file had a bad DB2 preload parameter designation. It improperly reported that the LD_PRELOAD=libdb2.a environment variable setting was required in the environment file; however, the correct setting needs to point to libdb2.so |
| IY12288 | When CICS was used on Windows systems, the IBM TXSeries Administration Tool did not display newly added entries, such as a transient data queue entry. It was necessary to exit from the utility and reenter to see the new information. |
| IY09593 | When CICS was used on an AIX system, the Add Listener panel in the System Management Interface Tool (SMIT) did not provide the proper selections for the protocol type field. Two entries ran together and were not able to be selected separately. |
| IY09478 | In version 4.3 of TXSeries CICS, the CEMT INQUIRE FILE(filename) transaction failed to show a designation of REM when the file was remote |
| IY08501 | The cicsexport and cicsimport commands did not copy conversion templates from one region to another. |
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
| APAR Number | Abstract |
| IY09828 | A CICS region abnormally terminated with the abnormal termination code
U5701 when connected to a CICS terminal. This situation occurred when a
CICS Universal Client was connected to a region via TCP and the transaction
timed out; it also occurred when a cicsterm terminal was connected
to a CICS for Windows NT region. The region terminated with the following
errors:
ERZ057002E CICS internal error: Unsuccessful condition 'FALSE' for function 'ComSU_XPOpen' on line 1362 in file 'cics/ServLvl/src/com/su/src/comsu_xpfns.c' of module 30 ERZ057005E CICS internal error: Abnormally terminating region with exit code 'U5701' |
| IY09734 | When a CICS transaction was routed to a mainframe over a SNA connection, the memory allocated in region pool storage for queueing the transaction to SNA was not freed. |
| IY09587 | CICS applications written in PL/I did not compile correctly. The compiler returned undefined symbol errors |
| IY09528 | On CICS for Windows NT, passwords supplied to XA-compliant resource managers from CICS were printed in the TSCstdout.log and TSCstderr.log files. Exposing the passwords in the log files created possible security problems. |
| IY09527 | Some internal cleanup processes were not thread safe |
| IY09162 | The terminal definitions shipped with TXSeries CICS were not installed if the system ID had previously been used. The installation failed with the abnormal termination code A28H |
| IY09161 | If you created a hard-coded terminal definition with a netname shorter than seven characters in length, then tried to install a CICS common client using that netname, the installation failed with the error ERZ042011E/0126 Netname ' xxxxxx' does not exist in the Terminal Definitions (WD) |
| IY09069 | When a transaction failed and CICS attempted to free region storage,
the region abnormally terminated with abend code U4802 after issuing the
following messages:
ERZ048036E/0301 CICS made an attempt to free region pool storage at address xxxxxxxx. This address is invalid. ERZ048008E/0303 CICS detected an unrecoverable error freeing region pool storage |
| IY08994 | A CICS region did not terminate when it encountered the fatal abnormal termination code U8032, which indicates the failure of an XA connection to a resource manager. |
| IY08992 | The cicsmap command sometimes generated a COBOL statement with a picture clause that extended beyond column 72, causing the COBOL compiler to fail |
| IY08990 | If a CICS program running under Micro Focus Animator used the EXEC CICS XCTL command to transfer control to another program, the process was suspended indefinitely |
| IY08570 | CICS for Windows NT did not recognize that the IBM-858 code page, which includes support for the Euro currency symbol, is a superset of the IBM-850 code page. As a result, if CICS had a conversion table defined and read an ASCII file from a remote system, it incorrectly converted ASCII to EBCDIC. |
| IY08566 | The CICS Foundation Classes sometimes used all available file descriptors. After all file descriptors were used, no other file processing was possible |
| IY08561 | When using CICS on AIX, when the EXEC CICS RECEIVE command was used to retrieve data across a Systems Network Architecture (SNA) connection, the command did not always receive all data contained in the SNA buffer |
| IY08559 | If a mainframe outage occurred while a CICS Front-End Programming Interface (FEPI) LU0 terminal was connected to the mainframe, the Virtual Telecommunications Access Method (VTAM) automatic restart did not reestablish the connection between the LU0 terminal and the mainframe when the mainframe was restored. |
| IY08544 | When used with the Japanese Kanji (Ja_JP) character set, a cicstermp terminal inserted an extra space in the output if it encountered a space in column 79 |
| IY08512 | If a CICS region detected an unsuccessful condition when a syncpoint function was being processed, the region abnormally terminated with a status code of U5701 |
| IY08511 | When using CICS on AIX and Solaris, if the cicstail command was used on a running CICS region, it did not display the messages from the region's CSMT.out file |
| IY08510 | When a CICS program running under Micro Focus Animator called another CICS program, the call failed with a duplicate symbol error |
| IY08507 | Terminal-naming clashes caused CICS to fail with the abnormal termination code A28H when transaction routing from a Terminal Owning Region (TOR) used autoinstall to assign terminal IDs (termids) sequentially. The terminal IDs, along with the TOR netname, were shipped to a TXSeries Application Owning Region (AOR), where TXSeries does its own autoinstall. When a subsequent request using the same remote system name (netname) was received, the request failed due to a duplicate remote system name. |
| IY08504 | CICS did not work correctly with the Micro Focus Animator license manager, and it was sometimes impossible to start Animator sessions because CICS had not released unused Animator licenses |
| IY08499 | A timeout facility on TCP/IP connections between a distributed CICS region and a Universal Client for TXSeries CICS was required by feature 201992. Code changes were made to header and configuration files for implementation of this feature |
| IY08497 | If an ECI application performed a second ECI call before the previous ECI call had completed, the application received the error -15 ECI_ERR_ALREADY_ACTIVE. |
| IY08496 | If a CICS terminal connection was closed while the terminal was still running a transaction, the CCIN transaction was unable to delete the terminal entry from the Communication Definitions (CD) in the 24 iterations the transaction performed. Until the terminal entry was manually deleted from the CD, subsequent connection attempts failed. |
| IY08489 | When using CICS on AIX and Solaris, the cicstail command did not immediately display data from the file used as its argument. This limited the command's usability for reviewing the status of a CICS region. |
| IY08258 | When using CICS on Solaris, the cicscp create sfs_server command failed with DCE errors |
| IY07612 | The External Call Interface (ECI) sample program failed and produced a core file when it processed an exit function |
| IY07422 | A line in the sample Java program named ClassTSQ2.java contained a
typographical error that prevented the program from compiling correctly.
The line originally read as follows:
TSQ Q = (TSQ)Beans.instantiate(null, "com.ibm.cics.server.TSQ1") |
This section lists the defects fixed in this PTF, organized in order of their APAR numbers.
| APAR Number | Abstract |
| IY07549 | (Solaris only) It was impossible to compile the External Call Interface (ECI) sample files for CICS 4.2 for Solaris |
| IY07548 | (AIX only) The cicsprC.exp export file, a file to which C applications are linked, specified deferred symbol resolution. This specification inhibited the use of shared libraries that employ EXEC CICS commands |
| IY07443 | (AIX only) Using the cicscp start region command to start
a CICS region when the SFS server was not running caused the command to
fail with the following error:
ERZ038182I/0182: Server started successfully. ERZ038255E/0120: Encina operation 'sfs_GetVolumeInfo' failed with error (1997905996) SFS_COMMUNICATION_ERROR ERZ010013I/0024: CICS has removed the lock file for region ERZ096004E/0006: An error was encountered during the processing of the cicscp command |
| IY07442 | A CICS application server sometimes waited indefinitely for an internal System Network Architecture (SNA) allocate or deallocate function call |
| IY07441 | Some user transactions abnormally terminated with the following message:
ERZ057002E/0259 CICS internal error: Unsuccessful condition TASTA_MYCATASK->AsyncAborted for function 'TasLU_CheckForAbort' ERZ05605E/0017 Abnormal termination U5655: a crucial mutual \ exclusion lock at address xxxx is held by a terminated process |
| IY07440 | The STARTBR command caused a leak in an Open File Descriptor (OFD) in a Structured File Server (SFS) server when an invalid key was issued. |
| IY07439 | When the DFHCCINX process was called, CICS regions failed with the abnormal termination code U5655 due to a lock on the IEntry mutex |
| IY07438 | CICS regions failed with the abnormal termination code U3466 due to an uninitialized mutex |
| IY07436 | Code changes that were made to the certification and decertification of the threadTID process failed to properly handle thread-cancellation procedures |
| IY07434 | (AIX only) High CPU usage occurred on AIX multiple processor machines due to the locking and unlocking of mutexes in a tight loop |
| IY07201 | The NetExpress External File Handler (EXTFH) failed during the linking process for Micro Focus COBOL programs |
| IY07171 | (Windows NT only) Regions sometimes failed to run correctly after a migration from CICS 4.2 to 4.3. The problem occurred because the cicsmigrate script erroneously assigned hexadecimal values to the TaskSharedPoolBase and RegionPoolBase attributes in the Region Definitions stanza. CICS for Windows NT requires that the values for these attributes be specified in decimal notation. |
| IY07169 | When Informix was used with CICS, CICS regions failed with the abnormal
termination code U8005 when a single-phase commit action was attempted.
The abnormal termination code was caused by a SQL error. The symptoms were
as follows:
"SECONDARY SYMPTOMS=Single Phase Informix, fvtest, SQLCODE 0, Unknown error message 0." |
| IY06643 | CICS terminal installation failed for Universal Client Terminals (version 3.1.) The flow for the CTIN transaction was modified for the version 3.1 release to add an additional signon-capable field. This field is self-defining and was intended to be ignored by any server that does not expect it. However, CICS rejected the flow with the error ERZ042004E/0112 |