Re: SIGNOFF ENDCNN(*YES) without disconnecting iSeries Access -- MIDRANGE-L

Subject: Re: SIGNOFF ENDCNN(*YES) without disconnecting iSeries Access
From: Dave Kahn <dkahn400@xxxxxxxxxxxxxx>
Date: Mon, 6 Jul 2009 16:51:47 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

2009/7/6 DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx>:

Would a command validation exit program help you with this? Seems like you could retrieve the call stack of the job requesting the SIGNOFF command, determine whether you need ENDCNN(*YES) or not, then execute the amended command string.

Just a WAG...

Wife and girfriend? :-)

I don't think that helps. The call stack relates to the job. Each
Telnet session is a job in its own right so the call stack of a lower
level job looks exactly the same as that of the top level one.

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.