|
midrange.com
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.
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.
