Re: Monitoring IFS objects for deletion at V5R4 -- MIDRANGE-L

Subject: Re: Monitoring IFS objects for deletion at V5R4
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 07 Sep 2011 08:36:17 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Evan Harris wrote:

Display the journal to an outfile then query for the Journal type
codes you are looking for.

The only problem with that is that the entry-specific data gets truncated at 100 characters, and the pathname of the IFS object comes in at byte 740 of that field.

Displaying to a spool file seems to work somewhat better.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Monitoring IFS objects for deletion at V5R4 , Jeff Young
Re: Monitoring IFS objects for deletion at V5R4 , Luis Rodriguez

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.