Re: Promote specific modules from service root
I must not be understanding something as I received and offline email telling me these commands would not back sub-directories, However on my z/OS 1.12 lpar. I receive the following messages which indicated they are backup up. What's the difference? I made an assumption, right or wrong you run this with superuser, we also temporarily changed from a R/O to R/W mount, to perform the restores. /usr/lpp/gskssl/IBM/ /usr/lpp/gskssl/IBM/GSKAH001 /usr/lpp/gskssl/IBM/GSKAH002 /usr/lpp/gskssl/IBM/GSKAH003 /usr/lpp/gskssl/IBM/GSKAH004 /usr/lpp/gskssl/IBM/GSKAH005 /usr/lpp/gskssl/IBM/GSKAH006 /usr/lpp/gskssl/IBM/GSKAH007 /usr/lpp/gskssl/IBM/GSKAH008 /usr/lpp/gskssl/IBM/GSKAH009 /usr/lpp/gskssl/IBM/GSKAH010 /usr/lpp/gskssl/IBM/GSKAH011 /usr/lpp/gskssl/IBM/GSKAH039 /usr/lpp/gskssl/IBM/GSKAH040 /usr/lpp/gskssl/IBM/GSKAH041 /usr/lpp/gskssl/IBM/GSKAH042 /usr/lpp/gskssl/IBM/GSKAH043 /usr/lpp/gskssl/IBM/GSKAH055 /usr/lpp/gskssl/IBM/GSKAH056 /usr/lpp/gskssl/IBM/GSKAH057 /usr/lpp/gskssl/IBM/GSKAM003 /usr/lpp/gskssl/IBM/GSKLM015 /usr/lpp/gskssl/bin/ /usr/lpp/gskssl/bin/gskkyman /usr/lpp/gskssl/bin/gsktrace /usr/lpp/gskssl/examples/ /usr/lpp/gskssl/examples/client.cpp /usr/lpp/gskssl/examples/common.cpp /usr/lpp/gskssl/examples/common.hpp /usr/lpp/gskssl/examples/display_certificate.c /usr/lpp/gskssl/examples/gsksrvr.envar /usr/lpp/gskssl/examples/secures.cpp /usr/lpp/gskssl/examples/secures.h /usr/lpp/gskssl/examples/server.cpp /usr/lpp/gskssl/examples/utils.cpp /usr/lpp/gskssl/examples/utils.hpp /usr/lpp/gskssl/examples/Makefile /usr/lpp/gskssl/include/ /usr/lpp/gskssl/include/gskcms.h /usr/lpp/gskssl/include/gskssl.h /usr/lpp/gskssl/include/gsktypes.h /usr/lpp/gskssl/lib/ /usr/lpp/gskssl/lib/nls/ /usr/lpp/gskssl/lib/nls/msg/ /usr/lpp/gskssl/lib/nls/msg/En_US.IBM-1047/ /usr/lpp/gskssl/lib/nls/msg/En_US.IBM-1047/gskmsgs.cat /usr/lpp/gskssl/lib/nls/msg/Ja_JP.IBM-939/ /usr/lpp/gskssl/lib/GSKCMS31.x /usr/lpp/gskssl/lib/GSKCMS64.x /usr/lpp/gskssl/lib/GSKSSL.x /usr/lpp/gskssl/lib/GSKSSL64.x Compression: 71.22% /usr/lpp/internet/bin/IBM/ /usr/lpp/internet/bin/IBM/IMWCACHE /usr/lpp/internet/bin/IBM/IMWFCGI /usr/lpp/internet/bin/IBM/IMWGSKIP /usr/lpp/internet/bin/IBM/IMWJAVDL /usr/lpp/internet/bin/IBM/IMWJGIW /usr/lpp/internet/bin/IBM/IMWOCGPR /usr/lpp/internet/bin/IBM/IMWOCGTL /usr/lpp/internet/bin/IBM/IMWOHTAP /usr/lpp/internet/bin/IBM/IMWSCONT /usr/lpp/internet/bin/IBM/IMWSOEDS /usr/lpp/internet/bin/IBM/IMWYWWUS /usr/lpp/internet/bin/IMWX00.so /usr/lpp/internet/bin/Jav_dll.so /usr/lpp/internet/bin/cacheagt /usr/lpp/internet/bin/cgiparse /usr/lpp/internet/bin/cgiutils /usr/lpp/internet/bin/gskipc.so /usr/lpp/internet/bin/htcounter.so /usr/lpp/internet/bin/htjgiwrapper /usr/lpp/internet/bin/libfcgi.so /usr/lpp/internet/bin/libhttpdapi.so /usr/lpp/internet/bin/mvsds.so /usr/lpp/internet/bin/wwwus.so Compression: 64.03% /usr/lpp/internet/sbin/IBM/ /usr/lpp/internet/sbin/IBM/HTTPD /usr/lpp/internet/sbin/IBM/IMWHTTPH /usr/lpp/internet/sbin/IBM/IMWLGRPJ /usr/lpp/internet/sbin/IBM/IMWOHTDM /usr/lpp/internet/sbin/IBM/IMWOWWWC /usr/lpp/internet/sbin/IBM/IMWSERVR /usr/lpp/internet/sbin/IBM/IMWSETUP /usr/lpp/internet/sbin/IBM/IMWSTCFG /usr/lpp/internet/sbin/IBM/IMWSTLNS /usr/lpp/internet/sbin/IBM/IMWSTTGT /usr/lpp/internet/sbin/IBM/IMWUSAGE /usr/lpp/internet/sbin/htadm /usr/lpp/internet/sbin/htlogrep /usr/lpp/internet/sbin/httpd /usr/lpp/internet/sbin/httpd_V5R3M0 /usr/lpp/internet/sbin/setup.sh /usr/lpp/internet/sbin/setupcfg.sh /usr/lpp/internet/sbin/setuplns.sh /usr/lpp/internet/sbin/setuptgt.sh /usr/lpp/internet/sbin/webusage /usr/lpp/internet/sbin/wwwcmd Compression: 69.29% Thanks Ms. Terri E. Shaffer terri.e.shaf...@jpmchase.com z/OS Engineer J.P.Morgan Chase Co. GTI ECS Enterprise Software Engineering (ESE) or Extreme Software Engineering Office: # 614-213-3467 Cell: # 412-519-2592 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Friday, January 04, 2013 4:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Promote specific modules from service root I just looked and I think Ms. Shaffer gave you a better solution using pax
Re: Promote specific modules from service root
My system is z/OS 1.11. I used uid(0). With the trailing /* the pax did not do
the subdirectories. When I left it off, I got a list similar to yours.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Shaffer, Terri E
Sent: Monday, January 07, 2013 7:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Promote specific modules from service root
I must not be understanding something as I received and offline email
telling me these commands would not back sub-directories, However on my
z/OS 1.12 lpar. I receive the following messages which indicated they
are backup up. What's the difference? I made an assumption, right or
wrong you run this with superuser, we also temporarily changed from a
R/O to R/W mount, to perform the restores.
/usr/lpp/gskssl/IBM/
/usr/lpp/gskssl/IBM/GSKAH001
/usr/lpp/gskssl/IBM/GSKAH002
/usr/lpp/gskssl/IBM/GSKAH003
/usr/lpp/gskssl/IBM/GSKAH004
/usr/lpp/gskssl/IBM/GSKAH005
/usr/lpp/gskssl/IBM/GSKAH006
/usr/lpp/gskssl/IBM/GSKAH007
/usr/lpp/gskssl/IBM/GSKAH008
/usr/lpp/gskssl/IBM/GSKAH009
/usr/lpp/gskssl/IBM/GSKAH010
/usr/lpp/gskssl/IBM/GSKAH011
/usr/lpp/gskssl/IBM/GSKAH039
/usr/lpp/gskssl/IBM/GSKAH040
/usr/lpp/gskssl/IBM/GSKAH041
/usr/lpp/gskssl/IBM/GSKAH042
/usr/lpp/gskssl/IBM/GSKAH043
/usr/lpp/gskssl/IBM/GSKAH055
/usr/lpp/gskssl/IBM/GSKAH056
/usr/lpp/gskssl/IBM/GSKAH057
/usr/lpp/gskssl/IBM/GSKAM003
/usr/lpp/gskssl/IBM/GSKLM015
/usr/lpp/gskssl/bin/
/usr/lpp/gskssl/bin/gskkyman
/usr/lpp/gskssl/bin/gsktrace
/usr/lpp/gskssl/examples/
/usr/lpp/gskssl/examples/client.cpp
/usr/lpp/gskssl/examples/common.cpp
/usr/lpp/gskssl/examples/common.hpp
/usr/lpp/gskssl/examples/display_certificate.c
/usr/lpp/gskssl/examples/gsksrvr.envar
/usr/lpp/gskssl/examples/secures.cpp
/usr/lpp/gskssl/examples/secures.h
/usr/lpp/gskssl/examples/server.cpp
/usr/lpp/gskssl/examples/utils.cpp
/usr/lpp/gskssl/examples/utils.hpp
/usr/lpp/gskssl/examples/Makefile
/usr/lpp/gskssl/include/
/usr/lpp/gskssl/include/gskcms.h
/usr/lpp/gskssl/include/gskssl.h
/usr/lpp/gskssl/include/gsktypes.h
/usr/lpp/gskssl/lib/
/usr/lpp/gskssl/lib/nls/
/usr/lpp/gskssl/lib/nls/msg/
/usr/lpp/gskssl/lib/nls/msg/En_US.IBM-1047/
/usr/lpp/gskssl/lib/nls/msg/En_US.IBM-1047/gskmsgs.cat
/usr/lpp/gskssl/lib/nls/msg/Ja_JP.IBM-939/
/usr/lpp/gskssl/lib/GSKCMS31.x
/usr/lpp/gskssl/lib/GSKCMS64.x
/usr/lpp/gskssl/lib/GSKSSL.x
/usr/lpp/gskssl/lib/GSKSSL64.x
Compression: 71.22%
/usr/lpp/internet/bin/IBM/
/usr/lpp/internet/bin/IBM/IMWCACHE
/usr/lpp/internet/bin/IBM/IMWFCGI
/usr/lpp/internet/bin/IBM/IMWGSKIP
/usr/lpp/internet/bin/IBM/IMWJAVDL
/usr/lpp/internet/bin/IBM/IMWJGIW
/usr/lpp/internet/bin/IBM/IMWOCGPR
/usr/lpp/internet/bin/IBM/IMWOCGTL
/usr/lpp/internet/bin/IBM/IMWOHTAP
/usr/lpp/internet/bin/IBM/IMWSCONT
/usr/lpp/internet/bin/IBM/IMWSOEDS
/usr/lpp/internet/bin/IBM/IMWYWWUS
/usr/lpp/internet/bin/IMWX00.so
/usr/lpp/internet/bin/Jav_dll.so
/usr/lpp/internet/bin/cacheagt
/usr/lpp/internet/bin/cgiparse
/usr/lpp/internet/bin/cgiutils
/usr/lpp/internet/bin/gskipc.so
/usr/lpp/internet/bin/htcounter.so
/usr/lpp/internet/bin/htjgiwrapper
/usr/lpp/internet/bin/libfcgi.so
/usr/lpp/internet/bin/libhttpdapi.so
/usr/lpp/internet/bin/mvsds.so
/usr/lpp/internet/bin/wwwus.so
Compression: 64.03%
/usr/lpp/internet/sbin/IBM/
/usr/lpp/internet/sbin/IBM/HTTPD
/usr/lpp/internet/sbin/IBM/IMWHTTPH
/usr/lpp/internet/sbin/IBM/IMWLGRPJ
/usr/lpp/internet/sbin/IBM/IMWOHTDM
/usr/lpp/internet/sbin/IBM/IMWOWWWC
/usr/lpp/internet/sbin/IBM/IMWSERVR
/usr/lpp/internet/sbin/IBM/IMWSETUP
/usr/lpp/internet/sbin/IBM/IMWSTCFG
/usr/lpp/internet/sbin/IBM/IMWSTLNS
/usr/lpp/internet/sbin/IBM/IMWSTTGT
/usr/lpp/internet/sbin/IBM/IMWUSAGE
/usr/lpp/internet/sbin/htadm
/usr/lpp/internet/sbin/htlogrep
/usr/lpp/internet/sbin/httpd
/usr/lpp/internet/sbin/httpd_V5R3M0
/usr/lpp/internet/sbin/setup.sh
/usr/lpp/internet/sbin/setupcfg.sh
/usr/lpp/internet/sbin/setuplns.sh
/usr/lpp/internet/sbin/setuptgt.sh
/usr/lpp/internet/sbin/webusage
/usr/lpp/internet/sbin/wwwcmd
Compression: 69.29%
Thanks
Ms. Terri E. Shaffer
terri.e.shaf...@jpmchase.com
z/OS Engineer
J.P.Morgan Chase Co.
GTI ECS Enterprise Software Engineering (ESE) or Extreme Software
Engineering
Office: # 614-213-3467
Cell: # 412-519-2592
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of John McKown
Sent: Friday, January 04, 2013 4:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Promote specific modules from service root
I just looked and I think Ms. Shaffer gave you a better solution using
pax. It addresses the problems I mention at the end of my post.
But on the off chance you're interesting, just as a curiosity, you
could do something like:
su - #switch to root
cd /Service/sub/directory #change to subdirectory
oldDir=${PWD#/Service} #strip leading /Service from name of current
Promote specific modules from service root
Normally, I apply maintenance to a copy mounted at /Service (or sometimes /Zervice :) and deploy by making a copy of the new root ZFS file (and the SYSRES :) and IPL from them. Let's say, I want to apply a limited set of fixes to a few executable modules and update a specific product without IPL. In the normal loadlib world, I would COPYMOD the modules, carefully refresh LLA if needed and restart the appropriate tasks. What would be the appropriate tool to accomplish this in the ZFS (or HFS) world? Some pax incantation? Dave Gibney Information Technology Services Washington State University -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Promote specific modules from service root
In a real UNIX, I'd use rsync with the -av switches. Given that such
do not exist on z/OS UNIX, I'd put the names of the files to be copied
into another file, without the leading /Service or /Zervice. I'd then
do something like:
su - #switch to root
for i in file.containing.list.of.files;do cmp -s $i /Service/$i || {
mv -v $i $i.bak;cp -v -a /Service/$i $i };done #copy changed files
exit #from the root shell
What this does is for each file in the list, compare the old ($i) and
new (/Service/$i) version. If they are different, then rename the
current version, $i, to a backup name $i.bak, then verbosely (-v) copy
(cp) the new to the old, keeping the attributes of the new (dates,
owners, etc) (-a).
You may then want restart those processes which it would not be too
disruptive to restart.
On Fri, Jan 4, 2013 at 1:26 PM, Gibney, Dave gib...@wsu.edu wrote:
Normally, I apply maintenance to a copy mounted at /Service (or sometimes
/Zervice :) and deploy by making a copy of the new root ZFS file (and the
SYSRES :) and IPL from them.
Let's say, I want to apply a limited set of fixes to a few executable modules
and update a specific product without IPL.
In the normal loadlib world, I would COPYMOD the modules, carefully refresh
LLA if needed and restart the appropriate tasks.
What would be the appropriate tool to accomplish this in the ZFS (or HFS)
world? Some pax incantation?
Dave Gibney
Information Technology Services
Washington State University
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Maranatha!
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Promote specific modules from service root
Thanks John,
Instead of a list in a file, how would I say do this for each file in a
directory? I get the potentially changed directories from the SMP/E report. I
don't want to risk missing a file by trying to extract the specific changed
files from the SMP/E report.
Dave Gibney
Information Technology Services
Washington State University
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of John McKown
Sent: Friday, January 04, 2013 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Promote specific modules from service root
In a real UNIX, I'd use rsync with the -av switches. Given that such
do not exist on z/OS UNIX, I'd put the names of the files to be copied
into another file, without the leading /Service or /Zervice. I'd then
do something like:
su - #switch to root
for i in file.containing.list.of.files;do cmp -s $i /Service/$i || {
mv -v $i $i.bak;cp -v -a /Service/$i $i };done #copy changed files
exit #from the root shell
What this does is for each file in the list, compare the old ($i) and
new (/Service/$i) version. If they are different, then rename the
current version, $i, to a backup name $i.bak, then verbosely (-v) copy
(cp) the new to the old, keeping the attributes of the new (dates,
owners, etc) (-a).
You may then want restart those processes which it would not be too
disruptive to restart.
On Fri, Jan 4, 2013 at 1:26 PM, Gibney, Dave gib...@wsu.edu wrote:
Normally, I apply maintenance to a copy mounted at /Service (or sometimes
/Zervice :) and deploy by making a copy of the new root ZFS file (and the
SYSRES :) and IPL from them.
Let's say, I want to apply a limited set of fixes to a few executable
modules
and update a specific product without IPL.
In the normal loadlib world, I would COPYMOD the modules, carefully
refresh LLA if needed and restart the appropriate tasks.
What would be the appropriate tool to accomplish this in the ZFS (or HFS)
world? Some pax incantation?
Dave Gibney
Information Technology Services
Washington State University
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Maranatha!
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Promote specific modules from service root
I just looked and I think Ms. Shaffer gave you a better solution using
pax. It addresses the problems I mention at the end of my post.
But on the off chance you're interesting, just as a curiosity, you
could do something like:
su - #switch to root
cd /Service/sub/directory #change to subdirectory
oldDir=${PWD#/Service} #strip leading /Service from name of current
subdirectory
for i in *;do
$j=${oldDir}/$i #name of file to possible replace
cmp $i $j || {mv -v $j $j.bak; cp -av $i $j; }
done
exit #out of root shell
Now, this only does files in the specific directory, not in
subdirectories in that directory. If you want files in subdirectories
of the directory, you need to change it slightly
su - #switch to root
cd /Service/sub/directory #change to subdirectory containing updated files
oldDir=${PWD#/Service} #strip leading /Service from name of current
subdirectory
find . -type f |\
while read i;do
j=${oldDir}/$i #file to possible replace
cmp $i $j || { mv -v $j $j.bak; cp -av $i $j; } #compare and possibly copy
end
The find command will find all regular files in the directory and its
subdirectories, and list them out to stdout, which is piped into the
while read i;do loop.
And just in case you're wondering, if there is a brand spanking new
file created by some PTF, the cmp will fail because there is no old
file to compare to. This also causes so the second part to run. Now,
in this case the mv will fail, but the cp will still run and so new
files are copied.
Hum, some possible problems could be if a PTF created a new
subdirectory and files, or created a new file which is not a regular
file. This would be something like a named FIFO or a special device
file (mknod command.)
On Fri, Jan 4, 2013 at 2:13 PM, Gibney, Dave gib...@wsu.edu wrote:
Thanks John,
Instead of a list in a file, how would I say do this for each file in a
directory? I get the potentially changed directories from the SMP/E report.
I don't want to risk missing a file by trying to extract the specific changed
files from the SMP/E report.
Dave Gibney
Information Technology Services
Washington State University
--
Maranatha!
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
