Re: Ifs stmf and qibm_qp0l_scan_open

thanks john, but you are describing such freedom, because...

when you do a DSPF, you are talking about ANOTHER job being able to
modify/delete the file you did the DSPF on, not the same job that has it
open. :)
furthermore... you most likely do not have an exit pgm registered to
QIBM_QP0L_SCAN_OPEN (and/or CLOSE)...
... if you did, then do you really think you would be able to modify the
contents of the file you did the DSPF on within your exit pgm, within the
same job that did the DSPF? :)

Probably not because it is your job/exit pgm that has the file opened (and
"locked")... right?

But I am not here to tell you that you can't, I am wanting to confirm this
and be sure because I really would like to modify that file within my exit
pgm.

That should probably make it clearer as to exactly what I want to do.

Thanks for the input - your thoughts?

Jay

On Fri, Jan 15, 2021 at 4:25 PM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Fri, Jan 15, 2021 at 3:26 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

If I have an exit pgm on the above mentioned exit point and in that pgm

I want to modify the file that just opened (let’s say clear it)... is that
even possible in this situation?

I’ve tried it and it says the file is locked to my current job.. no

surprise. So In the exit pgm, before I try to modify I have tried closing
the file, CHKIN, RLSIFSLCK and nothing will release the lock to allow me to
clear the file.

Am I attempting the impossible?

Oh the method of opening it in this situation is simply an option 5 to

display it from a WRKLNK cmd.

I'm not sure if it's impossible, because I don't understand the
specifics of what you're trying to do.

But I will offer this: If you open a (stream) file using DSPF (which
is what WRKLNK option 5 is), you can still do whatever you want to
that file via other means. For example, you can delete (RMVLNK or
WRKLNK option 4) or edit (EDTF or WRKLNK option 2) the file from
another session, and the screen which is showing DSPF will obliviously
keep showing that file until you exit from it, even though the file
may not exist anymore.

Actually, just now I tried opening a file with EDTF, and that doesn't
prevent deletion or modification from another session either. On one
session, use EDTF; then on another use RMVLNK, and the file is gone;
but then on the first session, continue editing and save, and then the
file is back again. Or open dueling edits on two sessions. Still works
(last save wins).

So, it seems that *in principle* just having something open in DSPF
(or even EDTF) shouldn't prevent it from being modified by something
else.

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com