|
This is how I solved the problem: Route the RUNRMTCMD to the PC that started user's emulation session (TCP/IP or SNA): o R320 and R370 and later of OS/400 provided an extension to the QDCRDEVD API to allow the IP address to be retrieved from the virtual device description. See APARs SA61841 (R320) and 61583 (R370) for details on the new format. See the system API reference documentation for information on the API itself. Using this API, it is possible to route the PC command to the PC that started the emulation device. No PTF is needed to retrieve the APPC device used for SNA connections. This information is available via the QDCRDEVD API in all releases. A sample program and command that demonstrates this may be available at FTP:\\testcase.software.ibm.com in the AS400/fromibm/ApiSamples directory as runrmtcmdd.zip. It contains a sample command RUNRMTCMD which adds a *DFT option for the protocol. If *DFT is selected, the protocol (SNA or IP) of the emulation session is retrieved as well as the APPC device name (SNA) or IP address (TCP/IP) and the command is routed to that PC. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.