Al,
Many years ago I had an auditor question me on everything.
I ran an SMPE job that produced many many hits in audit.
I decided the best way to show him exactly what I was doing was to
take the listing (in my case 6 boxes of paper) and explain everything
that was going on and why I got hit with an audit. After 3 hours he
called "you need to have this without question" I didn't mind it too
much but I got him off of my back for good.
Ed
On Feb 25, 2015, at 10:06 AM, Nims,Alva John (Al) wrote:
Side comment on this discussion about; "Remember, auditors can only
advise. They cannot compel." On What Planet are you ON? Okay,
maybe they do advise, but every time I have worked with Auditors
directly or indirectly, my MANAGEMENT has taken their word as
LAW!!!! :-) So I have had to do some ridiculous things for the
"Auditors!"
I really do not have any good suggestions for your problem. My
current setup we have all the SMPe data sets under a unique prefix
and service is received, applied & accepted in these data sets. I
run a copy job that copies and renames the data sets to build an
IPL volume and it's secondary volume.
In my last job we had a full SMPe setup for EACH LPAR (there were
about 50 of them) which had 2 sets based on the primary SYSRES
volume and some of the data sets would contain that volume serial
name. Each time we did service, we ran a copy job that copied,
renamed data sets and used SMPe UCLIN statements to make changes to
DDDEF's. I unfortunately do not have a copy of that JCL, it was a
little complicated.
Al Nims
Systems Admin/Programmer 3
Information Technology
University of Florida
(352) 273-1298
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-
[email protected]] On Behalf Of Staller, Allan
Sent: Wednesday, February 25, 2015 10:49 AM
To: [email protected]
Subject: Re: setting up a new, improved SMP/E environment
It might be better to document a procedure as follows:
1) Apply changes to MAINT, test. Resolve any issues. Repeat until
clean.
2) Migrate MAINT to DEV, and age for x days. Resolve any issues
and return to step 1.
3) migrate DEV to PROD.
If 3 separate zones target zones are really required, they should
be part of the migration process. SMP/E has commands to facilitate
migration of the zones.
The alternative is to run the apply/accept 3 times (once for each
zone).
Remember, auditors can only advise. They cannot compel.
HTH,
<snip>
We need to improve our SMP/E practice, and I am fishing for ideas -
for audit requirements, we need 3 separate target zones for our
MAINT, DEV and PROD environments - my idea would be to have 4
targets including a "W.I.P." one where I can apply the very latest
maintenance before deploying it.
Any ideas and suggestions will be gratefully accepted.
</snip>
----------------------------------------------------------------------
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
