My bad, the daily SMF dump job did NOT run at 2:00 AM on May 11th as it was 
scheduled to run.  That job was supposed to dump data for the 10th.  There was 
testing going on for the replacement joblog/sysout archiver software that 
caused all scheduled jobs on the sandbox LPAR for May 11th to wait for a reply. 
 I was not contacted until after midnight on May 12th, which is when I replied 
to the messages.  Since the SMF dump job uses the RELATIVEDATE(BYDAY,1,1) 
parameter, this caused the job to dump the May 11th data.

Ding, ding user error (and I am the user)!




Sent with Proton Mail secure email.

On Monday, June 3rd, 2024 at 1:12 PM, Michael Oujesky <[email protected]> 
wrote:

> What records are not missing from Sandbaox on May 10th? Do you have
> the job logs from SMF off-loading for may 10th data? What do the 2
> and 3 SMF record time-stamps from the May 10th -look like?
> 
> Michael
> 
> At 09:06 AM 6/3/2024, rpinion865 wrote:
> 
> > Content-Transfer-Encoding: base64We are running z/OS 2.4 on a z15
> > with three LPARs (Production, Development, and Sandbox). We use SMF
> > log streams to collect our SMF records. We kick off a batch job
> > everyday at 2:00 to capture the previous day's SMF records from the
> > log stream, and write them to a GDG dataset. SMF Type 89 is turned
> > on for all LPARs.
> > 
> > This past month, May, our Sandbox LPAR has 23 hours missing on May
> > 10th. The LPAR was up on May 10th. Yet, there are no TYPE 89 records
> > from 00:00 to 23:00 on May 10th. I cannot determine why the SMF Type
> > 89s were not cut for that day. I have the syslog for that day and
> > have looked at the messages after midnight of the 10th. But I do not
> > see anything regarding TYPE 89 records. What else can I do to
> > determine why the 89s were not cut for that one day only? Thanks in advance.
> > 
> > Sent with Proton Mail secure email.
> > 
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to