|
Angela, You can "extract" yourself from needing to have the 'x' (insert Client or iSeries here...) Access product installed if you use FTP and the rcmd command within the FTP session. It is pretty simple to accomplish and makes it easy to deploy the app without the dependencies on 'x' Access (and the PTF's and the bloat). You can also add options to display the command while executing or hide it (helpful when debugging). If you are interested, let me know and I can send along some sample code. Peter Helgren Value Added Software, Inc 801.581.1154 x202 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Angela Wawrzaszek Sent: Wednesday, February 02, 2005 9:22 AM To: Midrange Systems Technical Discussion Subject: rmtcmd not working on call to as400 We have a VB app that initiates a program on our AS/400. This has worked fine. It no longer works. It can be initiated from a DOS prompt, but not from the VB app. I am assuming some service is not started??? I started the iseries remote command on the PC running the program, and have started the tcpip service *rexec. Anything else? When the VB code runs it 'flashes' the dos prompt but it is too fast to see what happened. Is there a way to let that screen stay up? Tried setting on the rmtcmd call to VBmaximizefocus but that just 'flashes' a bigger screen. Also tried to set the property on iseries remote command to allow interaction with desktop. The command used in VB is: retval = Shell("c:\Windows\rmtcmd call RMT025CR 'CRANE" & ct & "'", 2) Set a variable to see the value of this and it is: call RMT025CR 'CRANE1' which is correct and is the command used on the dos prompt. I tried looking on the as/400 job in QSERVER for QDASOINIT but that just shows the job is connected. I compiled the CL program to show log CL *yes, but do not find a log anywhere, so I don't believe it is even initiating the job. Help! I'm running out of ideas! Angela Wawrzaszek IT Supervisor awawrzaszek@xxxxxxxxxxxxxxx (315) 258-4205 -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.