Re: Telnet Exit Program Problem

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Ray,

Are you using the DEVINIT1 or DEVINIT2 exit program?  Did you make any changes 
to the program?

I will assume DEVINIT2 because it actually does stuff with the virtual devices. 
 I will also 
assume no changes were made to the code.

Are you using wildcard device names?

DEVINIT2 will check the status of a generically named device before returning 
and only allow 
VARIED-ON and VARIED-ON-PENDING.  However, you may find that the list of 
partial devices is 
becoming very large and DEVINIT2 is taking too long to process them.  There is 
a chance that 
the exit program is taking more than 10 seconds to complete which may be 
contributing to your 
problem.  You can set a *TIMING value in the data area used by the exit 
programs to gather 
timing statistics.  You can also turn *DEBUG on and trace the exit program.  
Read the comments 
in the C program headers.  You can also use the RMVDEVD command supplied with 
the exit programs 
to reduce the number of virtual devices.

Are you using named device support?  

If so you may be running into a problem where the TELNET server doesn't know 
the device isn't 
available because the virtual terminal API doesn't return an indication of a 
device in use or 
varied-off and appears to hang.

I've known about this problem for a while (because it was causing problems in 
my TELNET server) 
but Jeffrey Stevens has recently informed me of the PTFs to fix that issue:

  V4R4 - SF59213
  V4R3 - SF58955
  V4R2 - SF59303 (Test PTF)

PS: With the virtual device support being extended to character values 
(0000-ZZZZ) has anybody 
got devices with rude names?  You know, QAPDEVF**K, for instance.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
//--- forwarded letter -------------------------------------------------------
> X-Mailer: Mozilla 4.5 [en] (Win95; U)
> Date: Tue, 26 Oct 1999 16:16:07 -0500
> From: "Ray Peterson" <rpeterso@witc.tec.wi.us>
> To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
> Reply-To: MIDRANGE-L@midrange.com
> Subject: Telnet Exit Program Problem

> 
> We downloaded and created the "Telnet Exit Program" examples from IBM's
> AS/400 Web Site last July.  Everything seemed to be working OK until
> recently when we discovered that if one of the devices being used
> becomes "varied off", all new sessions are blocked until the device is
> "varied on".  Has anyone else experienced this problem?  Or was it
> designed this way intentionally?
> 
> This software is written in "C" and while I have the compiler, I'm
> certainly not a "C" programmer, thus I'm kind of lost.
> 
> tia
> 
> Ray

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---