A fix is available
APAR status
Closed as program error.
Error description
z/OS EXplorer 3.3.2 internal defect fix
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: 01. All users allocate a dataset that a * * LISTDS returns RC 4 (partial success) * * 02. All users * * 03. All users running a Search or Locate * * on PDS with large number of members. * * 04. All users running TSO command in an * * ACF2 environment. * * 05. All users of server configured with * * TLSv1.3 support. * * 06. All users running mvs operations with * * the server having improper FEK.SFEKLPA * * configuration. * **************************************************************** * PROBLEM DESCRIPTION: 01. RSE mistreats LISTDSI RC 4 as * * error while reporting back to client * * query, causing client to display all * * characteristics of the dataset as * * "undetermined" * * 02.RSE message listener could shut * * down when encounter error in parsing * * non-standard message format. * * 03. Locate action on a member of a * * PDS having a large number of members * * may experience a short freeze due to * * processing of result. * * 04. When running in a TSO command in * * an ACF2 environment, it produces the * * informational only ACF0C038 message * * included in the execution output * * result. The presence of this message * * is unexpected causing an error in the * * execution result validation. * * 05. Currently, Daemon System ssl * * (GSK) can be configured and accept * * clients that are configured with * * TLSv1.2 or TLSv1.3. * * But the client connection to * * ThreadPool (Java SSL) may not work * * properly. Overall TLS support could * * be restricted to only-one protocol * * support at the server side. * * 06. FEK.SFEKLPA contains the modules * * required for running mvs operation * * and must be in LPA. When the * * requirement is not meet, the failure * * (here is by FEKDSI member) is * * expected, but the tracing should be * * clearly identified as error for users * * to recognize and handle. * **************************************************************** 01. RSE mistreats LISTDSI RC 4 as error case. 02. RSE message listener expects the message from TSO SEND and user EXIT routine in standard format. Messages with unexpected format either from original sender or issue with TSO SEND, or user EXIT, or backend message listener could choke up and shut down the RSE Java message listener. 03. Each Locate action on a member of a PDS when the member is not in the PDS member listing display may cause the host mvsminer to perform an all-members lockowner info batch query, which may take a long time especially when the PDS has a large number of members. 04. The ACF0C038 is informational only to denote that the running user TSO id is different from the default TSO userID defined in the Global System Option Records. RSE TSO command processor does not expect this message and may translate it incorrectly as error in certain conditions. 05. Earlier Daemon's System GSK support configuration was not conveyed properly to ThreadPool. The issue has been fixed but the implementation of ThreadPool Java SSL still is too restricted using the default enabled setting of its SSL context initialization as the base. Currently, the server, especially in Java 8, could be configured to support either TLSv1.2 or TLSv1.3, not both. 06. The processing of the output of FEKDSI in listing the dataset attributes misses to detect the failure based on its return code to flag as an error for the overall result.
Problem conclusion
01. LISTDSI specification defines RC 0 and RC 4 as successful with RC 4 as partially successful, but RSE treats non-0 RC as error. Correct to have it treat RC 4 as successful when returning to client query. 02. RSE message listener expect that TSO SEND and user EXIT construct message following a standard format. It works as expected when the original sender follows the valid syntax and rule of TSO SEND. In some conditions, such as when original message errors may escape the detection of TSO SEND and/or issues in user EXIT in constructing the forwarding message, or issue in RSE backend message listener, the message could arrive at RSE Java message listener in unexpected format. The RSE Java message listener has been modify to tolerate more with unexpected format message. 03. The batch query command by the host for the lockowner info should have been done only for the required members. The lockowner query in the attributes batch query command now is done with members filter. Note for other attributes query done by running a rexx script, it is till done for all members as rexx may not handle well with a long argument (as for the members listing). Also, for members query involved PDS with large number of members, the VSAM extended lockowner info tracker usage may also slow it down. It's best not to enable the VSAM extended lockinfo tracker when working with PDS having large number of members. 04. RSED should filter out the ACF0C038 from the output of TSO command execution, specifically in the TSO logon session info. It is informational only and based on the description of the message, the condition of the message is not an abnormal one within RSE execution context and could be ignored. In case the message may be relevant and should be filtered out, the properties "-Dinclude.info.msg=true" could be used to keep the message as is in the command execution output. 05. The Java supported properties are safe to be used in enabling the socket ssl configuration. ThreadPool could use the java ssl support properties, instead of the restricted enabled properties from its context initialization, as the base in syncing up with Daemon GSK ssl support. RSE service as a whole can be configured to support TLSv1.2 and TLSv1.3 (when allowed by GSK and Java system configuration). 06. FEKDSI return code should be included in parsing the result flag up an error in the processing of the result output from the host component. Return code of FEKDSI's list dataset now is processed and a non-zero value is determined as an error and logged as ERROR in host user log.
Temporary fix
Comments
APAR Information
APAR number
PH55097
Reported component name
EXP FOR Z/OS HO
Reported component ID
5655EXP23
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-06-12
Closed date
2023-06-12
Last modified date
2023-07-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI92190
Modules/Macros
FEJENF70 FEJJCNFG FEJJJCL FEJJMON FEJTSO FEK1SMPE FEK2RCVE FEK3ALOC FEK4ZFS FEK5MKD FEK6DDEF FEK7APLY FEK8ACPT FEK@CERR FEK@CONE FEK@CONF FEK@CUST FEK@DEB FEK@DESC FEK@FLOW FEK@GEN FEK@GENW FEK@ISPF FEK@IVP FEK@IVPD FEK@IVPW FEK@JCN1 FEK@JCNE FEK@JESJ FEK@MAIN FEK@MIGO FEK@OPTE FEK@OPTG FEK@OPTN FEK@PRIM FEK@RSE1 FEK@RSEO FEK@STRT FEK@TAB1 FEK@TAB2 FEK@TAB3 FEK@WRK1 FEK@WRK2 FEK@WRK3 FEK@WRK4 FEK@WRK5 FEKAPPCC FEKAPPCL FEKAPPCX FEKATTR FEKDSI FEKEESX0 FEKFASIZ FEKFATT1 FEKFBLD FEKFCIPH FEKFCLIE FEKFCMOD FEKFCMPR FEKFCMSG FEKFCOMM FEKFCOPY FEKFCOR6 FEKFCORE FEKFDBG FEKFDBG6 FEKFDBGM FEKFDIR FEKFDIR6 FEKFDIVP FEKFDST0 FEKFDST1 FEKFDST2 FEKFENVF FEKFENVI FEKFENVP FEKFENVR FEKFENVS FEKFEPL FEKFERRF FEKFGDGE FEKFICUL FEKFISPF FEKFIVP0 FEKFIVPA FEKFIVPD FEKFIVPI FEKFIVPJ FEKFIVPT FEKFJESM FEKFJESU FEKFJLIC FEKFJSON FEKFJVM FEKFLATR FEKFLDSI FEKFLDSL FEKFLEOP FEKFLOGS FEKFLPTH FEKFMAI6 FEKFMAIN FEKFMINE FEKFMNTL FEKFNTCE FEKFOMVS FEKFPATT FEKFPLUG FEKFPTC FEKFRIVP FEKFRMSG FEKFRSES FEKFRSRV FEKFSCMD FEKFSEND FEKFSSL FEKFSTUP FEKFT000 FEKFT002 FEKFT003 FEKFTIVP FEKFTSO FEKFUTIL FEKFVERS FEKFXITA FEKFXITL FEKFZOS FEKHCONF FEKHCUST FEKHDEB FEKHDESC FEKHFLOW FEKHGEN FEKHISPF FEKHIVP FEKHIVPD FEKHJESJ FEKHMAIN FEKHMIGO FEKHOPTE FEKHOPTN FEKHPRIM FEKHRSE1 FEKHRSEO FEKHSTRT FEKHTAB1 FEKHTAB2 FEKINIT FEKKEYS FEKLOCKA FEKLOGR FEKLOGS FEKM00 FEKM01 FEKM02 FEKMKDIR FEKMOUNT FEKMSGC FEKMSGS FEKRACF FEKRSED FEKSAPF FEKSAPPL FEKSBPX FEKSCLAS FEKSCLOG FEKSCMD FEKSCPYM FEKSCPYU FEKSDSN FEKSENV FEKSETUP FEKSISPF FEKSJCFG FEKSJCMD FEKSJMON FEKSLPA FEKSPROG FEKSPTKT FEKSRSED FEKSSERV FEKSSTC FEKSSU FEKSUSER FEKXCFGE FEKXCFGI FEKXCFGM FEKXCFGT FEKXMAIN FEKXML HUHFCOR6 HUHFCORE
Fix information
Fixed component name
EXP FOR Z/OS HO
Fixed component ID
5655EXP23
Applicable component levels
R330 PSY UI92190
UP23/06/17 P F306
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBDYH","label":"IBM Explorer for z\/OS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"330","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
03 July 2023