SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO shape_releas(1), vdiff(1), patch(1)FILES
<name1>+2+<name2>.pat
9.9.119 SHAPE_PATCH(1)
Check Out this Related Man Page
SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO shape_releas(1), vdiff(1), patch(1)FILES
<name1>+2+<name2>.pat
1.6.119 SHAPE_PATCH(1)
Hi
quick and question for the unix expert here
i downloaded the lastest patch from sun.
i'm ready to patch my production server. should i just patch it as is or go in to init 1 or init S to do the patching.
someone told me that you can just patch the server in init 3 and some other... (2 Replies)
Hello, greeting, really need help here...
I have a cluster system which having above patch level. Previous SA did nothing but left an undone job. Sigh..
If i install the patch 118558-39 onto the system, would it have any implication. Anytime to look after. I have reading a lot of meterial... (2 Replies)
Hi All,
If I need to verify my solaris 8 with patch 110910-03 and I query the server below:
#showrev -p | grep 'Patch: 110910-'
Patch: 110910-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu
Do I still need to apply the patch if the older 110910-01 patch exist?
Please... (5 Replies)
As i understand, Patch is a fix to bug in a product.
What is patch level wrt to solaris OS ? How do i know the patch level of a machine ? I have task to compare patch levels of 2 machines running solaris (3 Replies)
Hey!!!
Has anyone done HMC patch installation remotely? I would love to know if that would be possible. I have been doing through CD/DVD but hate to do the additional work of finding someone in the DC and sending him the CD's.
I have seen the option to supply remote site. can that be helpful?... (5 Replies)
Hi,
Is there any command to know the patch version?Suppose i installed RTlinux patch in rethat linux.How can i know the patch version installed?Any helps appreciated.
Thanks,
Sathi. (2 Replies)
hi every body
lock at this situation and tell me your advice
i tried to install patch in hp-ux v2 i used swinstall -s /path to the patch
every thing was good but during the installation network connection between the server and my labtob
when i connect again to the server i tried to... (2 Replies)
Hello
I have been asked to provide a security patch analysis of servers in my environment. For HPUX and Solaris there are tools wich can be loaded onto the servers to do this. However I do not know of one for Redhat . At this point I must mentioned that the Redhat servers are behind a firewall... (2 Replies)
Hi,
Just some questions on the script below...?
Given: bash-2.03$ command -a option1 name1 name2
ParseOptions()
{
local Len=${#@}
local Ctr=2 #always start at 2
local Name=()
local Iter=0
while ; do
if <- Is this correct? so I can get the $2... (2 Replies)
HI all,
As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010.
Using HP UX 11.11, 11.21 and 11.31
I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
I'm trying to patch an HPUX 11i v3 machine. The file I'm installing is "HP_UX_11i_v3_SecureShell_A.06.20.030._HP-UX_B.11.31_IA_PA.depot".
I get the following output in the log:
* Reading source for product information.
*Reading source for file information.
The corequisite
... (3 Replies)
Hi all,
I am exploring how I can automate the download and patching of my AIX servers via a central management mechanism.
I will need to patch all my servers annually to a certain pre-determined Service Pack (SP) level.
So far I performed some online search and found 2 products that might... (6 Replies)
I want to know the previous patch release date and the next patch release date of HPUX 11.31. Also I want to know what patch level is installed in the server at present.
I have searched in HPE sites but unable to find the information. It will be helpful if someone can help me with that info. (1 Reply)