A fix is available
APAR status
Closed as program error.
Error description
Internal defect fix - RSEAPI 1.2.4 ZOS0302T/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1. Users use mvs commands * * 2. All mvs users * * 3. All RSE API admin users * * 4. All mvs users using range search by * * start name All * * 5. mvs users * * 6. All users opening a GDS dataset * * 7. All User * * 8. All users * **************************************************************** * PROBLEM DESCRIPTION: 1. Introduce a new MVS command to * * retrieve VSAM data set attributes. * * 2. Customers requests to have a * * command to retrieve the length of the * * dataset file a head of a download to * * avoid the whole download processing * * if the file is empty. * * 3. RSE API /admin/getUserLogs cannot * * retrieve log files belonging to other * * users * * 4. For RSE API data set list query, * * the option Range-Name-Offset is to * * locate the data set with name in the * * list sorted by name. When caller uses * * this option in paging based on * * original previous list query with * * index paging, the returned list is * * not consistent with the original * * listing * * 5. RSE API data set query has been * * returned the list sorted by filetype * * and name, different from zosmf by name * * 6. Starting with version RSE host * * 3.4.3, opening a GDS dataset in the * * IDz editor would not work. Probably, * * only GDS SEQ dataset is affected. * * 7. In Explorer for z/OS 3.4.3, when a * * user logs in after a host upgrade, a * * directory, private_common_properties, * * is created under the z/OS Explorer * * user's OMVS home directory, even if * * the feature is not enabled in rse.env. * * 8. An RSEAPI user logout may result * * in NullPointerException, and the user * * may not connect until RSEAPI is * * restarted * **************************************************************** 1. Introduce a new MVS command to retrieve VSAM data set attributes. 2. In get raw content GET command, RSEAPI response's header bytes-on-host is set to the number of bytes as counted on host 3. The RSE API started task user ID must be permitted to read other users' log files with secure file access permissions (only the owner has access) 4. The Range-Name-Offset option is based on name sorting, it not compatible to use with default range search by index integer based on file type then name sorting. 5. RSE API default sorting in data set listing query should be similar as that of zosmf 6. In recent requirement to support GDS listing in RSEAPI, an additional info was added, which chokes up the client when processing 7. A directory, private_common_properties, is created under the z/OS Explorer user's OMVS home directory, even if the feature is not enabled. 8.During RSEAPI v1.1.4 user logging out, NullPointerExceptions (NPEs) may be observed in catalina and server logs. org.glassfish.jersey.server.ServerRuntime$Responder.process An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper. java.lang.NullPointerException at com.ibm.rse.rest.adapters.AdapterManager.shutdown (AdapterManager.java:218) at com.ibm.rse.rest.adapters.dstore.RACFAuthenticationService. logoutToken(RACFAuthenticationService.java:361) at com.ibm.rse.rest.api.jaxrs.AuthRESTService. logout(AuthRESTService.java:255)
Problem conclusion
1. Users now can use the command "GET datasets/{vsamClusterName} /VSAMAttributes to retrieve the attributes of a VSAM cluster. 2. The header bytes-on-host is included in the HEAD get raw content command along with the existing Etag header. 3. Define a z/OS UNIX superuser read access permission for the RSE API started task user ID. 4. To be used for paging, sorting used with Range-Name-Offset option now is based on the Sort-By option, presumably used consistently in all related paging requests. 5. A new header option Sort-By is introduced for RSE API data set query; option valid values are "name" or "type, default to "name" similarly to zosmf, and "type" denotes a filetype then name sorting 6. The info is only used by RSE API. Fill it only for RSE API workflow only 7. Add a check for the RSE_COMMON_PROPERTIES environment variable to verify whether the service is enabled. If the service is not enabled, do not create the private common properties. 8. Rapid login and out or error operation scenarios may cause unfinished user resources initialization, which in turn may lead to the logout's NPEs. Proper check on null resources have been added to prevent the NPEs.
Temporary fix
Comments
APAR Information
APAR number
PH70117
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
2026-02-12
Closed date
2026-02-13
Last modified date
2026-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO06799
Modules/Macros
HUH1SMPE HUH2RCVE HUH3ALOC HUH4ZFS HUH5MKD HUH6DDEF HUH7APLY HUH8ACPT HUHCRYPT HUHFT000 HUHFT001 HUHFT002 HUHFT003 HUHFT004 HUHFT005 HUHFT006 HUHFT007 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 UO06799
UP26/02/20 P F602
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:
02 March 2026