Synchronous Dial Up Line will not Drop

[Guest.Visitor]

We have a synchronous dialup link to another AS/400 that will not end on it's own. The line/ctl/dev all sit out there with no active jobs under them after a SNADS file finishes or a PASSTHRU session ends and never drops. I thought that the DSCTMR(1 1) would have made it drop after no activity for 1 second... Any ideas are greatly appreciated! TIA, JC O/S = V4R3 Modem = IBM 7852 w/factory switch settings Line/ctl/dev = CRTLINSDLC LIND(SWITCH01) RSRCNAME(CMN11) ONLINE(*NO) ROLE(*PRI) + INTERFACE(*RS232V24) CNN(*SWTPP) VRYWAIT(*NOWAIT) + AUTOCALL(*NO) EXCHID(05600000) NRZI(*YES) MAXCTL(1) + CLOCK(*MODEM) LINESPEED(9600) MODEM(*V54) + SWTCNN(*BOTH) AUTOANS(*YES) AUTODIAL(*YES) + DIALCMD(*V25BIS) CALLNBR(*NONE) CNNPOLLRTY(7) + MAXFRAME(521) DUPLEX(*FULL) NPRDRCVTMR(320) IDLTMR(30) + CNNPOLLTMR(30) POLLPAUSE(0) FRAMERTY(7) DSRDRPTMR(6) + AUTOANSTYP(*DTR) RMTANSTMR(60) MODEMRATE(*FULL) + THRESHOLD(*OFF) MODULUS(8) MAXOUT(7) CTSTMR(25) + LINKSPEED(9600) COSTCNN(128) COSTBYTE(128) + SECURITY(*NONSECURE) PRPDLY(*TELEPHONE) USRDFN1(128) + USRDFN2(128) USRDFN3(128) CMNRCYLMT(2 5) CRTCTLAPPC CTLD(SWITCH01) LINKTYPE(*SDLC) ONLINE(*YES) + SWITCHED(*YES) SHM(*NO) APPN(*NO) MAXFRAME(521) + RMTNETID(FRIBM000) RMTCPNAME(SWITCH01) + EXCHID(05600250) INLCNN(*DIAL) DIALINIT(*IMMED) + CNNNBR('011-44-4-44-44-44-44') ROLE(*SEC) STNADR(28) + AUTOCRTDEV(*ALL) CODE(*EBCDIC) PREDIALDLY(6) + REDIALDLY(120) DIALRTY(2) SWTDSC(*YES) DSCTMR(1 1) + POLLPTY(*NO) POLLLMT(0) OUTLMT(*POLLLMT) CNNPOLLRTY(7) + NDMPOLLTMR(*CALC) CMNRCYLMT(2 5) CRTDEVAPPC DEVD(SWITCH01) RMTLOCNAME(SWITCH01) ONLINE(*YES) + LCLLOCNAME(*NETATR) RMTNETID(*NONE) CTL(SWITCH01) + MODE(LU62) MSGQ(*LIBL/QSYSOPR) APPN(*NO) SNGSSN(*NO) + SECURELOC(*NO) LOCADR(00) CHGCTLAPPC CTLD(SWITCH01) SWTLINLST(SWITCH01)

[rkc@entrack.com]

I did not realize the line should end unless it is varied off. Are you attempting to vary it off? Ron

[Guest.Visitor]

I would like the line to drop after all sessions quit. For example, if there is a long running SNADS transmission, I would like the line to drop and go to CONNECT PENDING. Currently, it stays ACTIVE (along with the controlelr and device). With international calls, the costs are quite high if it stays up for a long time. Thanks, JC

[Guest.Visitor]

Write a short CL program that starts passthrough to the location you want. This CL will vary on the controller and line and then start passthrough. When passthrough ends, vary off the controller and line. Attach a short command to the cl to make it simple. For example, if you are passing through to London, name the command LONDON and the CL LONDONC (or whatever). Then when you want to connect to London, just type LONDON from a command line and that will vary on the appropriate devices and lines and controllers and away you go. When you're done, they'll all get varyied off and go back to connect pending status.

[Guest.Visitor]

Thanks Shannon. As a matter of fact, that is how I have done it so far... my main problem now is SNADS transmissions. These could last for hours. I could write a program that monitors for the message after the file completes, but that is not as elegent as I know it should be.

[Guest.Visitor]

May I make a few suggestions? 1. Do not vary off the line, except maybe for weekends. This will enable 2-way transmission. So people from the other end can start their own sessions. 2. Vary off the controller, then vary on again after about 5 minutes. This is enough to terminate the connection, but you need to vary on the controller again to allow 2-way transmission. 3. Instead of monitoring for transmission-end, monitor for number of users. End-of-transmission does not mean end-of-use. What if someone is connected on-line (via STRPASTHR for example)? 4. Include this CL in your AS/400's startup program (to ensure that the line is constantly monitored).

[Guest.Visitor]

Try changing DSCTMR(1 1) to DSCTMR(170 30). That's the way I'm set up and it works fine. What it's saying is if no communications have been active (DSPT, SNADS, etc.) for 170 seconds, wait 30 seconds and disconnect. Keep in mind, a display sitting at a remote signon screen is considered active. You may also want to check your distribution queues to see how often they are attempting to transmit. If they are less than the disconnect time, that may cause the timer to reset.