APAR
Date |
PTF |
Contents |
PK63805
2008/04 |
UK35522 |
ABEND 0C1/AKEA or 0C2/AKEA at X'FFFFFFFF' in program IESSOAPEcwhen using VSE SOAP Support to call an external Web Service. Abend happens at iconv_close in IESSOAPC due to overlaid storage. |
PK60731
2008/02 |
UK33625 |
- Problems in VSE Script Server:
- The logic for the 'IF' statement is not working correctly.
- The line number reported in an script error ($SCRIPTERROR$) is incorrect.
- Missing support for using SSL for connection to VSE.
- Installation problems with Java 6 and InstallShield: The error message "JVM not found" is displayed if installing under Java 6.
Note: Above update is in the workstation code (Component 5686-CF7-35). Please download from here and reinstall the component on your workstation.
|
PK57314
2007/11 |
UK31826 |
The VSE SOAP Engine fails to receive the response, in case the HTTP header specifies a charset enclosed in quotes: Content-Type: text/xml;charset="UTF-8". The code does not remove the quotes and tries to open a codepage converter (iconv) with the codepage name containing the quotes. The SOAP trace shows the following error situation:
IESSOAPC ASCII_CODEPAGE = "UTF-8"
IESSOAPC EBCDIC_CODEPAGE = IBM-1047
IESSOAPC INITCODEPAGES RC = 1 |
PK56828
2007/11 |
UK31534 |
When using VSE Connector Client or VSAM JDBC Driver in a pooled environment (e.g. within WebSphere Application Server) a connection error is not correctly handled. Instead, the calling application is receiving an exception: "Connection is currently used by another request."
Note: Above update is in the workstation code (Component 5686-CF7-35). Please download from here and reinstall the component on your workstation. |
PK50803
2007/08 |
UK28104 |
When adding a VSAM record with VSE Connectors through the VSAM-via-CICS service you may receive an AlreadyExistentException although the record has been inserted. This happens when the file is defined with RECORDFORMAT=F in CICS and the record mapping for that file does not map the complete record. This leads to a record being inserted that is shorter than required by CICS. CICS inserts the record, appends binary zeros to the record, but returns resp=LENGERR with resp2=14 (incorrect length for fixed length record format) which is incorrectly translated to an AlreadyExistentException. |
PK43803
2007/04 |
UK24349 |
- Under certain circumstances it can happen that VSAM-via-CICS mirror transaction ICVM keeps hanging. This may lead to MAXTASK situation in CICS. Also the client programs may not be able to access VSAM files via CICS in that situation.
- When using selectRecords() method with more than 1 filter, under certain circumstances only the first filter specification is used. All remaining filters are ignored. This can lead to incorrect or incomplete data to be returned.
|
PK37259
2007/01 |
UK21180 |
During startup of Security Server in FB partition the VSAM Redirector message IESC2001E FAILED TO LOAD CONFIG PHASE IESRDCFG occurs. Following this message the Security Server gets an VSAM OPEN error 4228I FILE BSTCNTL OPEN ERROR X'32'(050) CAT=VSESPUC and terminates.
|
PK35743
2006/12 |
UK20385 |
- A NotFoundException is thrown when trying to delete the last record of a VSAM file using VSE Connector Server and VSAM-via-CICS service. The record is being deleted, but the NotFoundException is thrown because the subsequent positioning does not work.
- Exclusive lock not released after update of a VSAM record through VSAM-via-CICS Service. This can cause other tasks to wait until the file is closed.
|
PK32204
2006/10 |
UK18624 |
Under some circumstances the VSE SOAP Engine formats outgoing decimal type values incorrectly. When the specified precision and the packed decimal values would lead to a value like 0.xy, the incorrect output would be X.xy instead. |
PK30197
2006/09 |
UK17908 |
When opening a VSAM file with VSE Connector Server for read only (INPUT), the usage of dataset name sharing causes the file being opened for write (OUTPUT) and therefore can cause sharing problems when the file is opened for OUTPUT in another partition and the VSAM share options do not allow to open the file twice for OUTPUT.
Note: You must also install LE/VSE PTF UK17703. |
PK27028
2006/07 |
UK15946 |
- When the VSE SOAP Engine receives a SOAP request that contains a SOAP header, it fails to parse the SOAP request. As a result, an incorrectly formatted SOAP response is sent back with Faultdetail="No method to execute".
- The XML Parser fails to parse tags with names that are only one character long (e.g. <x>). In this case error code NOT_WELL_FORMED (1) is returned.
|
PK25337
2006/05 |
UK14888 |
During open processing for a VSAM cluster, the VSE Connector Server checks if an label for the file is already existent and sufficient. If not, a temporary partition label named TMPnnnn is created. Due to incorrect checking existing labels are not detected if the corresponding catalog label name is shorter than 7 characters and the label area is on VDISK. This causes the creation of a temporary label on each open and can fill up the label area if too many labels are created.
Other misc problems:
- Problems when using LOCATE mode with redirected VSAM cluster.
- Incorrect key position and length is used when accessing a redirected VSAM cluster via an alternate index.
- Problems when using VSAM Redirector with compressed clusters.
- Performance degradation with VSAM Redirector due to improper use of GETVIS/FREEVIS SVCs.
- VSE Connector Server partition runs out of GETVIS when using VisualAge Generator ITF access to many VSAM files due to use of dataset name sharing with 255 strings.
|
PK18932
2006/02 |
UK11718 |
Misc problems in VSE SOAP engine, XML parser and HTTP client:
- Handling of UTF-8 encoded SOAP requests has been corrected. The SOAP engine now retrieves and sends the HTTP content in binary and translates it using LE iconv (please also install LE APAR PK20013 and PK19358).
- VSE XML parser has been enhanced to support XML entities. (Requirement MR0428053442).
- VSE SOAP Engine has been enhanced to support data types decimal, date, time and arrays. Decimal SOAP parameters are now represented as packed decimal with implied decimal point. (Requirement MR0715051311).
- HTTP client has been corrected to allow connections through a proxy server.
- HTTP client has been corrected to generate correct HTTP header 'accept-charset'.
- VSE SOAP interface has been enhanced to allow he use of longer method names (up to 128 chars). The interface is backward compatible, i.e. existing programs will work without changes.
Note: Due to changes in C header files IESHTTPH.h, IESSOAPH.h, IESXMLAH and IESXMLPH, you may need to adapt and recompile your programs, when they makes use of the VSE SOAP engine, XML parser and HTTP client.
|
PK03240
2005/03 |
UK01912 |
Several problems with VSE SOAP (Web Services) Support:
- Improper details in SOAP Fault message: In case a SOAP converter or SOAP user program returned an error code, the SOAP fault message now contains the return code in the detail text.
- Progck in IESSOAPD due to invalid user TS-Queue entry: An incorrectly formated user TS-Queue entry caused a trap in the SOAP code when the entry is being processed. Now a routine has been added to verify the format of the entry prior to the processing of that entry. In case an invalid entry is detected, an return code (INVALID_PARAM) is returned.
- Missing codepage choice for SOAP/HTTP communication: Support for specifying ASCII and EBCDIC codepages has been added. The codepages can be specified in the SOAP option phase IESSOAPO (details see below).
- SOAP Methods without XML namespaces are considered as invalid: Usualy the SOAP method is prefixed with an XML namespace
<ns1:getQuote xmlns:ns1="urn:iessoapd:getquote" ... . Some SOAP clients do not prefix the method: <getQuote xmlns="urn:iessoapd:getquote" ... . Code has been changed to accept such requests using the default namespace.
- GETVIS leak leads to CICS Short on storage: Incorrect use of EXEC CICS FREEMAIN caused a GETVIS leak. Code has been corrected to free th storage correctly.
- Missing SOAP-Action HTTP header in SOAP Client: When sending a SOAP request over HTTP, an HTTP-Header line called SOAP-Action is needed by some SOAP servers. Code has been enhanced to send this HTTP header line.
- XML parser does not accept single quotes in attributes: XML attributes are usually enclosed in double quotes ("). Some XML documents use single quotes for attributes. The code has been changed to support both, double and single quotes.
- Enhancements of SOAP/HTTP trace using option phase IESSOAPO: The trace support of SOAP support and HTTP client has been enhanced. Now the trace options are specified in the SOAP option phase IESSOAPO. The SOAP code tries to load this phase. If the phase is not available, trace is deactivated. Inside the phase, several options can be specified, including trace flags and code pages. The following job can be used to assemble the IESSOAPO option phase: IESSOAPO.job
You must define the program IESSOAPO to CICS before you can use it. Use CEDA DEFINE PROGRAM(IESSOAPO) to define the program. Language is Assembler.
Note: Due to changes in C header file IESHTTPH.h, you may need to adapt and recompile your programs, when they makes use of the VSE HTTP client.
|