Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does my application sometimes receive a NativeSeqFile error when using JRIO and the Remote Method Invocation (RMI) – Java Remote Method Protocol (JRMP) to access MVS datasets?

0
Posted

Why does my application sometimes receive a NativeSeqFile error when using JRIO and the Remote Method Invocation (RMI) – Java Remote Method Protocol (JRMP) to access MVS datasets?

0

RMI-JRMP uses sockets to make the connection between the client and the server java programs. Sockets in RMI-JRMP are given an expiration time (default 15000 milliseconds or 15 seconds). If the socket is not used within this timeframe, the socket is closed. A socket cleanup thread is activated every 15000 milliseconds and is run to clean up any closed sockets and their associated resources. With Java on the OS/390 and z/OS platforms, the socket connection runs in a thread. Additionally, the JRIO code uses the Java Native Interface (JNI) to call native OS/390 ‘C’ runtime library routines to access MVS datasets. Because JRIO uses these ‘C’ runtime library routines, JRIO is dependent on the behavior of these routines and any restrictions associated with them.

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.