Re: QIBM_QPWFS_FILE_SERV - V6R1 - Fails to call(?)

Actually Chris, not all of them do. The odd thing about Exit points is that each one is it's own separate animal.

I first got into exit programs thinking there would be some semblance of uniformity about how they were all implemented, but it's not like there was an exit point 'team' at IBM. The folks who implemented the File Server would implement the exit point just a little different than the team responsible for the ODBC server, and so on and so on.

Ending and restarting a subsystem is a pretty solid way to flush your network services exit program, but it is not strictly required of each one.

jte


On Feb 8, 2011, at 8:04 AM, Chris Bipes wrote:

I want to thank all of you who contributed. I have learned the easy way
about exit points needing the subsystem to restart. That is before I
actually wrote any. ;-))

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Narayanan Pillai
Sent: Tuesday, February 08, 2011 7:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: QIBM_QPWFS_FILE_SERV - V6R1 - Fails to call(?)

Chris,

Thanks, that is a step I missed mentioning. But we did do that. The
trick was to restart QSERVER. And Joe's suggestion to have a "Controller
Exit Program" that calls the "Real Exit Program" because recompiles
require subsystem restart :(

--
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.

--
John Earl
President and CEO,
Townsend Security
360-359-4418
townsendsecurity.com
The Encryption Company