|
Will the VRYCFG *off take out all Mochasoft telnet sessions, as well as AS/400 Client Access printer sessions, or will the command error out or hang if some sessions are still running? Then, is all that is needed is the VRYCFG *ON to get things going right away again (after the CHANGE to the line description runs), or does QINTER need something done to it? Thanks! -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Parrett Sent: Thursday, June 08, 2006 10:16 AM To: 'Midrange Systems Technical Discussion' Subject: RE: TCP/IP tuning Don, I Posted to the wrong subject. If you are IPL'ing the system then the Ethernet line should be down anyhow. It ht telnet user's are using client access they would simply have to reconnect. However they should not be able to connect until the interactive subsystem is started. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, June 08, 2006 9:59 AM To: Midrange Systems Technical Discussion Subject: RE: TCP/IP tuning What happens if the VRYCFG *OFF is issued and there are some Iseries users telneted (Mochasoft client) into the system at that time? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Parrett Sent: Thursday, June 08, 2006 9:41 AM To: 'Midrange Systems Technical Discussion' Subject: RE: TCP/IP tuning O.K. I think the line was active or vary on pending prior to the call of QSTRUP. Your program is correct and should have changed the line. With the monmsg cpf000 it would have continued normally. Without changing the line. Have you looked in QEZJOBLOG outq for a print relating to this? A way to solve this would be to: Vrycfg ethline01 *off Chglineth duplex(*full) Vrycfg ehtine01 *on Then continue . . . Am I correct in assuming that your user cannot afford 5 minutes of down time? That's really all the time it takes to do what you need. Kevin -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, June 08, 2006 9:25 AM To: Midrange Systems Technical Discussion Subject: RE: TCP/IP tuning Kevin - It was recompiled on 6/1, and shows run ONE time, early this morning 6/8. I do not see any particular message in the Q. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Parrett Sent: Thursday, June 08, 2006 9:06 AM To: 'Midrange Systems Technical Discussion' Subject: RE: TCP/IP tuning Sounds Like the program you listed did not run. Is your system value wrksysval QSTRUPPGM. The program should be compiled into the library shown here. There should also be a message or 2 in the qsysopr msgq that may point you to a resolution. Kevin -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, June 08, 2006 6:19 AM To: Midrange Systems Technical Discussion Subject: RE: TCP/IP tuning I see that the LINE description still shows online at IPL *NO, so the CHGLINETH command did not run ?? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, June 08, 2006 6:12 AM To: Midrange Systems Technical Discussion Subject: RE: TCP/IP tuning The IPL went last night, but I am still showing only HALF Duplex? Below is the modified CL which shows that it has been USED one time. I checked the logs, but nothing seems to indicate that there was an error in any of the commands. /********************************************************************/ PGM MONMSG MSGID(CPF0000) /********************************************************************** CHGLINETH LIND(ETHLIN01) ONLINE(*YES) DUPLEX(*FULL) MONMSG MSGID(CPF0000) VRYCFG CFGOBJ(ETHLIN01) CFGTYPE(*LIN) STATUS(*ON) /********************************************************************** STRSBS QSERVER STRSBS SBSD(QSYS/QCTL) STRSBS SBSD(AMESYS/QSPL) STRSBS SBSD(AMESYS/QSNADS) STRCLNUP STRPRTWTR DEV(*ALL) STRSBS SBSD(AMESYS/QBATCH) STRSBS SBSD(AMESYS/QCMN) STRSBS SBSD(AMESYS/QINTER) STRSBS SBSD(QPGMR) DLYJOB DLY(120) STRTCP DLYJOB DLY(120) STRHOSTSVR *ALL ENDPGM -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sean Porterfield Sent: Thursday, June 01, 2006 8:48 PM To: Midrange Systems Technical Discussion Subject: Re: TCP/IP tuning Also, your MONMSG commands should be after each of the commands you run instead of before. Since you already have a MONMSG CPF0000 at the beginning, it will apply to the whole program making your others redundant. -- Sean Porterfield Chris Bipes wrote:
Move it to the beginning. TCP will not start completely with out the line up and running. I would put it between 2900 and 3000 Christopher Bipes Information Services Director CrossCheck, Inc. -----Original Message----- From: Don Cavaiani Sent: Thursday, June 01, 2006 10:04 AM
I added lines 4900 through 5200 ... 2600- /******************************************************************** 2700- PGM 2800- MONMSG MSGID(CPF0000) 2900- /* A458A */ 3000- STRSBS QSERVER 3100- STRSBS SBSD(QSYS/QCTL) 3200- STRSBS SBSD(AMESYS/QSPL) 3300- STRSBS SBSD(AMESYS/QSNADS) 3400- STRCLNUP 3500- STRPRTWTR DEV(*ALL) 3600- STRSBS SBSD(AMESYS/QBATCH) 3700- STRSBS SBSD(AMESYS/QCMN) 3800- STRSBS SBSD(AMESYS/QINTER) 3900- STRSBS SBSD(QPGMR) 4500- /* A458A */ 4600- DLYJOB DLY(120) 4700- STRTCP 4800- MONMSG MSGID(CPF0000) ______________________________________________________________________ 4900- MONMSG CPF0000 5000- CHGLINETH LIND(ETHLIN01) ONLINE(*YES) DUPLEX(*FULL) 5100- MONMSG CPF0000 5200- VRYCFG CFGOBJ(ETHLIN01) CFGTYPE(*LIN) STATUS(*ON) ______________________________________________________________________ 5300- /* A458A */ 5400- DLYJOB DLY(120) 5500- STRHOSTSVR *ALL 5600- MONMSG MSGID(CPF0000) 5700- 6000- ENDPGM
-- 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.