|
Look at WRKACTJOB for something like this: QTRXC00275 QTCP BCH .0 QTRXC00423 QTCP BCH .0 use option 2 (chgjob) and change logging level to maximum Message logging: Level . . . . . . . . . . . . 4 Severity . . . . . . . . . . . 00 Text . . . . . . . . . . . . . *SECLVL Log CL program commands . . . . *YES Try your connect again, and when you get your job ended msg > job 181230/QTCP/QTRXC01170 ended there should be a job log.. I would also check your security audit journal (if you are running that) for any authority problems. hth jim ----- Original Message ----- From: "Eric PANISSARD" <epanissard@xxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, November 20, 2003 9:53 PM Subject: RE : RE : RE : runrmtcmd and V5R2 > QTCP user seems ok > If I look the TCP spool file I can't see any spool QRTXC... > > For your information there are 2 AS400 (product and backup) and the > result is the same for the both systems. I upgrade the two machines from > V4R5 to V5R2 the same week. May be there is a couple of PTF to apply ? > If I check the last one of 5722999 I can see RE03212 > > Eric PANISSARD > > > -----Message d'origine----- > De : midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Condon, Mike > Envoyé : jeudi 20 novembre 2003 13:01 > À : 'Midrange Systems Technical Discussion' > Objet : RE: RE : RE : runrmtcmd and V5R2 > > Strange. If the rexec jobs are not started, the Windows command should > time > out with something like "connection refused" after about 30-60 seconds > or > so. > Have you checked to see if user QTCP is intact/changed? > Does the QRTXC_____ job log spooled file show anything > useful/informative > when you look at it under wrksplf qtcp? > > And 9 minutes after I received your message, I received some spam: > A New language in 10 Days > > So that's one obstacle out of the way. > > -----Original Message----- > From: Eric PANISSARD [mailto:epanissard@xxxxxx] > Sent: Thursday, November 20, 2003 4:12 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE : RE : runrmtcmd and V5R2 > > > Hi Mike, > > We are looking for an AS400 guru, but unfortunately it's almost > impossible to get a local "green card" if you're not French and also we > need somebody who speak French :-(( > > Summary of what I can see : > - STRTCPSVR SERVER(*REXEC) > in the DSPLOG with the same time : > job 181230/QTCP/QTRXC01170 started > job 181230/QTCP/QTRXC01170 ended > > and with a return code 0 > > - CHGRXCA show me exactly the same information > - The Windows command ask me for the name and the password but > nothing more when I enter "wrkactjob" > > ???? > > Much thanks for your help > > Eric PANISSARD > Informatique De Tahiti > > > > -----Message d'origine----- > De : midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Condon, Mike > Envoyé : mercredi 19 novembre 2003 12:22 > À : 'Midrange Systems Technical Discussion' > Objet : RE: RE : runrmtcmd and V5R2 > > If I help solve the problem, does that mean I can get a job transfer to > Tahiti? > > - Try just starting the rexec server: > STRTCPSVR SERVER(*REXEC) > > - Does CHGRXCA show: > Autostart servers . . . . . . . *YES *YES, *NO, *SAME > > Number of initial servers . . . 2 1-20, *SAME, *DFT > > Inactivity timeout . . . . . . . 300 1-2147483647, *SAME, > *DFT > > Coded character set identifier 00850 1-65533, *SAME, *DFT > > > - What results do you get from a Windows command prompt if you enter: > Rexec <as400> wrkactjob > > Does it prompt for a user name? > > > > > > > -----Original Message----- > From: Eric PANISSARD [mailto:epanissard@xxxxxx] > Sent: Wednesday, November 19, 2003 3:46 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE : runrmtcmd and V5R2 > > > Hi Rob, > > You are right the *REXEC server is down that's why the job doesn't work. > But if I try to start it through Navigator or by the command STRTCPSVR > it stay stopped with no message at all in the DSPLOG or QSYSOPR... > > Best regards > > Eric Panissard > Informatique De Tahiti > > -----Message d'origine----- > De : midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx > Envoyé : mardi 18 novembre 2003 03:09 > À : Midrange Systems Technical Discussion > Objet : Re: runrmtcmd and V5R2 > > Duplicated this on my V5R2 systems. > > Short term corrective action: > Start iSeries Navigator. > Open up the remote system. > Open up Network. > Open up Servers. > Open up TCP/IP > See that Remote Execution is stopped. > Right click on it and start it. > > Long term corrective action > Start iSeries Navigator. > Open up the remote system. > Open up Network. > Open up Servers. > Open up TCP/IP > See that Remote Execution is stopped. > Right click on it and select Properties. > Check 'Start when TCP/IP is started'. > > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin > > > > > "Eric PANISSARD" <epanissard@xxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 11/17/2003 11:23 PM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > <MIDRANGE-L@xxxxxxxxxxxx> > cc > > Subject > runrmtcmd and V5R2 > > > > > > > I have some problems with the RUNRMTCMD command and the V5R2 : > > > > Between 2 AS400 I send some data file using FTP, after that I call an > RPG program on the receiver with the RUNRMTCMD. > > Few days before I upgrade the OS of each machine from V4R5 to V5R2. > > Today if I try to use the RUNRMTCMD I get the following message from the > sender (no message at all on the receiver and the FTP transfert works > very well) > > > > > > RUNRMTCMD CMD('call pgm(my_pgm)') rmtlocname('192.168.001.106') *IP > RMTUSER(qsecofr) RMTPWD() > > A remote host refused an attempted connect operation. > > > > Where I need to look for to find the problem ? > > > > Eric Panissard > > Informatique de Tahiti > > > > > > _______________________________________________ > 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. > > > _______________________________________________ > 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. > > > > _______________________________________________ > 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. > > _______________________________________________ > 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. > > > > _______________________________________________ > 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. > > _______________________________________________ > 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. > > > > > _______________________________________________ > 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-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.