Unless you have more than 36 QHST files in a 24 hour period. But, maybe IBM doesn't expect that to occur.
Take for example the text description for a QHST file 11402032131511140207093416.
The first 13 characters (1140203213151) defines the date and time the file was created. The format is CYYMMDDHHMMSS.
The last 13 characters (1140207093416) defines the date and time it became full. The format is CYYMMDDHHMMSS. It is also the first 13 characters of the next QHST file.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Wednesday, March 05, 2014 11:00 AM
To: Midrange Systems Technical Discussion
Subject: Re: Quick question about QHSTxxxxxx PFs
On 3/5/14 10:36 AM, CRPence wrote:
The order of the records, collated by the names of the files
listed, is not necessarily a chronological ordering.
Actually, *IF* (as you say) the records are guaranteed to be collated by name, I found something straight from the relevant equine masticatory
When a log-version is full, a new version of the log is automatically > created. Each version is a physical file that is named in the > following way:
where the following is true:
xxx Is a 3-character description of the log type (HST)
yyddd Is the Julian date of the first message in the log version
n Is a sequence number within the Julian date
(A through Z and 0 through 9)
which tells me they would only break chronological sequence if they somehow crossed a century boundary, which is (to say the least) unlikely to happen again within the product life of IBM midrange systems.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l