A fix is available
APAR status
Closed as program error.
Error description
RSEAPI 1.0.8 internal defect fix
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: 01.RSEAPI users * * 02.RSEAPI users * * 03.All RSEAPI users. * * 04.All RSEAPI users. * * 05.All RSEAPI users. * * 06.All RSEAPI users. * * 07.All RSEAPI users. * * 08.RSE API users * * 09.RSE API * * 10.All RSEAPI users. * **************************************************************** * PROBLEM DESCRIPTION: 01.RSEAPI user session data is not * * flushed until the end of a session. * * 02.RSEAPI jobOperation endpoint does * * not return the specific error * * message when it encounters * * exception * * 03.To apply memory usage threshold * * check for all commands, including * * non-overflow/redirect enabled * * calls. * * 04.To unify the naming of RSEAPI * * header key name follow the http key * * naming convention of hyphen style * * with leading capital, case * * insensitive * * 05.To unify the naming of RSEAPI * * header key name follow the http key * * naming convention of hyphen style * * with leading capital, case * * insensitive * * 06.To unify the naming of RSEAPI * * header key name follow the http key * * naming convention of hyphen style * * with leading capital, case * * insensitive * * 07.To unify the naming of RSEAPI * * header key name follow the http key * * naming convention of hyphen style * * with leading capital, case * * insensitive * * 08.RSE API users are not able to * * export job spool files to remote * * data set * * 09.Add support for new feature -> * * Common Properties * * 10.With RSEAPI, the query pds * * attributes does not wait for * * C_CONNECT done and could encounter * * a null exception on the client * * version check when getting maxgen * * (which could be set in a * * C_CONNECT). * **************************************************************** 01.RSEAPI user sessions keep request data in memory until the session times out. This means a session can hold onto more memory than necessary. 02.When RSEAPI jobOperation endpoint throws the exception, it does not include the specific error message. 03.Have the checker running as thread. Calculation of memory usage (from runtime) is done periodically (default checking interval of 1 min); checking on threshold (max of 80% default) is done per call; 503 (Service unavailable) is returned if memory usage is over the threshold. 04.Have the public standard follow the http key naming convention of hyphen style with leading capital, case insensitive. 05.Have the public standard follow the http key naming convention of hyphen style with leading capital, case insensitive. Also support camel key style as a variance 06.Have the public standard follow the http key naming convention of hyphen style with leading capital, case insensitive. Also support camel key style as a variance 07.Have the public standard follow the http key naming convention of hyphen style with leading capital, case insensitive. Also support camel key style as a variance 08.Introduce new end points for RSE API users to export job spool files to remote PDS and SEQ data set 09.New feature to support Common Properties 10.Have mvsminers detecting if it is run as RSEAPI to avoid the client version check in a PDS get attrs.
Problem conclusion
01.RSEAPI now uses a mechanism to free this data on regular intervals rather than at the end of a session. 02.Update the RSEAPI jobOperation endpoint to throw the exception with specific error message and details. 03.The memory checker validation is done for all calls to help to prevent crash due to excessive of memory usage for a process. 04.RSE API Overflow and misc funcs now follow the standard naming convention for http header. 05.RSE API TSO, unix and scanner adapters now follow the standard naming convention for http header. Backward compatibility for existing camel style is still supported. 06.RSE API JES adapter now follows the standard naming convention for http header. Backward compatibility for existing camel style is still supported. 07.RSE API mvs adapter now follows the standard naming convention for http header. Backward compatibility for existing camel style is still supported. 08.RSE API users can be able to export ob spool files to remote PDS and SEQ data set 09.This is a new feature added to RSE and RSE API to allow retrieval and storage of properties available to all users in a JSON format. 10.RSEAPI is guaranteed to run with a client version > 9.5, checking if the miner is running as RSEAPI is sufficiently equivalent as the check client version.
Temporary fix
Comments
APAR Information
APAR number
PH44566
Reported component name
EXP FOR ZOS RSE
Reported component ID
5655EXP33
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-03-02
Closed date
2022-03-02
Last modified date
2022-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI79545
Modules/Macros
HUH1SMPE HUH2RCVE HUH3ALOC HUH4ZFS HUH5MKD HUH6DDEF HUH7APLY HUH8ACPT HUHCRYPT HUHFT000 HUHFT001 HUHFT002 HUHFT003 HUHFT004 HUHFT005 HUHFT006 HUHFT007 HUHFT008 HUHFT009 HUHFT011 HUHFT012 HUHFT013 HUHMKDIR HUHMOUNT HUHPAX01 HUHRACF HUHSETUP HUHSHPAX HUHSTC
Fix information
Fixed component name
EXP FOR ZOS RSE
Fixed component ID
5655EXP33
Applicable component levels
R100 PSY UI79545
UP22/04/01 P F203
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"100"}]
Document Information
Modified date:
02 April 2022