When using IFASMFDL for extracting SMF-data, job might end with RC=08-0804 if no data is in the log stream

See also case TS017633432.

In brief: we are writing SMF data to logstreams (As recommended by IBM). We are having different LogStreams in order to pre-select the SMF-records.

On Log-Stream is for DB2-SMF records in which we collect records 100:102.

Every night at 2 o'clock the Logstream is dumped via IFASMFDL.  Lately we had the batch job doing this ending with RC=08-0804. When restarting hours laterm the job would run fine with RC=0.

The reason for the RC=8 was, that the DB2 systems were stopped on sundays. So, when trying to dump/archive SMF data on Monday, there was no entry in the logstream since saturday. That causes IFASMFDL to end with RC=8-0804.

In our opinion that is not correct, since there simplay was no entry for the days, so in our opinion the job should end with RC=0 or maybe RC=4 but not with RC=8.

IFASMFDL has the information, if the logstream exists and it also has the information if the requested date lays in the future. So, at least it should react with a more specific message .

RC=8 causes our scheduluing team to intervene, create a ticket etc. As mentioned, in our opionion that is not correct. 

We are now also writing the SMF-Type 89 to the DB2 logstream and exclude them from the dump. The SMF-89 are not many records, but they are written regulary so that there is an entry in the logstream and the IFASMFDL does not end with RC=8.

Ideas: 

- have a SMF-record  be written every day or even hour in order to have a timestamp. 

- have a SMF-record be written  whenever a IFASMFDL job is running / receiving an 0804

- have a different and more specific RC and message in a situation like that.

Thanks a lot and best regards,

Mario