Re: Journal Code F - Type IZ - INZPFM -- MIDRANGE-L

Subject: Re: Journal Code F - Type IZ - INZPFM
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 9 Oct 2019 12:19:15 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Wed, Oct 9, 2019 at 11:59 AM Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>
wrote:

Oh I have. Hence my comments that the programs are NOT doing anything
explicitly to initialize any records or members in the file.

There be mysterious sea monsters in the depths of OS/400.

Until I screen-share debugged with a major vendor, I never knew that what
we mere programmers call a "lock" is a high-level abstraction and there is
something lower in the kernel called a "seize". And that further, when any
file in a library creates a member, there is a "seize" on the entire
library. So there may be an analogous mystery in your case.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Journal Code F - Type IZ - INZPFM , Gord Hutchinson

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.