What's In A Name? - Revisited
MartinPacker 11000094DH Comment (1) Visits (4402)
I’ve used a title like this before.
This post is about gleaning information from names, specifically data set names.
Consider this one…
So what are we to make of this data set name?
It’s a real data set name, by the way, with only one obvious substitution.
What if I tell you the step name is
That gets us to
where I’m using the convention
What if I tell you this data set appears in a job that is part of a stream that kicked off on 30 November, 2017?
Then, and you probably guessed this,
That gets us to
and the data set name makes a lot of sense.
Now, it turns out that the
From SMF 30 I know that this job is one of a set of clones, being from Stream 4.
So you might fairly conclude the
So we could now decode the job as
You might’ve guessed that there would be a job called
So we reasonably decode the data set further:
This pattern is quite common in this batch application - where the data set name contains the writing program’s name and the reading program’s name. And the job names reflect their main program.
I think this takes us a long way further than just seeing the data set name raw.
So what does our code do?
What It Used To Do
It used to just recognise a job name in a data set name. This was most likely to occur in a temporary data set name.
from this same job (
This did appear in a fair number of permanent data sets, too. For some customers.
Now, this is new. If the code sees a step name in one of its data sets it bolds it.
What it can’t see is a different step from a different job.
If the creation date is like ‘D171130’ and it’s a data set qualifier it’s bolded.
If might be possible to detect other forms of date. For example,
In the example the low level qualifier (
As this example shows, there’s value in decoding data set names. Having code do it, spotting patterns for you, is the smarter way. And, in our case, bolding the detected pieces brings the reporting to life.
There are most certainly further insights that can be gained, such as when the SMFID is part of the name, or the prev
This machine is learning. But, as with ML, nobody’s quite sure what4 .