"Ron MacRae" <ronmac...@hotmail.co.uk> wrote in message
news:<listserv%201105100956103069.0...@bama.ua.edu>...
> Hi all,
>        I hope someone can clear up some confusion on my part.
> 
> In the jes log for running jobs and stcs messages are produced of the
format -
> 
> 18.36.58 STC01465 ---- SATURDAY,  30 APR 2011 ---- 
> ...snip...
> 00.00.05 STC01465 ---- SUNDAY,    01 MAY 2011 ---- 
> ...snip...
> 00.00.05 STC01465 ---- MONDAY,    02 MAY 2011 ---- 
> ...snip...
> 00.00.05 STC01465 ---- TUESDAY,   03 MAY 2011 ---- 
> ...snip...
> 00.00.06 STC01465 ---- WEDNESDAY, 04 MAY 2011 ----
> ...snip...
> 00.06.49 STC01465 ---- THURSDAY,  05 MAY 2011 ---- 
> ...snip...
> 00.00.05 STC01465 ---- FRIDAY,    06 MAY 2011 ---- 
> ...snip...
> 
> The first one is produced when the STC starts and subsequent entries
appear 
> to be written the first time the STC becomes active on a specific day.
I.e. if 
> you start the stc on SATURDAY and it sits in a wait until noon on the
Tuesday 
> then the 2nd msg of this format is produced at noon on Tuesday and
there are 
> no msgs for intevening days.
> 
> However there are cases where the msg is not written until some time
later in 
> the day, Thursday in this example, and I know from output to other
files that 
> there was CPU and I/O activity prior to the time the msg was issued.
> 
> So my question is what event actually triggers this msg?
> 
> Thanks in advance, Ron.
> 

This feature was added ages ago to JES2 and is described in: SA22-7532
JES2 Initialization and Tuning Guide, chapter: JES2 system data sets.
"
To provide an indication when a particular message was logged for jobs
that run multiple days, JES2 provides day/date messages in the JES2
JOBLOG. The time stamp on the first message matches the time that the
first data record (PUT) was processed. The time stamp on all subsequent
day/date messages is always midnight (00.00.00). see Figure 25 to
illustrate the following example: If a job is submitted on day 1 (27 MAR
1995), issues no messages for the next three days (28, 29, and 30
March), and ends on day 5 (31 MAR 1995), the JOBLOG contains two dates
only; the first at the top of the JOBLOG when the job began and the
second before the end on day 5 at midnight. There is no entry for a day
in which no messages were logged, and therefore, never two consecutive
lines with the day/date message.
"

Kees.
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to