Sponsored Content
Operating Systems AIX List of Installed patches for AIX from given set of patches Post 302687877 by bakunin on Friday 17th of August 2012 07:16:54 AM
Old 08-17-2012
Create a list of all installed filesets using the lslpp command. Since you intend to analyse it by a script i suggest you use the "-c" switch, which gives a colon-separated one-line-per-fileset output ideally suited to using it in scripts.

Then use a grep -f <your.list.file> <fileset.list> of some sorts to find the filesets on your lists which are installed - misses will be not installed at all.

Depending on the exact format of your list you will have to tweak this general sketch into a script, but the idea should be obvious.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to see all installed PATCHES

Hi all I am using HPUX11.00 i want to know how to see all installed PATCHES ..and also to see any perticular patch has been installed or not solaris showrev -p does not work in HPUX please suggest any command thanks praful (1 Reply)
Discussion started by: Prafulla
1 Replies

2. Solaris

How to find out installed patches on Sun5.9

Hi Unix Experts, I'm told to install WebSphere MQ on Sun 5.9 box. Before I install it, my task is to find out what OS patches have already installed on the box. I tried pkginfo -i command but it gives all of the packages installed. I want to find out a specific patch has been installed or... (1 Reply)
Discussion started by: hkhan12
1 Replies

3. Solaris

OS patches

Hi all, I am working on SUN-fire server solaris-10 How to find out what & how much " OS patches " installed on it?? plz help me out .:( (3 Replies)
Discussion started by: saurabh84g
3 Replies

4. AIX

command to list all installed patches

hi all i need an command to list all installed patches in aix 5.3 (5 Replies)
Discussion started by: maxim42
5 Replies

5. AIX

OS Patches installed but they seem as not installed

Hello everyone: I've installed an OS patch into AIX 6.1 by running the following command: instfix -d /tmp/6100-02-03 -k "IZ41855" however it seem not installed instfix -i -k "IZ41855" There was no data for IZ41855 in the fix database. what am I doing wrong? (8 Replies)
Discussion started by: edgarvm
8 Replies

6. AIX

file set not getting installed in aix

Hi One of the file set is not getting installed in aix. ========================================================================================= cbspsap01:/ # lppchk -v lppchk: The following filesets need to be installed or corrected to bring the system to a consistent state:... (1 Reply)
Discussion started by: newtoaixos
1 Replies

7. AIX

applying patches in aix 5.3

Hi Admins, Basically i am HPUX guy.HP will release patch bundles every three months and the same we are applying on servers as proactive steps. Please let me know how it happens with AIX. My servers are AIX 5.3 with TL 10 and some are TL 7. These servers are installed 2 years back and... (1 Reply)
Discussion started by: newaix
1 Replies

8. HP-UX

Patches hp-ux

Hi, I donīt have support HP, so I donīt get download patches on itrc. Somebody know a free site to download HP-UX patches? (3 Replies)
Discussion started by: quimera
3 Replies

9. Solaris

need help with message: no patches installed

Hi Folks, I am getting the following error when trying to see installed patches on my Solaris 9 system :wall: # patchadd -p No patches installed # Any help will be much appreciated Thanks in advance (1 Reply)
Discussion started by: momin
1 Replies

10. Solaris

List of patches and date installed

Does anyone know of a command that would show the list of patches installed and the date it was installed? My understanding is that "showrev -p" would show patches but not the date they were installed. I'm looking for this on a Solaris 10 server. Thanks. (2 Replies)
Discussion started by: ixauditor
2 Replies
ICON(1) 						      General Commands Manual							   ICON(1)

NAME
icon - interpret or compile Icon programs SYNOPSIS
icont [ option ... ] file ... [ -x arg ... ] iconc [ option ... ] file ... [ -x arg ... ] DESCRIPTION
icont and iconc each convert an Icon source program into executable form. icont translates quickly and provides interpretive execution. iconc takes longer to compile but produces programs that execute faster. icont and iconc for the most part can be used interchangeably. This manual page describes both icont and iconc. Where there there are differences in usage between icont and iconc, these are noted. File Names: Files whose names end in .icn are assumed to be Icon source files. The .icn suffix may be omitted; if it is not present, it is supplied. The character - can be used to indicate an Icon source file given in standard input. Several source files can be given on the same command line; if so, they are combined to produce a single program. The name of the executable file is the base name of the first input file, formed by deleting the suffix, if present. stdin is used for source programs given in standard input. Processing: As noted in the synopsis above, icont and iconc accept options followed by file names, optionally followed by -x and arguments. If -x is given, the program is executed automatically and any following arguments are passed to it. icont: The processing performed by icont consists of two phases: translation and linking. During translation, each Icon source file is translated into an intermediate language called ucode. Two ucode files are produced for each source file, with base names from the source file and suffixes .u1 and .u2. During linking, the one or more pairs of ucode files are combined to produce a single icode file. The ucode files are deleted after the icode file is created. Processing by icont can be terminated after translation by the -c option. In this case, the ucode files are not deleted. The names of .u1 files from previous translations can be given on the icont command line. These files and the corresponding .u2 files are included in the linking phase after the translation of any source files. The suffix .u can be used in place of .u1; in this case the 1 is supplied auto- matically. Ucode files that are explicitly named are not deleted. iconc: The processing performed by iconc consists of two phases: code generation and compilation and linking. The code generation phase produces C code, consisting of a .c and a .h file, with the base name of the first source file. These files are then compiled and linked to produce an executable binary file. The C files normally are deleted after compilation and linking. Processing by iconc can be terminated after code generation by the -c option. In this case, the C files are not deleted. OPTIONS
The following options are recognized by icont and iconc: -c Stop after producing intermediate files and do not delete them. -e file Redirect standard error output to file. -f s Enable full string invocation. -o name Name the output file name. -s Suppress informative messages. Normally, both informative messages and error messages are sent to standard error output. -t Arrange for &trace to have an initial value of -1 when the program is executed and for iconc enable debugging features. -u Issue warning messages for undeclared identifiers in the program. -v i Set verbosity level of informative messages to i -E Direct the results of preprocessing to standard output and inhibit further processing. The following additional options are recognized by iconc: -f string Enable features as indicated by the letters in string: a all, equivalent to delns d enable debugging features: display(), name(), variable(), error trace back, and the effect of -f n (see below) e enable error conversion l enable large-integer arithmetic n produce code that keeps track of line numbers and file names in the source code s enable full string invocation -n string Disable specific optimizations. These are indicated by the letters in string: a all, equivalent to cest c control flow optimizations other than switch statement optimizations e expand operations in-line when reasonable (keywords are always put in-line) s optimize switch statements associated with operation invocations t type inference -p arg Pass arg on to the C compiler used by iconc -r path Use the run-time system at path, which must end with a slash. -C prg Have iconc use the C compiler given by prg ENVIRONMENT VARIABLES
When an Icon program is executed, several environment variables are examined to determine certain execution parameters. Values in paren- theses are the default values. BLKSIZE (500000) The initial size of the allocated block region, in bytes. COEXPSIZE (2000) The size, in words, of each co-expression block. DBLIST The location of data bases for iconc to search before the standard one. The value of DBLIST should be a blank-separated string of the form p1 p2 ... pn where the pi name directories. ICONCORE If set, a core dump is produced for error termination. ICONX The location of iconx, the executor for icode files, is built into an icode file when it is produced. This location can be overridden by setting the environment variable ICONX. If ICONX is set, its value is used in place of the location built into the icode file. IPATH The location of ucode files specified in link declarations for icont. IPATH is a blank-separated list of directories. The current directory is always searched first, regardless of the value of IPATH. LPATH The location of source files specified in preprocessor $include directives and in link declarations for iconc. LPATH is otherwise sim- ilar to IPATH. MSTKSIZE (10000) The size, in words, of the main interpreter stack for icont. NOERRBUF By default, &errout is buffered. If this variable is set, &errout is not buffered. QLSIZE (5000) The size, in bytes, of the region used for pointers to strings during garbage collection. STRSIZE (500000) The initial size of the string space, in bytes. TRACE The initial value of &trace. If this variable has a value, it overrides the translation-time -t option. FILES
icont Icon translator iconc Icon compiler iconx Icon executor SEE ALSO
The Icon Programming Language, Ralph E. Griswold and Madge T. Griswold, Prentice-Hall Inc., Englewood Cliffs, New Jersey, Second Edition, 1990. Version 9.1 of Icon, Ralph E. Griswold, Clinton L. Jeffery, and Gregg M. Townsend, IPD267, Department of Computer Science, The University of Arizona, 1995. Version 9 of the Icon Compiler, Ralph E. Griswold, IPD237, Department of Computer Science, The University of Arizona, 1995. icon_vt(1) LIMITATIONS AND BUGS
The icode files for the interpreter do not stand alone; the Icon run-time system (iconx) must be present. Stack overflow is checked using a heuristic that is not always effective. 1 November 1995 IPD244b ICON(1)
All times are GMT -4. The time now is 08:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy