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

Narayanan,

If memory serves for performance reasons the exit point program is
determined when subsystem QSERVER starts. This means you will have to
end the host servers, end subsystem QSERVER, restart subsystem QSERVER
and restart the host servers.

A "quick" way to get your exit programs recognized by the servers is to
bring the system to a restricted state and then restart your controlling
subsystem. This may seem heavy handed but it works.

The host servers are listed by function at IBM's InfoCenter for V6R1.

Connecting to System i
System I Access for Windows
Administration
Host server administration
Identify i5/OS host servers and associated programs
Host servers by function

Also, think about adding some form of auditing to your exit program. It
will greatly aid in determining what is occurring. This can be as
simple as sending yourself a message saying "Exit program ABC was
called." or as complex as you feel is needed.

Hope this helps.

Gary Monnier

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

Do you have to register your exit program? WRKREGINF option 8 next to
the exit point. Do not use library list but specify the actual library.
Verify the program name. Check authority to the program and any objects
that it references. Looks like the jobs run under QUSER but adopt
authority to the actual user. Give public full access as a test, then
figure out the proper authority and please document your findings on
this list.