Troubleshooting
Problem
Upon connecting to the host from WebSphere® Developer for zSeries®, a RSEG1056U message appears:
Connect to
Symptom
A RSEG1056U message pops up, saying:
Connect to <hostname> failed with an unexpected exception
When tracing is enabled for Remote Server Explorer® (RSE) on the host, a more detailed error appears in the rsecomm.log:
ERROR FFSServerImpl: com.ibm.ftt.rse.mvs.server.miners.FFSException:
2048 0 0 0 "CEE3512S An HFS load of module libicudata32.0.dll failed.
The system return code was 0000000157; the reason code was 0BDF019B.
A similar error about the module libicudata32.0.dll might appear in the SYSLOG:
OMVSKERN IEW4004I FETCH FOR MODULE libicuda FROM DDNAME --HFS--- FAILED
BECAUSE
OMVSKERN INSUFFICIENT LSQA STORAGE WAS AVAILABLE.
OMVSKERN CSV034I PGMF FETCH FAILED FOR THE REQUESTED MODULE.
OMVSKERN RETURN CODE 14, REASON CODE 26110003
OMVSKERN PATHNAME =
/usr/usrhttp/wdz6/h001600/icuc/lib/libicudata32.0.dl
OMVSKERN l
OMVSKERN CSV028I ABENDE06-0140 JOBNAME=OMVSKERN STEPNAME=STEP1
Cause
There is a memory storage problem when trying to load libicudata32.dll.
Resolving The Problem
To enable tracing on the RSE component on the host, refer to the RDz Knowledge Center, specifically this item:
http://www.ibm.com/support/knowledgecenter/SSQ2R2_9.5.1/com.ibm.guide.cookbook.doc/topics/whitepaper_211.html?lang=en
| Troubleshooting tips |
- Verify MAXASSIZE has 2147483647, by executing d OMVS,O from SDSF. If the MAXASSIZE is not at 2147483647, the value can be set without having to IPL by running the command SETOMVS MAXASSIZE=2147483647.
- Verify the REGION size. If INETD is started by JCL using BPXBATCH, region size must be 0. If INETD is started from a TSO/OMVS session, the TSO region size must be 2096128.
- Verify that there is not a user exit, such as IEFUSI, that is restricting how much storage a user can run with.
- Verify that the IEFUI exist was modifying the amount of region (RLIMIT_AS) by following these steps:
- Run jdkiv to verify the value of RLIMIT_AS
- Issue the SETSMF command to turn off IEFUSI for OMVS:
- The command would be:
SETSMF SUBSYS(OMVS,(IEFwhatever except IEFUSI))
to disable IEFUSI for OMVS - Rerun jdkiv and recheck the value of RLIMIT_AS. If it has changed, the IEFUSI exist has modified the storage amount available.
- Disable the IEFUSI for OMVS can resolve the problem:
- Verify that the active SMFPRMxx has this in it:
SUBSYS OMVS,(NOEXITS)
which can be set dynamically with set smf=xx
The the following message appears:
Message IEE968I is issued when the SET SMF= command is processed because z/OS UNIX does not support the SSI Notify function
and can be ignored - If IEFUSI cannot be disabled, you might be able to work around this by creating OMVS segments for INETD1 thru INETD9 as follows:
- To display the storage summary, a JDKIV tool is available. Upload the file jdkiv to the host in binary format, and set the file permissions to 777.
INSERT INETD1 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD2 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD3 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD4 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD5 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD6 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD7 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD8 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
INSERT INETD9 ASSIZE(2147483647) HOME(/) OMVSPGM(/bin/sh) UID(0)
Once the file permissions are set, the tool can be executed as follows:
>./jdkiv
Note any warning messages at the bottom of the jdkiv output.
Was this topic helpful?
Document Information
Modified date:
08 August 2018
UID
swg21252834