customquery(ADM)

Syntax

customquery ListComponents [-e] [-p phase] [-D dir] [vend:comp[::vers]] ...

customquery ListPackages [-e] [-p phase] [-D dir] [vend:comp[:pkg] [::vers]] ...]

customquery ListPatches [-e] [-a accessType] [-D dir] [componentID...]

customquery ListFiles [-e] [-t type] [-a accessType] [-D dir] [-r] [vend:comp[:pkg][::vers]] ...

customquery ListExportTargets [-e] [-D dir] [vend:comp[:pkg] [::vers]] ...

customquery ListPhases [-e] [-D dir] [vend:comp[:pkg] [::vers]] ...

customquery IsFileIncluded [-e] [-a accessType] [-D dir] [-r] vend:comp[:pkg][::vers] filename

customquery GetExpectedSum [-e] [-D dir][-r] vend:comp[:pkg][::vers] filename

customquery ListDescriptions [-e] [-D dir] [vend:comp[:pkg][::vers]] ...

customquery swconfig

swconfig [-P]

Description

ListComponents

list components and versions, one version per line, in the form:

vendor:component::version.

If no vendor:component::version is specified, customquery lists all components.

ListPackages

return a list of packages which are either partially or fully at phase, one package per line, in the form:

vendor:component:package::version.

If no vendor:component:package::version is specified, customquery lists all packages of the given phase. If no phase is specified, the default phase is LOAD.

ListFiles

list all the files for the given package(s), one file per line.

ListPatches

lists the patches applied to a system.

ListExportTargets

list all the export targets for the given packages, one target per line. Export pathnames are listed relative to the root of the system.

ListDescriptions

list all the verbose descriptions for the given components or packages, one package per line. The -e option causes the vend:comp[:pkg][::vers] arguments to be treated as regular expressions instead of literals. The -D option is used for debugging; it specifies a non-root directory under which lie directories named /opt, var/opt, and so on.

ListPhases

list the phases (except EXPORT) for each specified package, in the form:

vendor:component:package::version PHASE1 PHASE2...

Each phase may be prepended with the keywords PART or CORRUPT.

IsFileIncluded

is true if the filename specified is included in the given component or package. This is exactly the same as checking whether the command customquery ListFiles [-a accessType] [-e] vend:comp[:pkg][::vers] displays filename in its output. If -r is not specified, filename is assumed to be relative to the root of the software storage object of the specified component (see hierarchy(M)). If -r is specified, filename is relative to the absolute root.

GetExpectedSum

return the checksum stored in the custom database for the given file. custom generates sums using the command sum -r. filename must be relative to the root of the software storage object of the specified component (see hierarchy(M)). For example, specify ./etc/mount instead of /opt/K/SCO/Unix/5.0.0/etc/mount.

swconfig

list the software sets (with release numbers) that have been modified since the system's initialization. Updates and patches are noted as such. The -P option only displays applied patches.

customquery accepts the following action options:

-a accessType

is either CLIENT or SHARED. The default is CLIENT.

-D dir

is used for debugging; it specifies a directory under which the software storage object hierarchies /opt and /var/opt can be found (see hierarchy(M)). It defaults to root (/).

-e

causes the vendor:component[:package][::version] arguments to be treated as regular expressions instead of literals.

-p phase

is one of the following: LOAD, ATTACH, REGISTER, or CONFIGURE. If phase is not specified, the default is LOAD.

-t type

is one of the following: ALL, DIR, FILE, FIFO, or SYML. If type is not specified, the default is ALL.

-r

is used for checking whether files are included. If the -r option is not specified, filename is assumed to be relative to the root of the SSO; if -r is specified, it is relative to the absolute root.

Exit values

0

success

1

error

The following exceptions pertain to the IsFileIncluded subcommand:

0

yes

1

no

Examples

   SCO:TclX::7.3.2a
   SCO:Unix::5.0.0
   SCO:WServer::1.0.0l

   SCO:WServer
   SCO:WServer::1.0.0l
   SCO:WServer:SharedControl::1.0.0l
   SCO:WServer:ClientControl::1.0.0l
   SCO:WServer:WSERVER::1.0.0l
   SCO:WServer:EXAMPLES::1.0.0l

   ./bin/ksh
   ./bin/posix/sh
   ./bin/rksh
   ./usr/lib/mkuser/ksh/profile
   ./usr/lib/mkuser/ksh/kshrc
   ./usr/lib/mkuser/ksh/mkuser.defs
   ./usr/lib/mkuser/rksh/profile
   ./usr/lib/mkuser/rksh/rkshrc
   ./usr/lib/mkuser/rksh/mkuser.defs
   ./usr/lib/mkuser/rksh/mkuser.init

   SCO:Unix:KSH::5.0.0 LOAD ATTACH REGISTER CONFIGURE

   SCO:Unix:KSH::5.0.0 LOAD CORRUPT-ATTACH

   SCO:Unix:KSH::5.0.0 PART-LOAD CORRUPT-PART-ATTACH

   ./bin/ksh	831108312

Sample output might be:

   Network Installation Boot Module 1.0.1       installed
   SCO TCP/IP                       2.0.0Cl     installed
        TCP/IP Version 2.0.0 Release 5.0.0c     applied
        TCP/IP Version 2.0.0 Release rs.tcp200  applied
   SCO NFS                          2.0.0Cl     installed
        NFS Version 2.0.0 Release Su 5.0.0c     applied
        NFS Version 2.0.0 Release Su rs.nfs200  applied

Files

See also

Standards conformance