A fix is available
APAR status
Closed as program error.
Error description
RSEAPI 1.2.3 Fix release
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1. Non secure or AT-TLS servers. * * 2. All MVS users. * * 3. All MVS users. * * 4. MVS list for data sets with name having * * SYS.prefix. * * 5. All MVS users. * * 6. All MVS users. * * 7. Count of data-sets in a query of data set * * attributes is nice to have as PRE-stage for * * a range query of data-set listing with * * attributes. * * 8. All. * * 9. All. * * 10. All. * **************************************************************** * PROBLEM DESCRIPTION: 1. When running under non-secure mode * * or AT-TLS, using RSEAPI v1.2.2 * * customers reported that when uploading * * more than 10 copy-books, the operation * * fails with * * error 503. If the number of grouped * * copy-books is 10 or less, the process * * completes successfully. The issue may * * also be shown with other commands when * * there are high number requests coming * * to the server at the same time. * * 2. VSAM creation functionality is * * introduced. * * 3. GDS entries are not included in * * query data-set list by default due to * * possible large number of entries. * * 4. RMVS list for data sets with name * * having SYS. prefix may result in error * * "type not supported" * * 5. In IBM z/OS Explorer RSEAPI version * * 1.2.1, there is an issue * * where responses might inaccurately * * include content from * * different data-sets when a single user * * makes simultaneous * * requests for multiple data-sets' * * content * * 6. GDG entry attributes does not show * * properly in data-set list query. * * 7. Caller implementation of range query * * of data-set with attributes needs the * * total of count in advance for paging * * preparation. * * 8. To implement the support for VSAM * * ALLOCATE LIKE and DELETE. * * 9. To implement the support for VSAM * * ALLOCATE LIKE and DELETE. * * 10. Server and user log location should * * be in sync and located to $RSEAPI_LOGS, * * default based on RSE log base location. * **************************************************************** 1. TOMCAT concurrency semaphore valve uses the incorrect JVM option name. 2. It is part of VSAM support feature. 3. Sometimes, it's desired to include GDS entries in data-set listing. 4. RSEAPI parsing chokes on "SYS." prefix as it collides with an internal marker. 5. RSEAPI has collision in sharing the internal download buffer for multiple concurrent content download. 6. GDG entry does not show properly in data-set list query. 7. A HEAD command to provide the total count of data-sets in the query is nice to have. 8. To implement the support for VSAM ALLOCATE LIKE and DELETE. 9. To implement the support for VSAM ALLOCATE LIKE and DELETE. 10. Currently server and user logs default and custom configurations are not in sync and may cause difficulty in logs collection.
Problem conclusion
1. Use the correct jvm option for the concurrency semaphore valve value for the request concurrency control. 2. Users now can create a VSAM dataset using the existing datasets POST command. 3. RSE API users now can include GDS in their dataset listing by setting the request's Include-GDS header to TRUE. 4. Special handling is introduce for parsing correctly. 5. As with raw content download, content download should use individual non-shared internal download buffer. 6. Fix introduced to show GDG attributes properly in dataset list query. In addition to that, a new header option Include-GDS is added to include the GDS in the listing. 7. HEAD command for dataset with attributes query is implemented per caller need. 8. Server now support VSAM ALLOCATE LIKE and DELETE through the existing REST API commands. 9. Server now support VSAM ALLOCATE LIKE and DELETE through the existing REST API commands. 10. Server and user default and custom log default and custom configuration now in sync, default to top location defined by $RSEAPI_LOGS and $RSEAPI_USER_LOGS. Refer to RSE API documentation for more details on other environments definitions for other logging configurations.
Temporary fix
Comments
APAR Information
APAR number
PH68631
Reported component name
EXP FOR ZOS RSE
Reported component ID
5655EXP33
Reported release
120
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-10-21
Closed date
2025-10-22
Last modified date
2025-11-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO05471
Modules/Macros
HUH1SMPE HUH2RCVE HUH3ALOC HUH4ZFS HUH5MKD HUH6DDEF HUH7APLY HUH8ACPT HUHCRYPT HUHFT000 HUHFT001 HUHFT002 HUHFT003 HUHFT004 HUHFT005 HUHFT006 HUHMKDIR HUHMOUNT HUHPAX01 HUHRACF HUHSETUP HUHSHPAX HUHSTC
Fix information
Fixed component name
EXP FOR ZOS RSE
Fixed component ID
5655EXP33
Applicable component levels
R120 PSY UO05471
UP25/10/24 P F510
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"120"}]
Document Information
Modified date:
03 November 2025