RE: DSCJOB - the mystery thickens

["Shaw, David" <dshaw@xxxxxxxxxxx>]

David,

You cannot, and never could, disconnect a telnet session that didn't have a
fixed session name.  QPADEVxxxx device names are dynamically assigned.  If you
shut down Telnet and restart it there is no guarantee that you would get that
session name again, since the remote system (PC) doesn't store it.  The "server
job" that it's talking about is the background communications server job that
monitors your Telnet connection, analogous to the Passthru monitor jobs when
using SNA 5250 emulation.  That job gets hooked into a device name at startup,
and it knows it can't control a disconnected job if the remote machine doesn't
remember the session name.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: David Shea [mailto:dshea@arctools.com]
> 
> I posted a message earlier today that I couldn't DSCJOB a 
> telnet job when I
> could last week (pre PTF).  Well, it gets better.
> 
> I can DSCJOB a job running from a real terminal (in this 
> case, a 3197 on a
> twinax controller).
> 
> I can NOT dscjob a Windows Telnet session started from a Win 95 box.
> 
> I CAN dscjob a Windows Telnet job from an NT Server box.
> 
> I CAN dscjob a CA Express telnet connection from EITHER a 95 OR a NT
> machine.
> 
> When I try to DSCJOB a Windows telnet session from the 95 
> box, I get the
> following error message:
> 
> CPF1358 - DSCJOB not allowed for Server Jobs.
> 
> Cause . . . . . :   Job 022479/QSECOFR/QPADEV0006 is either a 
> server job, or
> a client job with a server job active at the device.
>  Recovery  . . . :   Do the following:
>      -- From the server job, select the option to display the 
> System Request
>    menu on the client job.
>      -- Select the option to disconnect the client job.
>      When you use the DSCJOB command, the connection between 
> the client and
> server jobs is dropped.
> 
> Sooooo.... what's the difference between a Windows Telnet job 
> from an NT
> server  box and a Windows Telnet job from a 95 box????  Why 
> the heck is a
> Windows Telnet job from a 95 box being flagged as a 'Server' 
> job???  Very
> strange...
+---
| 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
+---