Re: rmtcmd not working on call to as400

[Dan Kimmel<dkimmel@xxxxxxxxxxx>]

It's been a long time, but I seem to remember that all rmtcmd calls are 
logged to QHST. Use the DSPLOG command and specify a time range. You CAN 
press F1 to get more information on any message in the QHST log. If the 
command is being rejected (usually because of a user not authorized) there 
should be an entry to that effect in QHST.

Dan




"Angela Wawrzaszek" <awawrzaszek@xxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/02/2005 10:22 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

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.