MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

RE: Quick question about QHSTxxxxxx PFs



fixed

Didn't mean to stutter James. :)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Wednesday, March 05, 2014 10:44 AM
To: Midrange Systems Technical Discussion
Subject: RE: Quick question about QHSTxxxxxx PFs

James,

James,

As an alternative to DSPOBJD you could use a combination of the following APIs to build an array, user index or keyed table.

Create User Space (QUSCRTUS) API
Delete User Space (QUSDLTUS) API
List Objects (QUSLOBJ) API
Convert Date and Time Format (QWCCVTDT) API if you want to convert date and time in format OBJL0400
Retrieve Pointer to User Space (QUSPTRUS) API or Retrieve User Space (QUSRTVUS) API to obtain the list contents

If you only want the QHSTxxxxxx names and descriptions, QUSLOBJ format OBJL0200 will give you that information pretty quickly. Interpreting the text will give you the PF's creation date and time.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Wednesday, March 05, 2014 10:13 AM
To: Midrange Systems Technical Discussion
Subject: Quick question about QHSTxxxxxx PFs

Filter-funneling the first two records of all history log entries pertaining to specified jobnames into a receiver file, programmatically, in chronological order, with a CL program calling an RPG Cycle program.

If I do this,
DSPOBJD OBJ(QSYS/QHST*) OBJTYPE(*FILE) +
OUTPUT(*OUTFILE) OUTFILE(QTEMP/HISTLIST)
to get my list of the extant history log PFs on the system, are the records in HISTLIST then guaranteed to reflect a chronological sequence of QHSTxxxxxx files?

Or do I need to use a keyed receiver file in order to force chronological sequence?

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

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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact