On Jan 30, 2008, at 7:26 PM, Bruce Hewson wrote:
In regards to Ed's comments:
If your company wanted to write SMF records for internal
applications, then
instead of assigning a unique SMF record type to each application,
it would be
better to assign 1 SMF type, and then assign each application a unique
subtype number. That way your company's internal applications only
tie up 1
SMF record type.
Regards
Bruce Hewson.
Bruce,
Excellent point but what we found out that two many OEM programs had
to be altered to do this. The only way we could do it was to split
all the user SMF records off to another file (deleting them from the
cumulative file. Then we ran into auditing issues and were reluctant
to buck heads with the auditors. We asked the three vendors how to
handle the situation they all came back with different opinions. One
was to time consuming to implement as each time we got programs from
them (about 3 times a year) we had to insert logic to essentially
delete the smf records in question. The logic entailed changing 30
COBOL programs. In one case the other vendors were a little cleaner
and they were somewhat happy to have the records deleted before it
got to them but they both produced error messages that type XX were
missing and the accounting people weren't happy . Another vendor's
code was set to abend if they didn't get the records they were
expecting. We could not win. I suppose if its a home based system it
might be easier but again depending on what you are doing with them.
All but one of the OEM vendor products supplied source so yes we
could change it *BUT* the vendors would *NOT* support it. We thought
we had tried different options and none of them made everybody happy
we were in a catch 22. We tried for an exemption and they would not
hear of it. The one vendor want to have the record layouts of every
vendor that cut SMF records. That was sort of OK but the lead time
was at least 1 year. It got so bad between the vendors and internal
politics and legal (auditors) we thought of creating two master tapes
but that was a nightmare as the number of tapes was depleting our
tape library with just one set if we had asked for more we would
have been told no in no uncertain terms (we did approach the manager
of the Library and he told us *NO* he was way over budget as it was).
I don't remember the number of tapes but at the time we were growing
by leaps and bounds and the library was threatening to have to
acquire more space to accommodate them and we did NOT have more space
(we had the entire building or at least the office space we had a
restaurant in the basement and a small bank as well. The only option
was to go into offsite storage and that would have set the budget
skyrocketing.
It was not fun but the place to work for was really good with their
employees and we did try and make everyone happy but were
unsuccessful and we were looked down on because we weren't a "team
player", SIGH.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
