Skip to main content

 
IBM Systems  > Servers  > Mainframe servers  > z/VSE  > 

Service and support

  
Introduction Preventive Corrective Problem Mgmt.
bk-bullet.gif General
bk-bullet.gif Advanced functions (AF)
bk-bullet.gif VSAM
bk-bullet.gif POWER
bk-bullet.gif Interactive interface & ICCF
bk-bullet.gif REXX
bk-bullet.gif CICS Transaction Server
bk-bullet.gif VSE Connectors
bk-bullet.gif TCP/IP
bk-bullet.gif DL/I
bk-bullet.gif Language Environment (LE)
bk-bullet.gif VSE VTAPE

z/VSE V4.2   |   z/VSE V4.1   |   Unsupported releases    

Unsupported release: VSE Connector 7.1 APARs for z/VSE V3.1
Unsupported release: VSE Connector 6.7 APARs for VSE/ESA V2.7
Unsupported release: VSE Connector 6.6 APARs for VSE/ESA V2.6
Unsupported release: VSE Connector 6.5 APARs for VSE/ESA V2.5


Unsupported release: VSE Connector 7.1 APARs for z/VSE V3.1

Last update March 18, 2009

APAR
Date
PTF Contents
PK82701
2009/03
UK44938 When using VSAM Redirector under CICS, you may receive the following VSAM CLOSE error when you terminate CICS using 'CEMT P SHUT I' and a redirected VSAM file is open at that time:
F8 0008 4228I FILE nnnnn CLOSE ERROR X'B8'(184) CAT=mmmm
(........) REQUEST ERROR: RPLFDBK = X'0C0004'
In this case VSAM will perform an autoclose at End of Task (EOT). VSAM Redirector can not use TCP/IP services at EOT, thus it returns an error when closing the file.
PK75755
2008/12
UK41622 1 MB data loss with remote Virtual Tapes in case of IDCAMS stacked BACKUP.
Note: Above update is in the workstation code (Component 5686-CF7-35). Please download from  here and reinstall the component on your workstation.
Note: You must also install VSE/AF APAR DY46926 / PTF UD53361.
PK71241
2008/09
UK39479 When trying to set a field of a record for an ESDS type VSAM cluster, the method VSEVsamRecord.setField() throws the following exception: "VSEVsamRecord.setField(): The key fields are not set. Use setKeyField() first to specify the key." Since an ESDS type VSAM cluster does not have a primary key, it should not be required to specify the key fields.

Note: Above update is in the workstation code (Component 5686-CF7-35). Please download from  here and reinstall the component on your workstation.
PK69863
2008/08
UK38648 When using VSAM Redirector together with TCP/IP for VSE 1.5F you may get the following message on a redirected GET request:
IPN379I Socket Receive dropped from BG reason: Partition start address is inconsistent.
The application that is executing the GET request hangs. Above situation happens if a GET is performed where the user buffer in RPL (addressed by RPLAREA, length in RPLRLEN) is shorter than the maximum record length of the cluster.
Please also apply TCP/IP for VSE FIX 124 (for 1.5F) or 146 for 1.5E.
PK69106
2008/07
UK38208
  1. When using the VSE Connector client JDBC support, SQL INSERT or UPDATE requests may fail when the target columns in the SQL statement do not list the key fields at the beginning. The following exception is thrown: "com.ibm.vse.connector.AccessDeniedException: VSEVsamRecord.setField(): The key fields are not set. Use setKeyField() first to specify the key."
  2. When using the VSE Connector client to insert VSAM data, the insert may fail when a part of the VSAM key is mapped by two or more fields, but only one field is set. The following exception is thrown: "com.ibm.vse.connector.AccessDeniedException:
    VSEVsamRecord.setField(): The key fields are not set. Use setKeyField() first to specify the key."

Note: Above update is in the workstation code (Component 5686-CF7-35). Please download from  here and reinstall the component on your workstation.

PK67494
2008/07
UK37357 A Java application using the VSE Connector Client receives a com.ibm.vse.connector.NotFoundException for a VSAM Cluster, map or field although the resource is existent, if the VSE Connector Server runs at a high
load.
PK67191
2008/06
UK37262 When using the VSE Connector Client method VSEVsamCluster.selectRecords() with a filter that builds a partial or complete key, the VSE Connector Server may fail to position to the specified key and instead positions to the beginning of the file. This may causes a long response time and high CPU and I/O utilization while the Server reads through all records of the VSAM file until it finds the record that matches the key.
PK66621
2008/06
UK36822 When using the VSEVsamCluster.selectRecords() method with a filter that builds a partial or complete key, the VSE Connector Server reads the whole VSAM file in case the VSAM file does not contain a record that matches the specified partial or complete key. This causes a long response time and high CPU and I/O utilization while the server reads through all records of the VSAM file. 
PK63805
2008/04
UK35522 ABEND 0C1/AKEA or 0C2/AKEA at X'FFFFFFFF' in program IESSOAPE when using VSE SOAP Support to call an external Web Service. Abend happens at iconv_close in IESSOAPC due to overlaid storage.

Note: You need to change the CSD definitions of programs IESSOAPC and IESSOAPE to EXECKey=CICS. Please see the  DFHCSDUP.job
PK60731
2008/02
UK33625
  1. 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.
  2. 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
  1. 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. 
  2. 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
  1. 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.
  2. 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
  1. 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".
  2. The XML Parser fails to parse tags with names that are only one character long (e.g. ). 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:

  1. Problems when using LOCATE mode with redirected VSAM cluster.
  2. Incorrect key position and length is used when accessing a redirected VSAM cluster via an alternate index.
  3. Problems when using VSAM Redirector with compressed clusters.
  4. Performance degradation with VSAM Redirector due to improper use of GETVIS/FREEVIS SVCs.
  5. 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:
  1. 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).
  2. VSE XML parser has been enhanced to support XML entities. (Requirement MR0428053442).
  3. 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).
  4. HTTP client has been corrected to allow connections through a proxy server.
  5. HTTP client has been corrected to generate correct HTTP header 'accept-charset'.
  6. 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:
  1. 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.
  2. 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.
  3. 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).
  4. SOAP Methods without XML namespaces are considered as invalid: Usualy the SOAP method is prefixed with an XML namespace  . Some SOAP clients do not prefix the method:  . Code has been changed to accept such requests using the default namespace.
  5. 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.
  6. 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.
  7. 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.
  8. 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.  


Back to top


VSE Connector 7.1 components

Comp. ID CLC Description
5686-CF7-35 81N VSE Connectors


Unsupported release: VSE Connector 6.7 APARs for VSE/ESA V2.7

Last update December 15, 2006

APAR
Date
PTF Contents
PK35852
2006/12
UK20471
  1. 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.
  2. 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.
PK32398
2006/10
UK18646 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.
PK27112
2006/07
UK15982
  1. 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".
  2. The XML Parser fails to parse tags with names that are only one character long (e.g. ). In this case error code NOT_WELL_FORMED (1) is returned.
PK25404
2006/05
UK14940

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:

  1. Problems when using LOCATE mode with redirected VSAM cluster.
  2. Incorrect key position and length is used when accessing a redirected VSAM cluster via an alternate index.
  3. Problems when using VSAM Redirector with compressed clusters.
  4. Performance degradation with VSAM Redirector due to improper use of GETVIS/FREEVIS SVCs.
  5. 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.
PK18960
2006/02
UK11787 Misc problems in VSE SOAP engine, XML parser and HTTP client:
  1. 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  PK19360).
  2. VSE XML parser has been enhanced to support XML entities. (Requirement MR0428053442).
  3. 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).
  4. HTTP client has been corrected to allow connections through a proxy server.
  5. HTTP client has been corrected to generate correct HTTP header 'accept-charset'.
  6. 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.  

PK03036
2005/03
UK01964 Several problems with VSE SOAP (Web Services) Support:
  1. 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.
  2. 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.
  3. 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).
  4. SOAP Methods without XML namespaces are considered as invalid: Usualy the SOAP method is prefixed with an XML namespace  . Some SOAP clients do not prefix the method:  . Code has been changed to accept such requests using the default namespace.
  5. 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.
  6. 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.
  7. 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.
  8. 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.  

PQ97187
2004/11
UQ95102 Using VSE XML parser IESXMLAP causes a GETVIS leak when called multiple times from one program:
When the VSE XML parser IESXMLAP is used to parse multiple XML documents in the same program, a GETVIS leak occours. This is caused by duplicate fetchep() calls inside the parser.
PQ88809
2004/05
UQ88865 Performance Problem with VSE Connector Server if many standard labels are available and other misc problems.
  • VSEConnectors: Now using new LABEL function to search for a label by given file-id. This requires AF APAR  DY46070. If this APAR is not applied, the old mechanism will be used.
  • VSAM Redirector: Corrected handling of SOCKET SEND to support BSI TCP/IP Stack.
    Added support for REUSE (new method VSAMFileInfo.isReuse() ).
  • HTTP: Now ISO8859-1 Codepage is the default ASCII codepage. If any other charset is specified in the HTTP header it will be used, if available. LE APAR  PQ87058 to avoid traps during iconv_open() when an invalid or unknown codepage is specified.
  • SOAP: Misc corrections and recompile.
  • VSE Connector Client/JDBC: Misc corrections.
  • VSE Script Server: Misc corrections.

Note: Please download the newest  VSE Connector ClientVSAM Redirector Server and  VSE Script Server.

PQ83126
2004/01
UQ84011

VSE Virtual Tape: Under some circumstances (tape record sizes) a BufferFullException is thrown which causes an IO error on VSE.

You should also install APAR  DY46179.

Note: Please download the newest VSE Virtual Tape Server.

Note: This PTF superseeds APAR PQ79349/PTF UQ80790

PQ74694
2003/06
UQ77749
  • VSE Connectors: Misc fixes in client code.
  • VSE Connectors: Corrected date handling in VSAM, LIBR, ICCF and POWER interfaces. To make sure the correct date format is used, set the COUNTRY parameter in CEEDOPT accordingly. E.g. if you are in the USA and you use US date format MM/DD/YY, specify:  COUNTRY=((US),OVR). If you are in Germany and you use the German date format DD/MM/YY specify:  COUNTRY=((DE),OVR).
  • VSE Connectors: Adding or changing a VSAM field definition with an empty description will no longer create unnecessary records in the mapping repository IESMAPD. In addition the repository is being cleaned from these empty description records when it is opened for update he first time.
  • VSE Connectors: Enhanced clean utility IESVSDCL to remove empty description records.
  • VSE Connectors: Using buffered sends for transmitting new console messages.
  • VSAM Redirector: Added support for multible string applications (e.g. CICS). Now the string ID is sent to the VSAM Redirector Server
    ATTENTION:
    • Due to a protocol change with this support the VSAM Redirector Server must be updated also. This code will NOT run with older versions of VSAM Rediector Server!
    • Due to a interface change of the redirector handler interface you must recompile and adapt your handlers! Please have a look at the sample handlers and the javadoc.
  • VSE Script: minior fixes.
  • VSE SOAP: Add support to set tracing of the VSE SOAP implementation and the HTTP client on or off via TS-Queue entry. To activate the Trace, insert the following entry into a TS-Q named IESSOAPT: 'SCED0000'. To activate the trace of the HTTP client, add entry 'H0000000' into TS-Q IESHTTPT. You may do this using one of the following commands:
    • CECI WRITEQ TS QUEUE(IESSOAPT) FROM('SCED0000')
    • CECI WRITEQ TS QUEUE(IESSOAPT) FROM('SCED0000') ITEM(1) REWRITE
  • VSE Virtual Tape: Misc fixes.

Note: Please download the newest  VSE Connector ClientVSAM Redirector ServerVSE Script Server  and  VSE Virtual Tape Server.

PQ71095
2003/02
UQ74256
  • VSE Connectors: A missing security check allows to access VSE Connector Server plugins to be executed although a previous logon was not successful or no logon was performed at all.
  • Visual Age Generator: The VSE Connector Server plugin IESVSAPL now uses dataset name sharing to open a VSAM file. This allows to open a VSAM file more than once for update.
  • VSE Connectors: Accessing compressed VSAM clusters does not work correct because of invalid record length and key position information returned by VSE Connector Server.
  • VSAM Redirector: Problem with VSAM Redirector when processing a DELETE request and OWNER=REDIR.
  • VSE Virtual Tape: Enhancements of remote Virtual Tape server.
  • VSEConnectors: Enhancements of VSAM JDBC Driver.
  • VSE Script: minior fixes.
  • VSE SOAP and VSE Connector: recompile of C sources due to use of wrong compiler level.

Note: Please download the newest  client code.


Back to top


VSE Connector 6.7 components

Comp. ID CLC Description
5686-066-35 75N VSE Connectors

Back to top


Unsupported release: VSE Connector 6.6 APARs for VSE/ESA V2.6

Last update February 15, 2006

APAR
Date
PTF Contents
PK18960
2006/02
UK11786 Misc problems in VSE SOAP engine, XML parser and HTTP client:
  1. 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  PK19360).
  2. VSE XML parser has been enhanced to support XML entities. (Requirement MR0428053442).
  3. 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).
  4. HTTP client has been corrected to allow connections through a proxy server.
  5. HTTP client has been corrected to generate correct HTTP header 'accept-charset'.
  6. 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.  

PK03036
2005/03
UK01963 Several problems with VSE SOAP (Web Services) Support:
  1. 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.
  2. 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.
  3. 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).
  4. SOAP Methods without XML namespaces are considered as invalid: Usualy the SOAP method is prefixed with an XML namespace  . Some SOAP clients do not prefix the method:  . Code has been changed to accept such requests using the default namespace.
  5. 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.
  6. 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.
  7. 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.
  8. 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.  

PQ97187
2004/11
UQ95101 Using VSE XML parser IESXMLAP causes a GETVIS leak when called multiple times from one program:
When the VSE XML parser IESXMLAP is used to parse multiple XML documents in the same program, a GETVIS leak occours. This is caused by duplicate fetchep() calls inside the parser.
PQ88809
2004/05
UQ88864 Performance Problem with VSE Connector Server if many standard labels are available and other misc problems.
  • VSEConnectors: Now using new LABEL function to search for a label by given file-id. This requires AF APAR  DY46070. If this APAR is not applied, the old mechanism will be used.
  • VSAM Redirector: Corrected handling of SOCKET SEND to support BSI TCP/IP Stack.
    Added support for REUSE (new method VSAMFileInfo.isReuse() ).
  • HTTP: Now ISO8859-1 Codepage is the default ASCII codepage. If any other charset is specified in the HTTP header it will be used, if available. LE APAR  PQ87058 to avoid traps during iconv_open() when an invalid or unknown codepage is specified.
  • SOAP: Misc corrections and recompile.
  • VSE Connector Client/JDBC: Misc corrections.
  • VSE Script Server: Misc corrections.

Note: Please download the newest  VSE Connector ClientVSAM Redirector Server and  VSE Script Server.

PQ83126
2004/01
UQ84010

VSE Virtual Tape: Under some circumstances (tape record sizes) a BufferFullException is thrown which causes an IO error on VSE.

You should also install APAR  DY46179.

Note: Please download the newest VSE Virtual Tape Server.

Note: This PTF superseeds APAR PQ79346/PTF UQ80781

PQ78973
2003/10
UQ81044

This PTF retrofits the SOAP functionality that has been introduced with VSE/ESA 2.7 to VSE/ESA 2.6.

Note: In order to use the SOAP functionality you must do the following steps:

  • Make sure you are on the required PTF Level for CICS/TS:
  • Define programs to CICS CSD: Run the  DFHCSDUP job to define some CICS programs.
PQ74694
2003/06
UQ77748
  • VSE Connectors: Misc fixes in client code.
  • VSE Connectors: Corrected date handling in VSAM, LIBR, ICCF and POWER interfaces. To make sure the correct date format is used, set the COUNTRY parameter in CEEDOPT accordingly. E.g. if you are in the USA and you use US date format MM/DD/YY, specify:  COUNTRY=((US),OVR). If you are in Germany and you use the German date format DD/MM/YY specify:  COUNTRY=((DE),OVR).
  • VSE Connectors: Adding or changing a VSAM field definition with an empty description will no longer create unnecessary records in the mapping repository IESMAPD. In addition the repository is being cleaned from these empty description records when it is opened for update he first time.
  • VSE Connectors: Enhanced clean utility IESVSDCL to remove empty description records.
  • VSE Connectors: Using buffered sends for transmitting new console messages.
  • VSAM Redirector: Added support for multible string applications (e.g. CICS). Now the string ID is sent to the VSAM Redirector Server
    ATTENTION:
    • Due to a protocol change with this support the VSAM Redirector Server must be updated also. This code will NOT run with older versions of VSAM Rediector Server!
    • Due to a interface change of the redirector handler interface you must recompile and adapt your handlers! Please have a look at the sample handlers and the javadoc.
  • VSAM Redirector: Added DD name and partition filter for VSE/ESA 2.6. Now the IESRDENT macro allowes to specify DD names (labels) for cluster and catalog. It also allowes to specify a partition ID (e.g. F2) as filter.
  • VSE Virtual Tape: Misc fixes.

Note: Please download the newest  VSE Connector ClientVSAM Redirector Server and  VSE Virtual Tape Server.

PQ70859
2003/02
UQ74414
  • VirtualTape: Accessing a remote virtual tape with tape records > 32K causes unexpected exceptions in the Virtual Tape Server.
  • VSEConnector: Accessing compressed VSAM clusters does not work correctly, due to invalid record length and key position information.
  • VSE Connector Client: misc. fixes for VSAM JDBC driver.

Note: Please download the newest  VSE Connector Client and  VSE Virtual Tape Server

PQ69928
2003/02
UQ73820
  • A missing security check allowes to access VSE Connector Server plugins to be executed although a previous logon was not successful or no logon was performed at all.
  • Miscellaneous problems in the VSE Connector Client code.
  • Miscellaneous problems in VSAM JDBC driver.
PQ69300
2002/12
UQ72624 For all VisualAge Generator users using VSAM remote access in ITF.
The VSE Connector Server plugin IESVSAPL now uses dataset name sharing to open a VSAM file. This allwes to open a VSAM file more than once for update.
Note: This PTF requires LE APAR  PQ69314.
PQ67459
2002/11
UQ66736
  • VSEConnector: Error getting VSE System level from SPLEVEL.PROC.
  • VSEConnector: Performance problem in VSEVSAMCluster.selectRecords().
  • VSEConnector: Too small SEND/RECEIVE buffers for large records.
  • VSEConnector: Problems in DL/I Plugin.
  • VSEConnector: Trap in ICCF request.
  • VSEConnector: Error in CopyMap function
  • VSEConnector: Added MaxRows Filter
  • VSEConnector: Error in JDBC Driver ResultSet skips rows with invalid data
  • VSAM Redirector: Use GETVIS LOC=BELOW in module IESREDCK
  • VSAM Redirector: Allow reconfiguration without restart of VSAM application.
  • VSAM Redirector: redesigned DB2 sample handler.
PQ60612
2002/06
UQ71844
  • VSEConnectur: Specifying a partial key as filter in selectRecords did not locate to the first records identified by the parial key.
  • VSEConnectur: New keyword SECURITY in main config member to set the level of security:
    • FULL - Full security.
    • RESOURCE - Logon and resource, but no user type security.
    • LOGON - Only logon security, no resource and user type.
    • NO - no security, user can logon without a password.
    Default is SECURITY=FULL.
  • VSEConnectur: Skipping non existing libraries during LibraryList request.
  • VSAMRedirector: New module IESREDCK.OBJ.
PQ59275
2002/04
UQ64865
  • VSAMRedirector: Problem with VSAM Redirector when processing a DELETE request and OWNER=REDIR.
  • VSAMRedirector: Specifying a different properties file did not work.
  • VSEConnectors: Minior updates in sample applets.
  • VSEConnectors: Specifying a different properties file did not work.
  • VirtualTape: Specifying a different properties file did not work

Included in VSE/ESA 2.6.1 refresh

PQ56517
2002/01
UQ61889

Please see also  PQ56557  (REXX)

Due to a level of the C Compiler used to compile C modules in the GA version of VSE/ESA 2.6.0 S/390 instructions with a opcode of e.g. x'A7' were generated. These instructions require at least the following hardware

  • S/390 Parallel Enterprise Server 9672 Rx2
  • Multiprise 2000/3000
  • P390/R390
  • Integrated Server

In case a customer is running another hardware system (e.g. ES/9221 or 9672-Rx1) the usage of these C modules could esult in 'operation exception' errors.

C modules are used in the following components of VSE/ESA 2.6:

  • VSE Central Functions (Virtual Tape Server, TCP/IP Key Verification)
  • VSE Connectors (VSE Connector Server)
  • VSE IUI (EZA Socket Interface)

Included in VSE/ESA 2.6.1 refresh

PQ56024
2002/01
UQ61889
  • VSEConnector: The VSE Connector Server crashes under some circumstances due to a internal storage overlay.
  • VSEConnector: Updating a VSAM record containing packed decimal fields may cause a ConcurrentUpdateException during VSEVsamRecord.commit().
  • VSAMRedirector: Minior problems with VSAM Redirector and Virtual Tape Server.

Included in VSE/ESA 2.6.1 refresh

PQ54703
2001/11
UQ60250
  • VSE Connector: Problems in VSAM-via-CICS service for concurrent update checking.
  • VSAM Redirector: Problems in UPDREQONLY processing.
  • Virtual Tape Server: Problems in Workstaton part of Virtual Tape Support

Included in VSE/ESA 2.6.1 refresh


Back to top


VSE Connector 6.6 components
Comp. ID CLC Description
5686-066-35 65N VSE Connectors

Back to top


Unsupported release: VSE Connector 6.5 APARs for VSE/ESA V2.5

Last update February 25, 2005

APAR
Date
PTF Contents
PQ74694
2003/06
UQ77747
  • VSE Connectors: Corrected date handling in VSAM, LIBR, ICCF and POWER interfaces. To make sure the correct date format is used, set the COUNTRY parameter in CEEDOPT accordingly. E.g. if you are in the USA and you use US date format MM/DD/YY, specify:  COUNTRY=((US),OVR). If you are in Germany and you use the German date format DD/MM/YY specify:  COUNTRY=((DE),OVR).
  • VSE Connectors: Using buffered sends for transmitting new console messages.
PQ70859
2003/02
UQ74413 VSEConnector: Accessing compressed VSAM clusters does not work correctly, due to invalid record length and key position information.
PQ69928
2003/02
UQ73819 A missing security check allowes to access VSE Connector Server plugins to be executed although a previous logon was not successful or no logon was performed at all.
PQ69300
2002/12
UQ72623 For all VisualAge Generator users using VSAM remote access in ITF.
The VSE Connector Server plugin IESVSAPL now uses dataset name sharing to open a VSAM file. This allwes to open a VSAM file more than once for update.
Note: This PTF requires LE APAR  PQ69314.
PQ67458
2002/11
UQ71832
  • Error getting VSE System level from SPLEVEL.PROC.
  • Performance problem in VSEVSAMCluster.selectRecords().
  • Too small SEND/RECEIVE buffers for large records.
  • Problems in DL/I Plugin.
  • Trap in ICCF request.
PQ60611
2002/06
UQ66733
  • Specifying a partial key as filter in selectRecords did not locate to the first records identified by the parial key.
  • New keyword SECURITY in main config member to set the level of security:
    • FULL - Full security.
    • RESOURCE - Logon and resource, but no user type security.
    • LOGON - Only logon security, no resource and user type.
    • NO - no security, user can logon without a password.
    Default is SECURITY=FULL.
  • Skipping non existing libraries during LibraryList request.
PQ56316
2002/01
UQ62126
  • Updating a VSAM record containing packed decimal fields may fail with a ConcurrentUpdateException at method VSEVsamRecord.commit(). This is caused by a sign nibble value of X'F' instead of X'C'.
  • Execution of the ExecuteJob request (VSEPower.executeJob() method) can cause a internal dispatcher loop under some timeout circumstances.
  • The Display Activity Plugin causes a internal dispatcher loop while gathering activity data. The Display Activity Plugin seems to hang after first measurement interval.
PQ56023
2002/01
UQ61521
  • The VSE Connector Server crashes under some circumstances due to a internal storage overlay.
  • Paralell access to the same VSAM dataset causes NOT_FOUND error when using selectRecords() method.
PQ52261
2001/11
UQ60340
  • The length of an PACKED field in a VSAM Map was calculated incorrectly.
  • Added support for PACKED fields up to 19 digits (10 bytes). Also added support for 64 bit integers (signed/unsigned).
  • Handling of VSAM open for empty cluster was wrong.
  • Logon of a user failed with TopSecret, because TopSecret does not allow to extract AF segment.
  • Update of a VSAM record did not write the updated data to disk immediately.
  • Read of a VSAM record holds a lock on the CI under some circumstances.
  • Update and Delete of a VSAM record did not check for concurrent updates.

Integerated into VSE/ESA 2.6

PQ51324
2001/08
UQ56851
  • Filters at selectRecordsmethoddidnotworkwith<,<=,>,>= and STRING or BINARY data types.
  • Opeing VSAM files for input did open with data set name sharing, which implies open for output.
  • Performance problem while handling a request due to calls to recv().
  • Performance problem at connect due to hostname lookup done by trace facility at client side.
  • Connection was not released to connection mamanger in case of an exception during request handing.
  • Under some circumstances VSAM requests establishes a second connection during request processing.
  • The VSAM CLOSE ALL command did not close all opened files.

Integerated into VSE/ESA 2.6

PQ50122
2001/06
UQ55480
  • When using methon VSEVsamCluster.selectRecords() with filter(s) that consists of a field of type SIGNED, UNSIGNED or PACKED, the filter did not work correctly. The result was that no recor matches the filter.
  • LocateFilter was not working correctly with filter <=. Select did start at filter value instead of starting at first record.
  • Select did not terminate when filter < or <= is used with key, and the value of the key is greater than the specified filter value. Instead the file was read until EOF was reached.
  • Browsing large VSAM catalog takes very long time. This applies also for very fragmented catalogs (i.e. there are a lot of deleted records within the catalog).

Integerated into VSE/ESA 2.6

PQ49063
2001/06
UQ54777
  • Now automatically adding a temporary partition label for the master catalog before opening. This solves the problem with opening the master catalog when a IJSYSUC is present in the standard labels.
  • ClusterList Request-handler has been optimized when retriving information about a single cluster.
  • Added SocketBuffer-Trace. It can be enabled via SETTRACE command.
  • Added tracing for VSAM Open errors It can be enabled via SETTRACE
      command.
  • Added line content to message "IESC1017E SYNTAX ERROR IN CONFIG FILE: ". Now displaying the line in error.

Integerated into VSE/ESA 2.6, included in VSE/ESA 2.5.2 refresh.

PQ41480
2000/09
UQ46934

Several problems/enhancements in VSE Connector Server and VSE Connector Client.

Integerated into VSE/ESA 2.6, included in VSE/ESA 2.5.1 refresh.


Back to top


VSE Connector 6.5 components

Comp. ID CLC Description
5686-066-35 55N VSE Connectors

Back to top



 
We're here to help

Easy ways to get the answers you need.

  E-mail us E-mail us

Stay informed
Get the latest news about z/VSE through Twitter  

Service & support
VSE Recommended Service Level 
VSE Corrective Service 
Search the APAR database 
Software problem reporting 
Sending problem material to IBM 
Ordering PTFs 
Apply PTFs from the internet 
Support for IBM mainframes 
ShopzSeries 
IBM Global Services 

Acrobat
Get Adobe® Reader®