Re: qibm_qpwfs_file_server

sure but that would require a NEP or other process to process those entries
and do something.

Was hoping for a trigger at the source.

but thanks!

jay

On Mon, Feb 3, 2025 at 9:36 AM <stefan@xxxxxxxxxx> wrote:

At worst you can start journaling for the directories required and then
grab the entries in the journal.

Best regards

Stefan

--
No trees were killed in the sending of this message, but a large number of
electrons were terribly upset.

Stefan Tageson
+46 732 369934
stefan@xxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay
Vaughn
Sent: Monday, February 3, 2025 3:28 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: qibm_qpwfs_file_server

ok that makes sense.

So what exactly would be the exit point if I'm wanting to detect when a
file lands in an IFS directory?

Lets say it was ftp'd in... (but could be dropped in a directory other
than ftp so don't want to limit ourselves to a ftp exit point)...

I want an exit point to fire my pgm to let me know.

is there an exit point for that?

I know there is scan_open and scan_close - but I do believe those files
need to have a scan attribute assigned to them for the exit point to fire
for those.

Then there is the new open/close exit points in 7.5 BUT, we are not on 7.5
yet.

Any options?

thanks

jay

On Mon, Feb 3, 2025 at 9:23 AM <stefan@xxxxxxxxxx> wrote:

If the exit point is for NetServer methinks you need to create/remove
files using netserver - typically using a share.
Wrklnk et al are all native commands not executed using netserver.

Best regards

Stefan

--
No trees were killed in the sending of this message, but a large
number of electrons were terribly upset.

Stefan Tageson
+46 732 369934
stefan@xxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jay Vaughn
Sent: Monday, February 3, 2025 3:19 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: qibm_qpwfs_file_server

It has been some time since I've worked with this exit point.

I currently have a simple pgm registered to the exit point and have
restarted netsrv, but when I do my wrklnk and create a file or
directory I cannot get the exit program to fire.
I've attached to the pwfs0100 format and based on supported functions,
deleting/creating a file in the IFS should fire my exit pgm... right?

I even used an old exit program (that does other things I don't want
it to
do) that I tested to be sure my new pgm was ok, and I cannot get it to
reflect a last used date either on the pgm object when I take an IFS
action on a file.

When I change/add the exit pgm I am sure to restart the server (in a
series of steps I used in the past that would always work)...

What am I missing?

tia

Jay V
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.