× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2004

Re: V5R2 and *rexec server problem (SOLVED)

A note to all - i found this apar thru iSeries Support Search screen, which
allows search of apars, info center, psp, ptf covers, redbooks, knowledge
base,
and more - all in a single search. You can select/unselect which areas to
search.
It's a great feature & thanks to IBM.
http://www-912.ibm.com/ImprovedSearch/SearchBroker?selScope=More&action=fromMasthead&q=&Search.x=39&Search.y=13
jim

----- Original Message ----- 
From: "Emilio Padilla - Sistemática Intl." <EPADILLA@xxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, February 06, 2004 8:55 AM
Subject: RE: V5R2 and *rexec server problem (SOLVED)


> Bingo,
>
> This was the actual value
>
> Número secuencia entrada direccionamiento . :   2511
> Programa  . . . . . . . . . . . . . . . . . :   QTMXSRVR
>   Biblioteca  . . . . . . . . . . . . . . . :     QTCP
> Clase . . . . . . . . . . . . . . . . . . . :   QSYSCLS20
>   Biblioteca  . . . . . . . . . . . . . . . :     QSYS
> Máximo pasos direccionamiento activos . . . :   *NOMAX
> Identificador agrupación  . . . . . . . . . :   1
> Valor comparación . . . . . . . . . . . . . :   'REXECSRVR'
>
> Posición inicial comparación  . . . . . . . :   1
>
> I did the change and everything started ok.
>
> Thanks a lot
>
> EAPT
> Informatica Corporativa
>
>
> -----Original Message-----
> From: Jim Franz [mailto:franz400@xxxxxxxxxxxx]
> Sent: Thursday, February 05, 2004 6:46 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: V5R2 and *rexec server problem
>
> The following APAR is interesting and may solve your problem
> apar II13488 written for v5r1 but text says this problem also exists v5r2
>
http://www-912.ibm.com/n_dir/nas4apar.NSF/1be1a5b61b213a6c86256c23007048f4/5
> c8e1650c6303f6086256c9b0041fc47?OpenDocument&Highlight=0,rexec
> jim
>
> ----- Original Message ----- 
> From: "Emilio Padilla - Sistemática Intl." <EPADILLA@xxxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, February 05, 2004 12:38 PM
> Subject: RE: V5R2 and *rexec server problem
>
>
> > Already done that.  I created the dtaara, started the rexec server,
> deleted
> > the dtaara and, I didn't had any QPSRVTRC on the whole system. I even
> > uninstalled the 5722TC1, installed and install ptf again.
> >
> > Same results.  I think there most be some system value or obscure vale
or
> > parameter that causes this problem.
> >
> > Regards
> >
> > EAPT
> > Informatica Corporativa
> >
> > -----Original Message-----
> > From: Gary Monnier [mailto:gary.monnier@xxxxxxxxxxxxx]
> > Sent: Thursday, February 05, 2004 11:11 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> > Well, I guess you are going to have to do a trace.  Here is some of
IBM's
> > documentation on how to do it.
> >
> > The REXEC server can be traced by creating a data area. Note that
running
> > the REXEC server with trace running may cause a significant performance
> > impact.
> >
> > To trace the REXEC server:
> >
> > Create the data area using the following command: CRTDTAARA
> > DTAARA(QUSRSYS/QTMXRXCDBG) TYPE(*LGL) LEN(1)
> > Perform the REXEC operation that you want to trace.
> > Delete the data area using the following command: DLTDTAARA
> > DTAARA(QUSRSYS/QTMXRXCDBG)
> > Enter the following command to find the output queue:
> > DSPSYSVAL QPRTDEV
> >
> > For example, the following display appears:
> >
> > Figure 3. Display System Value Display
> >
> >
> >
>
+---------------------------------------------------------------------------
> > -----+
> > |                               Display System Value
> > |
> > |  System value . . . . . :   QPRTDEV
> > |
> > |  Description  . . . . . :   Printer device description
> > |
> > |  Printer device . . . . :   PRT01          Name
> > |
> >
>
+---------------------------------------------------------------------------
> > -----+
> > The printer device is also the name of the default system output queue.
> >
> > Record the name of the printer device. In this example, PRT01 is the
> printer
> > device.
> > Press F12 (Cancel) to return to the display where you entered the
> DSPSYSVAL
> > command.
> > Type the following command:
> > WRKOUTQ OUTQ(printer-device)
> >
> > Replace printer-device with the printer device recorded in the previous
> > display. PRT01 is the output queue in this example. For example, the
> > following display appears:
> >
> > Figure 4. Work with Output Queue Display
> >
> >
> >
>
+---------------------------------------------------------------------------
> > -----+
> > |                            Work with Output Queue
> > |
> > |Queue:   PRT01          Library:   QGPL           Status: RLS
> > |
> > |Type options, press Enter.
> > |
> > |  1=Send   2=Change   3=Hold   4=Delete   5=Display   6=Release
> > 7=Messages    |
> > |  8=Attributes        9=Work with printing status
> > |
> > |Opt  File        User        User Data   Sts   Pages  Copies  Form Type
> > Pty   |
> > | _   QTCPPRT     QTCP        QTMSMTP     HLD     46   1       *STD
> > 5    |
> > | _   QPSRVTRC    QSECOFR                 HLD     44   1       *STD
> > 5    |
> >
>
+---------------------------------------------------------------------------
> > -----+
> > Press F18 (Bottom) to get to the bottom of the spooled file list if
> More...
> > appears on the display.
> > Find the last file named QPSRVTRC with the same user as the user who was
> > logged on the REXEC server when the trace was created.
> > Press F11 (View 2) to view the date and time of the file you want to
work
> > with.
> > Verify that you are working with the most recent spooled file, QPSRVTRC.
> > Indicate in the problem report that the trace was tried and it failed.
> Send
> > whatever trace information there is with the problem report.
> >
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Emilio Padilla -
> > Sistemática Intl.
> > Sent: Wednesday, February 04, 2004 2:20 PM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> >
> > I already did that, the message below is the result of that change.
> >
> > EAPT
> > Informatica Corporativa
> >
> > -----Original Message-----
> > From: Gary Monnier [mailto:gary.monnier@xxxxxxxxxxxxx]
> > Sent: Wednesday, February 04, 2004 1:04 PM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> > Emilio,
> >
> > Try changing the job description for REXEC to (4 0 *SECLVL), end and
start
> > *REXEC and review the joblog.  It may supply you needed information.
> >
> > CHGJOBD JOBD(QTCP/QTMXRXCS) LOG(4 00 *SECLVL)
> > ENDTCPSVR SERVER(*REXEC)
> > STRTCPSVR SERVER(*REXEC)
> >
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Emilio Padilla -
> > Sistemática Intl.
> > Sent: Wednesday, February 04, 2004 10:08 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> >
> > The server is no waiting for anything, it just come up and down in the
> same
> > second, sorry about the Spanish but my system has the OS in Spanish.
> >
> > This is the joblog for the rexec job:
> >
> > CPI1125    Informativo             00   02/04/04  12:17:28.355392
> QWTPCRJA
> > QSYS        0108     *EXT
> >                                      Mensaje . . . . :   Se ha sometido
el
> > trabajo 005423/QTCP/QTRXC01203.
> >                                      Causa . . . . . :   Se ha sometido
el
> > trabajo 005423/QTCP/QTRXC01203 a la cola
> >                                        de trabajos QSYSNOMAX de QSYS
desde
> > el trabajo 005305/xxxxx/xxxxxx.
> >                                        El trabajo 005423/QTCP/QTRXC01203
> se
> > ha arrancado utilizando el mandato
> >                                        Someter Trabajo (SBMJOB) con los
> > siguientes atributos de trabajo: JOBPTY(5)
> >                                        OUTPTY(5) PRTTXT()
RTGDTA(REXECSVR)
> > SYSLIBL(QSYS       QSYS2      QHLPSYS
> >                                        QUSRSYS    AFPTOOL    SPLTOOL
> > MAILTOOL) CURLIB(*CRTDFT) INLLIBL(QGPL
> >                                         QTEMP) LOG(4 00 *SECLVL)
> > LOGCLPGM(*YES) INQMSGRPY(*DFT) OUTQ(/*DEV)
> >                                        PRTDEV(P1) HOLD(*NO)
DATE(*SYSVAL)
> > SWS(00000000) MSGQ(QUSRSYS/QTCP)
> >                                        CCSID(284) SRTSEQ(*N/*HEX)
> > LANGID(ESP) CNTRYID(NI) JOBMSGQMX(16)
> >                                        JOBMSGQFL(*PRTWRAP)
ALWMLTTHD(*NO)
> > INLASPGRP(*NONE) SPLFACN(*KEEP).
> >
> > CPF1164    Finalización            00   02/04/04  12:17:28.356872
> QWTMCEOJ
> > QSYS        00BD     *EXT                    *N
> >                                      Mensaje . . . . :   Trabajo
> > 005423/QTCP/QTRXC01203 finalizado el 02/04/04 a
> >                                        las 12:17:28; se utilizaron 1
> > segundos; código de finalización 0 .
> >                                      Causa . . . . . :   El trabajo
> > 005423/QTCP/QTRXC01203 se ha completado el
> >                                        02/04/04 a las 12:17:28 después
de
> > utilizar un tiempo de unidad de proceso
> >                                        de 1 segundos. El trabajo tuvo el
> > código de finalización 0. El trabajo
> >                                        finalizó después de 1 pasos de
> > direccionamiento con un código de
> >                                        finalización secundario 0.  Los
> > códigos de finalización de trabajo y sus
> >                                        significados son los siguientes:
> 0 -
> > El trabajo se completó normalmente.10 -
> >                                        El trabajo se completó
normalmente
> > durante una finalización controlada o una
> >                                        finalización del subsistema
> > controlada.20 - El trabajo excedió la gravedad
> >                                        de finalización (atributo de
> trabajo
> > ENDSEV).30 - El trabajo finalizó de
> >                                        forma anómala.40 - El trabajo
> > finalizó antes de pasar a activo.50 - El
> >                                        trabajo finalizó mientras estaba
> > activo.60 - El subsistema finalizó de forma
> >                                        anómala mientras el trabajo
estaba
> > activo.70 - El sistema finalizó de forma
> >                                        anómala mientras el trabajo
estaba
> > activo.80 - El trabajo finalizó (mandato
> >                                        ENDJOBABN).90 - Se forzó la
> > finalización del trabajo después de que
> >                                        terminara el límite de tiempo
> > (mandato ENDJOBABN).Recuperación  . :   Para
> >                                        obtener más información, vea el
> tema
> > sobre Gestión de trabajos en Information Center,
> > http://www.iseries.ibm.com/infocenter.
> >
> >
> > EAPT
> > Informatica Corporativa
> >
> >
> > -----Original Message-----
> > From: Gary Monnier [mailto:gary.monnier@xxxxxxxxxxxxx]
> > Sent: Wednesday, February 04, 2004 12:02 PM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> > Ok, so after 300 seconds your REXEC servers will disconnect from your
> > clients.  Have you tried increasing Tiempo espera sin actividad to a
value
> > you feel comfortable with.
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Emilio Padilla -
> > Sistemática Intl.
> > Sent: Wednesday, February 04, 2004 9:37 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> >
> > Is all defaults
> >
> >
> > Teclee elecciones, pulse Intro.
> >
> > Arranque aut. de servidores  . . AUTOSTART      *YES
> > Número de servidores iniciales   NBRSVR         2
> > Tiempo espera sin actividad  . . INACTTIMO      300
> > Identificador juego caracteres   CCSID          00850
> >
> >
> >
> > EAPT
> > Informatica Corporativa
> >
> >
> > -----Original Message-----
> > From: Gary Monnier [mailto:gary.monnier@xxxxxxxxxxxxx]
> > Sent: Wednesday, February 04, 2004 11:16 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> > Emilio,
> >
> > Have you checked the REXEC attributes?  Prompt command CHGRXA and see
what
> > the inactivity timeout parameter is set to.  The default is 5 minutes
(300
> > seconds).
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Emilio Padilla -
> > Sistemática Intl.
> > Sent: Wednesday, February 04, 2004 8:28 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: V5R2 and *rexec server problem
> >
> >
> > No, there's nothing there, the job is starting and ending normally. It
> just
> > that won't stays up. I'm thinking maybe about some parameter somewhere
> that
> > is making the server not to wait. I even started audit journaling for
qtcp
> > user profile in case there was some authority problem, but there's
nothing
> > there either.
> >
> > EAPT
> > Informatica Corporativa
> >
> > -----Original Message-----
> > From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
> > Sent: Wednesday, February 04, 2004 10:00 AM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: V5R2 and *rexec server problem
> >
> > Anything in:
> > - QSYSOPR
> > - DSPLOG
> > - WRKPRB
> >
> > Rob Berendt
> > -- 
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > Emilio Padilla - Sistemática Intl. <EPADILLA@xxxxxxxxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 02/04/2004 10:36 AM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Fax to
> >
> > Subject
> > V5R2 and *rexec server problem
> >
> >
> >
> >
> >
> >
> > Hi all, I'm having a problem with my *rexec server in V5R2.  I don't now
> > why
> > but it does not stay up.  Every time I start the server, the server
comes
> > up
> > and immediately down.  The joblog says nothing, just that the job
started
> > (CPI1125) and ended normally (CPF1164) with code 0.  Any ideas why? I'm
in
> > V5R2 with C33644520 installed.
> >
> > TIA
> >
> > EMILIO PADILLA T
> > Informatica Corporativa
> >
> > _______________________________________________
> > 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.
> >
> >
> > _______________________________________________
> > 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 thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.