tme 10 software distribution reference...

TME 10 Software DistributionReference Manual

Version 3.6

September 1998

are.rayteral, or

.

2,

ft

gh

thatse

therad ofctionibility

thisn sende,

TME 10 Software Distribution Reference Manual (September 1998)Copyright NoticeCopyright © 1998 by Tivoli Systems, an IBM Company, including this documentation and all softwAll rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement oAddendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication mbe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any compulanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manuotherwise, without prior written permission of Tivoli Systems. The document is not intended forproduction and is furnished “as is” without warranty of any kind.All warranties on this document arehereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication ordisclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/RISC System/6000, Tivoli Management Environment, TME 10, TME 10 ADE, TME 10 AEF,TME 10 Distributed Monitoring, TME 10 EIF, TME 10 Enterprise Console, TME 10 Framework,TME 10 Inventory, TME 10 Software Distribution, TME 10 User Administration.

Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of MicrosoCorporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively throuX/Open Company Limited.

Other company, product, and service names mentioned in this document may be trademarks orservicemarks of others.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not implythey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theproducts, programs, or services is not intended to imply that only Tivoli Systems or IBM products,programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or olegally protectable right, any functionally equivalent product, program, or service can be used instethe referenced product, program, or service. The evaluation and verification of operation in conjunwith other products, except those expressly designated by Tivoli Systems or IBM, are the responsof the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter indocument. The furnishing of this document does not give you any license to these patents. You calicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus AvenuThornwood, New York 10594.

i

TME 10 Software DistributionReference Manual

Preface.................................................................................................................. vi

Chapter 1—File Package DefinitionsFile Package Definition Format ..........................................................................1-2

Keyword Options Section ..........................................................................1-3

Files and Directories Section......................................................................1-3

Nested File Packages Section.....................................................................1-7

Exclude Files Section .................................................................................1-7

Keywords ............................................................................................................1-8

Chapter 2—CommandsUsing TME 10 Commands .................................................................................2-1

Command Line Syntax .......................................................................................2-2

Object References ...............................................................................................2-2

Registered Names.......................................................................................2-3

Object Paths................................................................................................2-3

TME 10 Software Distribution Commands ........................................................2-4

NetWare Managed Site Commands....................................................................2-7

Command Syntax................................................................................................2-8

waddicon .............................................................................................................2-9

waddpath ...........................................................................................................2-12

wclrblk ..............................................................................................................2-13

wclrline .............................................................................................................2-15

wcpfpblock........................................................................................................2-17

wcpyfile.............................................................................................................2-19

wcrtfpblock .......................................................................................................2-20

wdistfp...............................................................................................................2-22

wdistfpblock......................................................................................................2-26

wdskspc.............................................................................................................2-29

TME 10 Software Distribution Reference Manual i

weditini ............................................................................................................. 2-31

wexprtfp ............................................................................................................ 2-33

wgetfpattr .......................................................................................................... 2-35

wgetkey............................................................................................................. 2-40

wgetval.............................................................................................................. 2-42

wimprtfp............................................................................................................ 2-44

winsblk.............................................................................................................. 2-46

winsline............................................................................................................. 2-48

winstruct_file .................................................................................................... 2-50

wmrgini............................................................................................................. 2-52

wmvapobj.......................................................................................................... 2-53

wmvfpobj .......................................................................................................... 2-54

wrestart.............................................................................................................. 2-55

wrmfp................................................................................................................ 2-56

wrmfpblock....................................................................................................... 2-58

wrplblk .............................................................................................................. 2-61

wrplline ............................................................................................................. 2-63

wrunprog........................................................................................................... 2-65

wseterr............................................................................................................... 2-66

wsetfpattr .......................................................................................................... 2-67

wsetfpcontents .................................................................................................. 2-72

wsetfpopts ......................................................................................................... 2-74

wsetfpprgs......................................................................................................... 2-86

wsettrus ............................................................................................................. 2-97

wsetval .............................................................................................................. 2-99

wswdistrim...................................................................................................... 2-101

Chapter 3—PolicyDefault Policy Methods ...................................................................................... 3-2

Default Policy Methods for AutoPacks...................................................... 3-4

Default Policy Methods for File Package .................................................. 3-5

Validation Policy Methods ................................................................................. 3-8

ii Version 3.6

Validation Policy Methods for AutoPacks...............................................3-10

Validation Policy Methods for File Packages ..........................................3-13

Validation Policy Methods and TME 10 Commands ..............................3-21

Policy Objects ...................................................................................................3-22

Creating a New Policy Object ..................................................................3-24

Replacing the Contents of a Policy Method.............................................3-25

Assigning Policy to a Policy Region........................................................3-27

Example—Setting a Default Policy Method.....................................................3-28

Policy Methods .................................................................................................3-32

ap_def_autopack_file ........................................................................................3-33

ap_def_autopack_host.......................................................................................3-34

ap_val_autopack_host_file ...............................................................................3-35

ap_val_name .....................................................................................................3-37

ap_val_operation...............................................................................................3-39

fp_def_excludes ................................................................................................3-41

fp_def_flist ........................................................................................................3-42

fp_def_nestedlist ...............................................................................................3-43

fp_def_options ..................................................................................................3-44

fp_def_src_host.................................................................................................3-45

fp_val_delete_src_host .....................................................................................3-46

fp_val_excludes ................................................................................................3-48

fp_val_flist ........................................................................................................3-50

fp_val_name......................................................................................................3-52

fp_val_nestedlist ...............................................................................................3-54

fp_val_operation ...............................................................................................3-56

fp_val_options...................................................................................................3-58

fp_val_src_host .................................................................................................3-60

Chapter 4—Configuration ProgramsProcessing Command Line Arguments ..............................................................4-2

Processing Input Files .........................................................................................4-3

Return Codes of Configuration Programs...........................................................4-3

TME 10 Software Distribution Reference Manual iii

UNIX Configuration Programs.................................................................. 4-3

NetWare Configuration Programs.............................................................. 4-4

PC Configuration Programs ....................................................................... 4-5

PC Environment Space ....................................................................................... 4-5

UNIX Example Scripts ....................................................................................... 4-6

Rebooting After a File Package Distribution ............................................. 4-6

Removing Files from the Destination Directory........................................ 4-7

Running an Installation Script After a Distribution ................................... 4-8

Checking the Architecture Type ................................................................ 4-9

PC Example Programs...................................................................................... 4-11

Checking Disk Space ............................................................................... 4-11

Preparing a Windows NT Target Before a Distribution .......................... 4-13

Configuring Distributed PC Software...................................................... 4-15

Chapter 5—CustomizationsTME 10 Application Extension Facility............................................................. 6-1

Retrieving Dialog Descriptors.................................................................... 6-2

Changing Existing Dialog Gadgets............................................................ 6-3

Exposing File Package Keywords and Excluded Files .............................. 6-9

Creating a Switch Gadget and the Excluded Files List ................... 6-14

Creating a Choice and Text Gadget................................................. 6-18

Bitmaps and Icons .................................................................................... 6-26

TME 10 Application Development Environment............................................. 6-27

Customizing the File Package Resource .................................................. 6-28

The fp_push Method........................................................................ 6-29

The fp_to_fpblock Method.............................................................. 6-29

The fp_to_size Method.................................................................... 6-29

The set_fp_name Method ................................................................ 6-30

Customizing the AutoPack Resource....................................................... 6-30

The calc_size Method...................................................................... 6-31

The distributep Method ................................................................... 6-31

The init_by_upload Method ............................................................ 6-31

iv Version 3.6

3

The init_from_existing Method.......................................................6-31

The removep Method.......................................................................6-32

Chapter 6—TroubleshootingHow Software Distribution Works .....................................................................7-1

Software Distribution Methods...........................................................................7-3

Network Communications ..................................................................................7-6

Distributing to Managed Nodes ..........................................................................7-7

Distributing from Source Host/TMR Server to Managed Nodes...............7-8

Distributing from Source Host/TMR Server through a Repeater...............7-9

Distributing from a Source Host to Multiple Repeaters...........................7-10

Distributing to Endpoints..................................................................................7-11

Distributing from Source Host/TMR Serverto Endpoints via a Gateway......................................................................7-13

Distributing from Source through Multiple Gateways and Repeaters .....7-14

Distributing to PC Managed Nodes ..................................................................7-16

Troubleshooting Tips ........................................................................................7-18

Examining the File Package Definition....................................................7-20

Verifying Repeater Parameters and Configurations.................................7-21

Checking lost-n-found..............................................................................7-22

Checking the Default Directory on a Target System ...............................7-22

Verifying Setup for Endpoints .................................................................7-24

Verifying Setup for PC Managed Nodes..................................................7-25

Performing Miscellaneous Debugging Tricks..........................................7-26

Chapter 7—Object ConsistencyThe fp_name_change Operation .........................................................................8-2

The remove_fp Operation ...................................................................................8-2

The host_name_change Operation......................................................................8-

The remove_host Operation................................................................................8-3

The wchkdb Command .......................................................................................8-4

Moving Objects Between Collections ................................................................8-5

TME 10 Software Distribution Reference Manual v

vi Version 3.6

Preface

reT

s

forr

rs

the

e

re

d

PrefaceTivoli Management Environment 10 (TME 10) Software Distributionapplication provides a means of managing and distributing softwaacross a multi-platform network that can include UNIX machines, Nand NetWare servers, and PCs running Windows, Windows 95,Windows NT, or OS/2. For distributions that encompass wide areanetworks (WANs), TME 10 Software Distribution has a built-in,WAN-smart capability that reduces inter-network traffic and ensurean efficient distribution.

This manual explains advanced features and concepts necessaryyou to effectively use and tailor Software Distribution fully meet youdistribution needs.

Who Should Read This ManualThe target audience for this manual is senior system administratowho intend to improve or customize Software Distributionfunctionality. You should have knowledge of the UNIX operatingsystem; concepts such as directories, files, and symbolic links; andPC operating systems running on the machines to which you willdistribute software. In addition, you should be familiar with SoftwarDistribution and have use for its advanced features.

Prerequisite and Related DocumentsYou must understand the information in the following manuals befoattempting to use this guide:

■ TheTME 10 Software Distribution User’s GuideProvides concepts and procedures for daily file package andAutoPack operations.

■ TME 10 Framework User’s Guide, TME 10 Framework Planningand Installation Guide, andTME 10 Framework ReferenceManualProvide detailed information and procedures to manage theTME 10 environment from the TME 10 desktop or the commanline interface (CLI), including information about configuring,maintaining, and troubleshooting your TME 10 installation.

TME 10 Software Distribution Reference Manual vii

Preface

d

f the

y.

n

t.

ed.

What This Guide ContainsTheTME 10 Software Distribution Reference Manualcontains thefollowing sections:

■ Chapter 1, “File Package Definitions”

Details how to edit and use the file package definition format ankeywords.

■ Chapter 2, “Commands”

Provides the syntax statements, descriptions, and examples oTME 10 Software Distribution commands.

■ Chapter 3, “Policy”

Describes default and validation policy and how to define polic

■ Chapter 4, “Configuration Programs”

Describes and provides examples for the Software Distributiobefore, after, removal, after removal, commit, and on errorprograms.

■ Chapter 5, “Customizations”

Provides instructions and conceptual information forcustomizing Software Distribution dialogs and bitmaps.

■ Chapter 6, “Troubleshooting”

Details how Software Distribution works and providestroubleshooting tips for solving problems in your environmen

■ Chapter 7, “Object Consistency”

Describes how Software Distribution maintains databaseconsistency if managed nodes or profiles are deleted or renam

viii Version 3.6

Preface

d

in

Typeface ConventionsThe guide uses several typeface conventions for special terms anactions. These conventions have the following meaning:

Bold Commands, keywords, file names, or otherinformation that you must use literally appear inboldtypeface. Names of windows, dialogs, and othercontrols also appear inbold.

Italics Variables and values that you must provide appearitalics.

Bold Italics New terms appear inbold italic the first time they areused.

Monospace Code examples appear inmonospace font.

Platform-Specific InformationThe following table identifies text used to indicate platform-specificinformation or procedures.

Platform Supported Versions

AIX 4.x Managed Node, Endpoint:IBM RS/6000 series running AIX, Versions 4.1, 4.2,and 4.3

AS/400 Endpoint:V3R2, V3R7, V4R1, and V4R2

Digital UNIX Managed Node, Endpoint:Versions 4.0a and 4.0d.

DG/UX Endpoint:Versions 4.11 and 4.20 on the ix86 platform

HP-UX Managed Node, Endpoint:HP9000/700 and 800 series running HP-UX, Versions10.01, 10.10, 10.20 and 11.00

NCR Managed Node, Endpoint:NCR 3000 series running NCR UNIX SVR4 MP-RAS3.0.1 and 3.0.2

TME 10 Software Distribution Reference Manual ix

Preface

d

NetWare PC Agent, Endpoint:IBM-compatible PCs 486 or higher running NovellNetWare, Versions 3.11, 3.12, 4.01, 4.1, and 4.11

OS/2 TME 10 Desktop for Windows, PC Agent, Endpoint:IBM-compatible PCs 486 or higher running IBM OS/2,Versions 2.0, 2.1,Warp 3.0, and Warp 4.0 withWin-OS/2

Pyramid Endpoint:Pyramid MIServer-ES, Version 5.4MN

Sequent Managed Node, Endpoint:Sequent DYNIX/ptx, Releases 4.2.3 and 4.4.2

SCO Managed Node, Endpoint:SCO UnixWare 7, SCO UnixWare Versions 2.1.1 and2.1.2

SGI Managed Node, Endpoint:SGI IRIX, Versions 6.2 and 6.4

Solaris Managed Node, Endpoint:Sun SPARC series running Solaris, Versions 2.4, 2.5,2.5.1, and 2.6

Solaris Intel Managed Node, Endpoint:Solaris2-ix86, Versions 2.5.1 and 2.6

SunOS Managed Node, Endpoint:Sun SPARC series running SunOS, Versions 4.1.3 an4.1.4

Windows TME 10 Desktop for Windows, PC Agent, Endpoint:IBM-compatible PCs 486 or higher running MicrosoftWindows, Versions 3.1, 3.11, and Windows 95

Windows NT TME 10 Desktop for Windows, PC Agent, ManagedNode, Endpoint:IBM-compatible PCs 486 or higher running MicrosoftWindows NT, Versions 3.51 SP5, 4.0, and 4.0 SP3.

Platform Supported Versions

x Version 3.6

Preface

text

ub.

the)ch

ithfor

TME 10 Software Distribution IconsThe following icons represent TME 10 Software Distribution profileresources:

File package and AutoPack profile resources are created in the conof a profile manager and are distributed to subscribing systems orprofile managers managed by TME 10.

Contacting Customer SupportIf you encounter difficulties with any Tivoli products, you can enterhttp://www.support.tivoli.com to view the Tivoli Support homepage. After you link to and submit the customer registration form, yowill be able to access many customer support services on the We

Use the following phone numbers to contact customer support in United States: the Tivoli number is 1-800-848-6548 (1-800-TIVOLI8and the IBM number is 1-800-237-5511 (press or say 8 after you reathis number). Both of these numbers direct your call to the TivoliCustomer Support Call Center.

We are very interested in hearing from you about your experience wTivoli products and documentation. We welcome your suggestionsimprovements. If you have comments or suggestions about thisdocumentation, please send e-mail to [email protected].

TME 10 Software Distribution Reference Manual xi

Preface

xii Version 3.6

File P

ackage Definitions

ngtes

n

d in

1File Package Definitions

TME 10 Software Distribution enables you to set file packageproperties using the desktop, command line, or by exporting/importifiles. When you export a file package, Software Distribution generathe file package definition, which you can edit to change thecharacteristics of the file package. This file package definition is aASCII file that contains the following characteristics of the filepackage:

■ Processing options

■ Logging options

■ Platform-specific options

■ Files and directories in the file package

■ Nested file packages in the file package

■ Files to exclude from the file package

The source host, targets, and file package attributes are not includethe file package definition.

1

TME 10 Software Distribution Reference Manual 1–1

File Package Definition Format

y a

ationn

reeto

ne

File Package Definition FormatThe file package definition is comprised of a header and foursections—keyword options, files and directories to be distributed,nested file packages, and excluded files. Each section is delimited b% (percent), as illustrated here:

If the file package definition does not contain a header, or if the formof the header is unlike the header illustrated above (with the exceptof version numbers), a fatal error will result and Software Distributiowill stop the distribution or removal operation. However, you cancreate a partial file package definition, containing the header, the thsection delimiters, and only those keywords to be set, and import it inthe file package. Blank lines and comments in the file packagedefinition are ignored. Items can span multiple lines by ending a liwith a backslash (\).

The following sections describe each section of the file packagedefinition.

header

keyword options

files and directories

nested file packages

exclude files

(flist)

1–2 Version 3.6

File Package Definition Format File P

ackage Definitions

,

y

et,

e

ay

ged,

on

r

Keyword Options SectionThe keyword options section contains a complete list of keywordswhich control the behavior of a file package distribution, and theirdefault values. The format for this section is the keyword, followed ban equal sign (=) and the value for that keyword, as follows:

keyword=value

Do not include spaces around the equal sign. If a keyword is not snothing follows the equal sign nd Software Distribution uses thedefault value specified for this parameter.

If you want to specify multiple values for a keyword, you must enclosthe assigned values in single quotation marks (' ' ), as follows:

mail_id='[email protected] [email protected]'

If you do not surround the pairs with single quotation marks, you mreceive a misleading diagnostic message while importing thedefinition similar to the following message:

Invalid file package definition: Error: Line 35: Expected'=' assignment.

Becausekeyword=valuepairs are separated by spaces, the file packaparsing code expects a new keyword assignment after a space antherefore, expects an equal sign (=) before the new line.

The valid keywords and their values are discussed in “Keywords” page 1-8.

Files and Directories SectionThe second section of the file package definition, called theflist,contains the names of the files and directories to be distributed (oremoved) by the file package. Specifically, the flist can contain thefollowing:



e

s

o

e

d.

r

■ The path of a file. Directories and file names may containwildcard characters. The supported wildcard characters aresimilar to that of the Bourne shell, such as

* Matches any string, including the null string.

? Matches any single character.

[...] Matches any one of the enclosed characters.

Also, a backslash (\) may be used as a directory delimiter in thpath of a file name.

■ The path of a directory. TME 10 Software Distribution distributethe directory and its contents if theDescend into directoriescheck box is selected in theGeneral Options section. If youwish to distribute all contents of the /tmp/hpux directory but donot wanthpux added to the destination path, specify/tmp/hpux/as the source directory (with the trailing slash). Finally, if you dnot select theDescend into directoriesoption, only the directoryis distributed.

Note: TME 10 Software Distribution supports the UNIX/. pathname convention, which specifies that all contents of thdirectory are to be included, only if you select theDescend into directories check box during thedistribution.

■ A shell command surrounded by grave accent marks (`). Whenthe file package is distributed, the shell command is interpreteThus, the shell command must produce a valid list of files ordirectories, one per line. Commonly used commands includefind , cat, andls -l.

Each entry is listed one per line, as follows:

/src/gnu/etc/host/etc/group'cat /tmp/filenames'

You can also specify one or more options for each line in the flist.Options affect the file name, directory name, or shell command fowhich they are specified and alter the way the file or directory isprocessed. The flist options are as follows:

1–4 Version 3.6


ackage Definitions

ue

ehe

y

ge

d Specifies the destination path and overrides the valfor both thedefault_dest andxxx_platform_prefixkeywords. The last path component from the sourcpath is concatenated to the destination path to form tpath. If the source is a directory, all paths in thehierarchy are also modified.

g Specifies the file GID as a name or number.

G Specifies the directory GID as a name or number.

m Specifies the filechmod options, in octal values only.

M Specifies the directorychmodoptions, in octal valuesonly.

o Specifies whether to descend into directories andoverride thedescend_dirs keyword. Valid values aredescend andnodescend.

s Overrides thesrc_relpath keyword and specifies apath on the source host from which to obtain the fileand directory.

t Sets the modification time given in the format of thedate command.

u Specifies the file UID as a name or number.

U Specifies the directory UID as a name or number.

Specify an option in the following format after the file name, directorpath, or shell command:

option =value

Do not type spaces around the equal sign (=). List all options on thesame line.

For example, suppose you specify the following flist in the file packadefinition:

/etc/hosts d=/usr/safe/etc/passwd d=/tmpREADME.txt s=/usr/local d=/etc



n

t:

rd

an

t

les

at. ise

If you have specified the following keywords in the keywords sectioof the file package definition:

default_dest=/keep_paths=nsrc_relpath=/

TheREADME.txt file is obtained from the/usr/local directory andthe specified files are distributed as follows:

/usr/safe/hosts/tmp/passwd/etc/README.txt

In addition, the following examples are valid entries:

/etc/passwd d=/backups/etc u=root/bin/miscdir U=201 G=30 o=descend/bin/file_ex t=0125120095 m=0600

Finally, consider the following information when specifying the flis

■ All file and directory entries should be full paths (not relativepaths), unless you have specified thesrc_relpath keyword. See“Keywords” on page 1-8 for more information on definingkeywords. In addition, you must specify the path using forwaslashes (/), even if the file or directory resides on a PC.

■ Double-quote any entry that contains an embedded space orequal sign (=).

■ You cannot specify an option in conjunction with an entry thacontains a wildcard character.

■ Because some PCs limit file names to eight characters and finame extensions to three characters, you must specify all filethat will be distributed or processed on a PC target in this formIf you specify a file to be distributed or removed whose nametoo long, Software Distribution will truncate the file name on thPC target.

■ Environment variables are not allowed.

■ You cannot include a file or directory namedTRAILER!!! in thefile package. This is the POSIX-compliantcpio end-of-archivefile marker.

1–6 Version 3.6


ackage Definitions

age.ved)

rentage

ts

aceas

ile

hee

he

Nested File Packages SectionThe third section of the file package definition contains a list of filepackage names, one per line, that are nested in the current file packThe contents of these nested file packages are distributed (or remowhen the parent file package is distributed (or removed).

When file packages are nested, all operations performed on the pafile package are performed on the nested files. The nested file packinherits most of the properties from the parent file package; thecharacteristics of the parent file package apply to itself and all of inested file packages.

Note: You can only add 50 levels of nested directories to a filepackage.

If a file package name contains special characters, such as white sp(for example,FP 1), you must enclose the name in double quotes, follows:

%"FP 1"Payroll"WP Man Pages""Database!"

Exclude Files SectionThis section provides an easy way for you to exclude files from the fpackage operation. When you perform an operation, SoftwareDistribution compares each file in the file package to the entries in texclude files section. If there is a match, that file is excluded from thfile package operation.

For example, you might want to distribute everything in the/usr/todddirectory exceptcore files or files ending in.o. The exclude filessection of the file package would be as follows:

%core*.o

When you perform a file package operation, if any of the entries in tflist creates acore file or a file that ends with.o, those files areexcluded during the operation.


Keywords

rd

(

opose

the

p.are

s:

As illustrated in the previous example, you can specify shell wildcacharacters such as* , ?, \, [, and]. In addition, the exclude files list canalso contain a shell command surrounded by grave accent marks`).

KeywordsYou can set all of the keywords listed in the file package definitionusing the export/import capability and most of them using the desktand command line. The following illustrations map the keywords tvarious general and platform-specific dialogs—when you select theboxes or enter a value in any of these fields, the keyword is set forfile package. In addition, these illustrations provide the SoftwareDistribution defaults to the keywords available through the desktoExcept for those noted, all keywords available through the desktoplisted in the following illustrations.

The following dialog sets file package properties for all file package

stop_on_error

descend_dirs

keep_paths

do_compress

default_file_mode

post_noticemail_id

log_host

log_file

1–8 Version 3.6

Keywords File P

ackage Definitions

The following dialog sets platform-specific file package options forUNIX file packages:

unix_program_

unix_program_

input_from_src

prog_from_src

unix_program_prog_path

unix_program_input_path

unix_before_skip_non_zero

unix_platform_prefix

unix_default_file_gid

unix_default_file_uid

follow_links


Keywords

The following dialog sets platform-specific file package options forNetWare file packages:

nw_program_

nw_login_

input_from_src

get_from_src

nw_program_prog_from_src

nw_program_

nw_login_

prog_path

prog_path

nw_program_input_path

nw_before_skip_non_zero

nw_platform_prefix

nw_bindery

nw_tree

nw_context

nw_force_disconnect

nw_force_disconnect

nw_broadcast_message

1–10 Version 3.6

Keywords File P

ackage Definitions

nir

The following dialog sets platform-specific file package options forWindows file packages:

Set thewin_before_skip_non_zero keyword from the desktop byselecting theBefore Distribution button.

Also, all of the PC options dialogs are similar. Refer to this illustratioto correlate Windows 95, Windows NT, and OS/2 keywords to therespective dialog.

win_platform_prefix

win_optional_dist

win_program_prog_from_src

win_program_input_from_src

win_optional_dist_timeout

win_program_prog_path

win_program_input_path

win_program_option


Keywords

h

fitsan

The following dialog illustrates the keyword that is available througtheRemove File Packages desktop.

The following keywords are listed in the keyword options section othe file package definition. Each keyword is described in terms of function, the operation it is related to, and the valid values that you cspecify. If a keyword has a default value, it is also listed.

rm_empty_dirs

Keyword Description Related to Valid Values

append_log Specifies whether toappend a notice to thelog file when filepackage distribution,commit, or removaloperations areperformed.

Reporting ornotification

y = Append notice tolog filen = Replace the logfile (default)

1–12 Version 3.6

Keywords File P

ackage Definitions

backup_fmt Specifies a format usedto make a backup of filesthat exist at the target.Supposebackup_fmt =/back/%p/%f.%n , thefile package contains/usr/bin/fp and atdistribution time thesame file exists on thetarget, the/usr/bin/fpon the target moves to/back/usr/bin/fp.1. If/back/usr/bin/fp.1already exists, theoriginal file moves to/back/usr/bin/fp.2, andso on up to a maximumindex number of 100.

File packageprocessing

An absolute path,optionally containing%p , %f , or%n ,where:%p = the directorypath%f = the file name%n = an auto-incrementing numericindex value

There is no defaultvalue.

create_dirs Specifies whether tocreate (at thedestination) theintermediate directoriesfor the files in the filepackage if thosedirectories do notalready exist.


y = Create the inter-mediate directories onthe destination(default)n = Do not create newdirectories



Keywords

default_dest Specifies the defaultdestination directory forall entries in the filepackage.The destinationdirectory path isconstructed asxxx_platform_prefix/default_dest/filename,where filename is thelast component of thefile name or the full path(if keep_paths isspecified).


Any valid path name.


This keyword isuseful if you aredistributing a filepackage to differenttypes of machines andwant the file packageto reside in the sameplace on all machines.Use thexxx_platform_prefixkeywords to specifyplatform-specificparts of thedestination directory,such as a drive letter.

default_dir_mode Sets the defaultpermission (mode) forall directories distributedin the file package.

Security Any octal mode asdescribed by thechmod man page.Only r (4) andrw (6)are set on PCs.The default is topreserve the mode ofthe source.

default_file_mode Sets the defaultpermission (mode) forall files and linksdistributed in the filepackage.

Security Any octal mode asdescribed by thechmod man page.Only r (4) andrw (6)are set on PCs.The default is topreserve the mode ofthe source.


1–14 Version 3.6

Keywords File P

ackage Definitions

default_mtime Sets the defaultmodification time for allentries distributed in thefile package.


Any numberconforming to thedate (UNIX)command semantics,which isMMddhhmm[yy].MM is the month,ddis the day,hh is thehour,mm is theminutes, andyy is theyear. You mustspecify all numberswith two digits; forexample, February is02.The default is themodificaiton time ofthe original file on thesource host.

descend_dirs Specifies whether totraverse directoriesencountered in the filesand directories list,thereby distributing notonly the directoryentries, but alsoeverything contained inthe directories.


y = Distribute nameddirectories andcontentsn = Distribute onlynamed directories(default)

do_checksum Specifies whether toverify a transmission byusing a checksumcomputed on the sourceand targets.


y = Do checksumn = Do not dochecksum (default)

do_compress Specifies whether tocompress the filepackage beforedistributing it.


y = Do compressn = Do not compress(default)



Keywords

dos_after_input_from_src

Provided forbackward-compatibility.

Afterprograms onDOS targets

None

dos_after_input_path



None

dos_after_option Provided forbackward-compatibility.


None

dos_after_prog_from_src



None

dos_after_prog_path



None

dos_after_removal_input_from_src


After removalprograms onDOS targets

None

dos_after_removal_input_path



None

dos_after_removal_option



None

dos_after_removal_prog_from_src



None

dos_after_removal_prog_path



None


1–16 Version 3.6

Keywords File P

ackage Definitions

dos_before_input_from_src


Beforeprograms onDOS targets

None

dos_before_input_path



None

dos_before_prog_from_src



None

dos_before_prog_path



None

dos_before_skip_non_zero



None

dos_commit_input_from_src


Commitprograms onDOS targets

None

dos_commit_input_path



None

dos_commit_option Provided forbackward-compatibility.


None

dos_commit_prog_from_src



None

dos_commit_prog_path



None



Keywords

dos_on_error_input_from_src


On errorprograms onDOS targets

None

dos_on_error_input_path



None

dos_on_error_option



None

dos_on_error_prog_from_src



None

dos_on_error_prog_path



None

dos_platform_prefix Provided forbackward-compatibility.

Destinationpaths on DOStargets

None

dos_removal_input_from_src


Removalprograms onDOS targets

None

dos_removal_input_path



None

dos_removal_option Provided forbackward-compatibility.


None

dos_removal_prog_from_src



None


1–18 Version 3.6

Keywords File P

ackage Definitions

dos_removal_prog_path



None

file_cksums Indicates whether to usechecksums on theindividual files in the filepackage to detectdifferences between thesource file and the targetfile rather than justmodification time,ownership groupmembership, and filemode. This is onlyrelevant whenanychanges are indicatedfor a distribute orpreview operation.


y = Computechecksum onindividual files todetect differencesbetween the sourceand the targetn = Use onlymodification time,ownership, groupmembership, and filemode to detectdifferences betweenthe source and target(default)

follow_links Indicates whether tofollow symbolic links tothe original files towhich the links point,thereby causing the filesto be distributed, ratherthan the links.

CAUTION! If you aredistributing the filepackage to PC targets,do not set this keywordto n or the distribution tothe PCs will fail if thereare symbolic links in thefile package definition.


y = Copy originalfiles to destination(default)n = Create new linksto original files at thedestination



Keywords

install_progs Indicates whether toremove theconfiguration programswhich get unpacked onthe target machine(assuming they werespecified to come fromthe source host) afterthey are run.


y = Install theprograms thatoriginate on thesource into thedestination pathdefined byxxx_platform_prefix/default_destn = Install theprograms thatoriginate on thesource host usingtemporary names andremove them from thetarget after processing(default)

keep_paths Indicates whether toconcatenate the entiresource file path nameonto the destination filepath.For example, sendingsource file /etc/motd todefault destination/target/dist, ifkeep_paths= y, the filearrives at the targets as/target/dist/etc/motd;otherwise, it arrives as/target/dist/motd.


y = Append pathnamesn = Do not appendpath names (default)


1–20 Version 3.6

Keywords File P

ackage Definitions

list_path Specifies the directoryon the target in which towrite the log filecontaining a list of allfiles and directoriesdistributed to orremoved from the target.The log file is calledfpname.log, wherefpname is the name ofthe file package beingdistributed or removed.If this directory does notexist,create_dirs=ymust be specified tocreate the directory.


A fully specified pathto a directory.


Note: Do not enablethis keyword if thefile package name hasspaces or more thaneight characters.

log_file Specifies a completepath to place noticeinformation in when adistribute, commit, orremoval is performed.


Complete file path. Ifthe file does notalready exist, anattempt is made tocreate the file with theUID and GID of theadministratorperforming theoperation. The defaultis no path, indicatingno log file.

log_file_gidb Specifies the GID of thelog file specified by thelog_file keyword.


Any decimal valuevalid as a GID on thesource system.The default is theGID of theadministrator whofirst distributed thefile package.



Keywords

log_file_mode Specifies the file modeof the log file specifiedby thelog_file keyword.


Any valid octal value.The default is600,owner readable andwritable.

log_file_uidb Specifies the UID of thelog file specified by thelog_file keyword.


Any decimal valuevalid as a UID on thesource system.The default is theUID of theadministrator whofirst distributed thefile package.

log_host Specifies the name of amanaged node where thelog file is written.


Name of the managednode.The default is no hostname. If a log file isspecified but not a loghost, the default loghost is the TMRserver.

mail_id Specifies completee-mail addresses ofpeople to send mail towhen a distribution,commit, or removal isperformed.See theTME 10Framework Planningand Installation Guidefor more info aboutconfiguring e-mail inyour TMR.


Complete e-mailaddresses, such [email protected],valid on the TMRserver. By default,mail is not sent.

modifiers For internal use only. File packageprocessing

None


1–22 Version 3.6

Keywords File P

ackage Definitions

nested_first Indicates whether toprocess the nested filepackages before thecontents of the filepackage.


y = Process nestedfile packages beforethe contents of thisfile packagen = Process nestedfile packages after thecontents of this filepackage (default)

no_overwrite Indicates whether tooverwrite a file on thetarget.


y = Does notoverwriten = Overwrites(default)

nt_after_input_from_src

Indicates whether thefiles specified by thent_after_input_pathkeyword resides on thesource host.

Afterprograms onWindows NTtargets

y = Resides on thesource hostn = Resides on thetarget (default)

nt_after_input_path Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_after_prog_pathkeyword (only valid ifyou set thent_after_prog_pathkeyword).If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_after_prog_pathkeyword.The default is no pathname.



Keywords

nt_after_option Indicates whether toreboot the target afterthe program runs, restartWindows NT on thetarget after the programruns, or neither. If theafter program fails, thetarget is not rebooted orrestarted.


reboot = Reboot thetarget after theprogram runsrestart = RestartWindows NT after theprogram runsNULL = Do notreboot, or restartWindows NT(default)

nt_after_prog_from_src

Indicates whether theprograms specified bythent_after_prog_path keyword resides onthe source host.



nt_after_prog_path Specifies the full path ofprograms to be run on aWindows NT target aftera file package’s files aredistributed. If theprograms reside on thesource host, you canspecify a relative path tothem. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces).The default is no pathname.

nt_after_removal_input_from_src

Specifies whether thefiles specified by thent_after_removal_input_path keywordresides on the sourcehost.

After removalprograms onWindows NTtargets



1–24 Version 3.6

Keywords File P

ackage Definitions

nt_after_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_after_removal_prog_path keyword(only valid if you set thent_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_after_removal_prog_path keyword.The default is no pathname.

nt_after_removal_option

Indicates whether toreboot the target afterremoval completes. If anafter removal program isspecified and it fails, thetarget is not rebooted.


reboot = Reboot thetarget after removalrestart = RestartWindows NT after theprogram runsNULL = Do notreboot (default)

nt_after_removal_prog_from_src

Specifies whether theprograms specified bythent_after_removal_prog_path keywordresides on the sourcehost.





Keywords

nt_after_removal_prog_path

Specifies a full path of aprogram to be run on aWindows NT target afterremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.


Any valid, completefile name. The defaultis no path name (thatis, do not run aprogram afterremoving a filepackage).

nt_before_input_from_src

Indicates whether thefiles specified by thent_before_input_pathkeyword resides on thesource host.

Beforeprograms onWindows NTtargets


nt_before_input_path

Specifies a full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_before_prog_pathkeyword (only valid ifyou set thent_before_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_before_prog_path keyword. Thedefault is no pathname.


1–26 Version 3.6

Keywords File P

ackage Definitions

nt_before_prog_from_src

Yes or no toggle thatindicates whether theprograms specified bythent_before_prog_pathkeyword resides on thesource host.



nt_before_prog_path

Specifies the full path ofprograms to be run on aWindows NT targetbefore the file package isdistributed.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Thedefault is no pathname.

nt_before_skip_non_zero

Indicates whether toskip the distribution toan NT target (notperformed) if theprograms specified bythent_before_prog_pathkeyword exits with anonzero exit code.


y = Skipn = Do not skip(default)

nt_commit_input_from_src

Indicates whether thefiles specified by thent_commit_input_path keyword resides onthe source host.

Commitprograms onWindows NTtargets




Keywords

nt_commit_input_path

Specifies a full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_commit_prog_pathkeyword (only valid ifyou set thent_commit_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_commit_prog_path keyword. Thedefault is no pathname.

nt_commit_option Indicates whether toreboot the target afterthe commit operationcompletes, restartWindows NT on thetarget after the commitoperation completes, orneither. If the commitprogram fails, a rebootor restart will not beperformed.



nt_commit_prog_from_src

Indicates whether theprograms specified bythent_commit_prog_pathkeyword resides on thesource host.




1–28 Version 3.6

Keywords File P

ackage Definitions

nt_commit_prog_path

Specifies the full path ofprograms to be run on anNT target during a filepackage commitoperation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nt_on_error_input_from_src

Specifies whether thefiles specified by thent_on_error_input_path keyword resides onthe source host.

On errorprograms onWindows NTtargets


nt_on_error_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_on_error_prog_path keyword (onlyvalid if you set thent_on_error_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_on_error_prog_path keyword. Thedefault is no pathname.



Keywords

nt_on_error_option Indicates whether toreboot or restart thetarget after the on errorprogram runs. If an onerror program isspecified and it fails, thetarget is not rebooted.


reboot = Reboot thetargetrestart = RestartWindows NT after theprogram runsNULL = Do notreboot (default)

nt_on_error_prog_from_src

Specifies whether theprograms specified bythent_on_error_prog_path keyword resides onthe source host.



nt_on_error_prog_path

Specifies a full path of aprogram to be run on aWindows NT target if anerror stops thedistribution of a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nt_platform_prefix Specifies a destinationpath for a PCs runningWindows NT.

Destinationpaths onWindows NTtargets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) on NTtargets. There is nodefault value.


1–30 Version 3.6

Keywords File P

ackage Definitions

nt_removal_input_from_src

Indicates whether thefiles specified by thent_removal_input_path keyword resides onthe source host.

Removalprograms onWindows NTtargets


nt_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythent_removal_prog_path keyword (onlyvalid if you set thent_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution and obtainsthe input files from thepath specified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thent_removal_prog_path keyword. Thedefault is no pathname.

nt_removal_option Indicates whether toreboot the target afterthe removal, restartWindows NT on thetarget after removal, orneither. If the removalprogram fails, a rebootor restart will not beperformed.





Keywords

nt_removal_prog_from_src

Indicates whether theprograms specified bythent_removal_prog_path keyword resides on thesource host.



nt_removal_prog_path

Specifies the full path ofprograms to be run onthe Windows NT targetbefore removing a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nw_after_input_from_src

Indicates whether thefiles specified by thenw_after_input_pathkeyword resides on thesource host.

Afterprograms onNetWaretargets



1–32 Version 3.6

Keywords File P

ackage Definitions

nw_after_input_path

Specifies the full path offiles whose name is to bepassed as the secondargument (argv [2]) tothe NLM or .NCF filesspecified by thenw_after_prog_pathkeyword (only valid ifyou set thenw_after_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_after_prog_path keyword. Thedefault is no pathname.

nw_after_prog_from_src

Indicates whether theprograms specified bythenw_after_prog_pathkeyword resides on thesource host.





Keywords

nw_after_prog_patha

Specifies the full path ofNLM or .NCF files to berun on a NetWare targetafter a file package’sfiles are distributed.If the programs andinput files reside on thesource host, you canspecify a relative path tothem. SoftwareDistribution runs theprograms and obtainsthe input files from thepath specified by thesrc_relpath keyword.



nw_after_removal_input_from_src

Specifies whether thefiles specified by thenw_after_removal_input_path keywordresides on the sourcehost.

After removalprograms onNetWaretargets



1–34 Version 3.6

Keywords File P

ackage Definitions

nw_after_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theNLM or .NCF filesspecified by thenw_after_removal_prog_path keyword(only valid if you set thenw_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_after_removal_prog_path keyword.The default is no pathname.

nw_after_removal_prog_from_src

Specifies whether theprograms specified bythenw_after_removal_prog_path keywordresides on the sourcehost.





Keywords

nw_after_removal_prog_patha

Specifies a full path ofNLM or .NCF files to berun on a NetWare targetafter removing a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nw_before_input_from_src

Indicates whether thefiles specified by thenw_before_input_pathkeyword resides on thesource host.

Beforeprograms onNetWaretargets


nw_before_input_path

Specifies the full path offiles to be passed as thesecond argument (argv[2]) to the NLM or .NCFfiles specified by thenw_before_prog_pathkeyword (only valid ifyou set thenw_before_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_before_prog_path keyword. Thedefault is no pathname.


1–36 Version 3.6

Keywords File P

ackage Definitions

nw_before_prog_from_src

Indicates whether theprograms specified bythenw_before_prog_pathkeyword resides on thesource host.



nw_before_prog_patha

Specifies the full path ofNLM or .NCF files to berun on a NetWare targetbefore the file package isdistributed.If the programs andinput files reside on thesource host, you canspecify a relative path tothem. SoftwareDistribution runs theprograms and obtainsthe input files from thepath specified by thesrc_relpath keyword.



nw_before_skip_non_zero

Indicates whether thedistribution to theNetWare target shouldbe skipped (notperformed) if theprograms specified bythenw_before_prog_pathkeyword exits with anonzero exit code.





Keywords

nw_bindery Indicates whether tologin to the NetWare 4.1server in bindery mode,thus, emulating aNetWare 3.x machine.If you set this keywordand bindery emulation isoff on the NetWareserver, the DirectoryServices account is usedwith thenw_contextandnw_tree keywords.


y = Login in binderymoden = Do not login inbindery mode(default)

nw_broadcast_message

Specifies the messagethat is broadcast toNetWare clientsconnected to theNetWare server prior tothe distribution to theserver.


A string of up to 255chars that is broadcastto NetWare targets ofthe distribution. Youdo not need to includenewlines in themessage; the agentformats it. There is nodefault value

nw_broadcast_mode Specifies whether tobroadcast the messagespecified by thenw_broadcast_messagekeyword to allNetWare clientsconnected to theNetWare server or onlythose clients that havelocked files which willbe distributed to theserver.


y = Broadcast themessage to allNetWare targets(default)n = Broadcast themessage to only thosetargets that havelocked files that willbe distributed


1–38 Version 3.6

Keywords File P

ackage Definitions

nw_commit_input_from_src

Indicates whether thefiles specified by thenw_commit_input_path keyword resides onthe source host.

Commitprograms onNetWaretargets


nw_commit_input_path

Specifies the full path offiles to be passed as thesecond argument (argv[2]) to the NLM or .NCFfiles specified by thenw_commit_prog_path keyword (onlyvalid if you set thenw_commit_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_commit_prog_path keyword. Thedefault is no pathname.

nw_commit_prog_from_src

Indicates whether theprograms specified bythenw_commit_prog_path keyword resides onthe source host.





Keywords

nw_commit_prog_patha

Specifies the full path ofNLM or .NCF files to berun on a NetWare targetduring a file packagecommit operation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nw_context Specifies the directoryservices context for adistribution to aNetWare 4.1 server. Ifthis keyword is notspecified, the defaultcontext for the targetserver as specified in theTMEAGENT.CFG fileis used.


A string that specifiesa valid directoryservices context onthe target server.There is no defaultvalue.

nw_force_disconnect Specifies whether tobreak a lock on a file andreplace the file during adistribution to aNetWare target.


y = Break the lockand replace the filen = Do not break thelock or replace the file(default)

nw_on_error_input_from_src

Specifies whether thefiles specified by thenw_on_error_input_path keyword resides onthe source host.

On errorprograms onNetWaretargets



1–40 Version 3.6

Keywords File P

ackage Definitions

nw_on_error_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theNLM or .NCF filesspecified by thenw_on_error_prog_path keyword (onlyvalid if you set thenw_on_error_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_on_error_prog_path keyword. Thedefault is no pathname.

nw_on_error_prog_from_src

Specifies whether theprograms specified bythenw_on_error_prog_path keyword resides onthe source host.





Keywords

nw_on_error_prog_patha

Specifies a full path ofNLM or .NCF files to berun on a NetWare targetif an error stops thedistribution of a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



nw_platform_prefix Specifies a destinationpath for NetWaretargets.

Destinationpaths onNetWaretargets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) onNetWare targets.There is no defaultvalue.

nw_removal_input_from_src

Indicates whether thefiles specified by thenw_removal_input_path keyword resides onthe source host.

Removalprograms onNetWaretargets



1–42 Version 3.6

Keywords File P

ackage Definitions

nw_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2]) to the NLM or.NCF files specified bythenw_removal_prog_path keyword (onlyvalid if you set thenw_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thenw_removal_prog_path keyword. Thedefault is no pathname.

nw_removal_prog_from_src

Indicates whether theprograms specified bythenw_removal_prog_path keyword resides onthe source host



nw_removal_prog_patha

Specifies the full path ofNLM or .NCF files to berun on a NetWare targetbefore removing a filepackage from thetargets.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.





Keywords

nw_tree Specifies a directoryservices tree to which todistribute a file packageon a NetWare target. Ifthis keyword is notspecified, the defaulttree for the target serveras specified in theTMEAGENT.CFG fileis used.


A string that specifiesa valid directoryservice tree on theNetWare target. Thereis no default value.

os2_after_input_from_src

Indicates whether thefiles specified by theos2_after_input_pathkeyword resides on thesource host.

Afterprograms onOS/2 targets


os2_after_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bytheos2_after_prog_path(only valid if you set theos2_after_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_after_prog_path keyword. Thedefault is no pathname.

os2_after_option Provided for future use. Afterprograms onOS/2 targets

None


1–44 Version 3.6

Keywords File P

ackage Definitions

os2_after_prog_from_src

Indicates whether theprograms specified bytheos2_after_prog_pathkeyword resides on thesource host.



os2_after_prog_path

Specifies the full path ofprograms to be run on anOS/2 target after a filepackage’s files aredistributed.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



os2_after_removal_input_from_src

Specifies whether thefiles specified by theos2_after_removal_input_path keywordresides on the sourcehost.

After removalprograms onOS/2 targets




Keywords

os2_after_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bytheos2_after_removal_prog_path keyword(only valid if you set theos2_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_after_removal_prog_path keyword.The default is no pathname.

os2_after_removal_option

Provided for future use. After removalprograms onOS/2 targets

None

os2_after_removal_prog_from_src

Specifies whether theprograms specified bytheos2_after_removal_prog_path keywordresides on the sourcehost.




1–46 Version 3.6

Keywords File P

ackage Definitions

os2_after_removal_prog_path

Specifies a full path ofprograms to be run on anOS/2 target afterremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



os2_before_input_from_src

Indicates whether thefiles specified by theos2_before_input_path keyword resides onthe source host.

Beforeprograms onOS/2 targets


os2_before_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bytheos2_before_prog_pathkeyword (only valid ifyou set theos2_before_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_before_prog_path keyword. Thedefault is no pathname.



Keywords

os2_before_prog_from_src

Indicates whether theprograms specified bytheos2_before_prog_pathkeyword resides on thesource host.



os2_before_prog_path

Specifies the full path ofprograms to be run on anOS/2 target before thefile package isdistributed.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



os2_before_skip_non_zero

Indicates whether thedistribution to the OS/2target should be skipped(not performed) if theprogram specified by theos2_before_prog_pathkeyword exits with anonzero exit code.



os2_commit_input_from_src

Indicates whether thefiles specified by theos2_commit_input_path keyword resides onthe source host.

Commitprograms onOS/2 targets



1–48 Version 3.6

Keywords File P

ackage Definitions

os2_commit_input_path

Specifies the full path ofa file to be passed as thesecond argument(argv[2] or %2) toos2_commit_prog_path (only meaningfulif os2_commit_prog_path is set).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_commit_prog_path keyword. Thedefault is no pathname.

os2_commit_option Provided for future use. Commitprograms onOS/2 targets

None

os2_commit_prog_from_src

Indicates whether theprogram specified by theos2_commit_prog_path keyword resides onthe source host.



os2_commit_prog_path

Specifies the full path ofprograms to be run oneach OS/2 target duringa file package commitoperation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.





Keywords

os2_on_error_input_from_src

Specifies whether thefiles specified by theos2_on_error_input_path keyword resides onthe source host.

On errorprograms onOS/2 targets


os2_on_error_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bytheos2_on_error_prog_path keyword (onlyvalid if you set theos2_on_error_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_on_error_prog_path keyword.The default is no pathname.

os2_on_error_option

Provided for future use. On errorprograms onOS/2 targets

None

os2_on_error_prog_from_src

Specifies whether theprograms specified bytheos2_on_error_prog_path keyword resides onthe source host.




1–50 Version 3.6

Keywords File P

ackage Definitions

os2_on_error_prog_path

Specifies a full path ofprograms to be run on anOS/2 target if an errorstops the distribution ofa file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



os2_platform_prefix Specifies a destinationpath for PCs runningOS/2.

Destinationpaths on OS/2targets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) onOS/2 targets. There isno default value.

os2_removal_input_from_src

Indicates whether thefiles specified by theos2_removal_input_path keyword resides onthe source host.

Removalprograms onOS/2 targets




Keywords

os2_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bytheos2_removal_prog_path keyword (onlyvalid if you set theos2_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theos2_removal_prog_path keyword. Thedefault is no pathname.

os2_removal_option Provided for future use. Removalprograms onOS/2 targets

None

os2_removal_prog_from_src

Indicates whether theprograms specified bytheos2_removal_prog_path keyword resides onthe source host.




1–52 Version 3.6

Keywords File P

ackage Definitions

os2_removal_prog_path

Specifies the full path ofprograms to be run on anOS/2 target beforeremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



post_notice Indicates whether topost notices to theSoftware Distributionnotice group when filepackage distribution,commit, or removaloperations areperformed.


y = Post notice(default)n = Do not postnotice

postproc Provides a means ofencoding data for filepackages. You canspecify a processingfilter to encrypt filepackage data just beforeit leaves the source host.This keyword must beused in conjunction withthepreproc keyword.

File packageencryptionprocessing onUNIX targets

Any string withoutembedded new-lines.This option is ignoredon PCs. There is nodefault value.



Keywords

preproc Provides a means ofdecoding data for filepackages. You canspecify a processingfilter to decrypt the filepackage as it arrives atthe target. This keywordmust be used inconjunction with thepostproc keyword.

File packagedecryptionprocessing onUNIX targets

Any string withoutembedded new-lines.This option is ignoredon PCs. There is nodefault value.

prog_env Specifies a string thatwill be the subject of aputenv before anyconfiguration program isrun on a UNIX machine.The string is a list ofname=valuepairs.Given a file packagenamedGNU Emacswith aunix_platform_prefixof /usr/local/bin/gnu,consider the followingexample:prog_env=“DEST=$unix_platform_prefixFPNAME=‘$fpname’”Within a configurationprogram,$DESTwouldbe/usr/local/bin/gnuand$FPNAME wouldbe“GNU Emacs.”

Configura-tion programson UNIXtargets

Any environmentvariable value. Youcan provide a variablename that matchesany file packagekeyword. These areexpanded into the filepackage’s value forthe keyword.Note: The filepackage name is not akeyword;$fpnameissupported as a specialstring because mostconfigurationprograms need accessto the file packagename. There is nodefault value.


1–54 Version 3.6

Keywords File P

ackage Definitions

progs_timeout Sets a timeout value forall configurationprograms specified inthe file package. Thistimeout value is onlyrecognized onendpoints.

Configura-tion programson endpoints

Any decimal value.The default is -l,enabling theconfigurationprogram to run untilcompletion (notimeout).

rm_empty_dirs Indicates whether toremove all empty targetdirectories at the targetsafter a file package isremoved. Emptydirectories are removedup to, but not includingxxx_platform_prefix +default_dest.


y = Remove emptydirectoriesn = Do not removeempty directories(default)

rm_extraneous Indicates whether toremove all files anddirectories in an existingdestination directoryprior to installing a filepackage.


y = Removeextraneous filesn = Do not removeextraneous files(default)

skip_older_src Indicates whether tooverwrite a target file ifit is newer than thesource file.


y = Do not overwritethe target file with thesource file if thesource file is oldern = Overwrite thetarget file with thesource file regardlessof which one is older(default)

src_after_as_uidb Specifies the UID of theuser under which to runsrc_after_prog_path.

Afterprograms onthe sourcehost

Any decimal valuevalid as a UID on thesource system. Thedefault is to run asroot.



Keywords

src_after_input_path

Specifies files to bepassed through standardinput to the programsspecified by thesrc_after_prog_pathkeyword (only valid ifyou set thesrc_after_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpathkeyword. Ifthe input files reside onthe target, you mustspecify a full path toeach.


One or more valid filenames, separated bycommas (no spaces).The order of theseinput filescorresponds directlywith the order of theprograms specified bythesrc_after_prog_path keyword. Thedefault is no pathname.

src_after_prog_path Specifies programs to berun on the source hostafter the file package isdistributed to the targets.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpathkeyword. Ifthe programs reside onthe target, you mustspecify a full path toeach.


One or more valid filenames, separated bycommas (no spaces).The default is no pathname.


1–56 Version 3.6

Keywords File P

ackage Definitions

src_before_as_uidb Specifies the UID of theuser under which to runthe programs specifiedby thesrc_before_prog_pathkeyword.

Beforeprograms onthe sourcehost

Any decimal valuevalid as a UID on thesource system. Thedefault is to run asroot.

src_before_input_path

Specifies files to bepassed through standardinput to the programsspecified by thesrc_before_prog_pathkeyword (only valid ifyou set thesrc_before_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpathkeyword. Ifthe input files reside onthe target, you mustspecify a full path toeach.


One or more valid filenames, separated bycommas (no spaces).The order of theseinput filescorresponds directlywith the order of theprograms specified bythesrc_before_prog_path keyword. Thedefault is no pathname.



Keywords

src_before_prog_path

Specifies programs to berun on the source hostbefore the file package isdistributed to the targets.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpathkeyword. Ifthe programs reside onthe target, you mustspecify a full path toeach.


One or more valid filenames, separated bycommas (no spaces).The default is no pathname.

src_before_skip_non_zero

Indicates whether thedistribution to the targetshould be skipped (notperformed) if theprograms specified bythesrc_before_prog_pathkeyword exits with anonzero exit code.




1–58 Version 3.6

Keywords File P

ackage Definitions

src_relpath Specifies the path on thesource host from whichrelative files anddirectories in the filepackage are obtained.You can specifyprograms and input filesthat reside on the sourcehost with relative paths.Software Distributionadds the path specifiedby this keyword to thebeginning of the paths ofthe programs or inputfiles.


A full path on thesource host. There isno default value.

stop_on_error Indicates whether tostop processing to thetarget if an error occurswhile distributing orremoving to the target.


y = Stop processingin the event of anerror (default)n = Do not stopprocessing in theevent of an error

unix_after_as_uidb Specifies the UID of theuser under which to runthe programs specifiedby theunix_after_prog_pathkeyword.

Afterprograms onUNIX targets

Any decimal valuevalid as a UID on thetarget systems. Thedefault is to run asroot.

unix_after_input_from_src

Indicates whether thefiles specified by theunix_after_input_pathkeyword resides on thesource host





Keywords

unix_after_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_after_prog_pathkeyword (only valid ifyou set theunix_after_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_after_prog_path keyword. Thedefault is no pathname.

unix_after_prog_from_src

Indicates whether theprograms specified bytheunix_after_prog_pathkeyword resides on thesource host.



unix_after_prog_path

Specifies the full path ofprograms to be run on aUNIX target after a filepackage’s files areapplied to that target.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.




1–60 Version 3.6

Keywords File P

ackage Definitions

unix_after_removal_as_uidb

Specifies the UID of theuser under which to runthe program specified bytheunix_after_removal_prog_path keyword.

After removalprograms onUNIX targets


unix_after_removal_input_from_src

Specifies whether thefiles specified by theunix_after_removal_input_path keywordresides on the sourcehost.



unix_after_removal_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_after_removal_prog_path keyword(only valid if you set theunix_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_after_removal_prog_pathkeyword. The defaultis no path name.

unix_after_removal_prog_from_src

Specifies whether theprograms specified bytheunix_after_removal_prog_path keywordresides on the sourcehost.





Keywords

unix_after_removal_prog_path

Specifies a full path ofprograms to be run on aUNIX target afterremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



unix_before_as_uidb

Specifies the UID of theuser under which to runthe program specified bytheunix_before_prog_path keyword.

Beforeprograms onUNIX targets

Any decimal valuevalid as a UID on thetarget system. Thedefault is to run asroot.

unix_before_input_from_src

Indicates whether thefiles specified by theunix_before_input_path keyword resides onthe source host.




1–62 Version 3.6

Keywords File P

ackage Definitions

unix_before_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_before_prog_path keyword (onlyvalid if you set theunix_before_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_before_prog_path keyword. Thedefault is no pathname.

unix_before_prog_from_src

Indicates whether theprograms specified bytheunix_before_prog_path keyword resides onthe source host.


y = Resides on thesource host.n = Resides on thetarget (default)

unix_before_prog_path

Specifies the full path ofprograms to be run oneach UNIX target beforea file package’s files aredistributed.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.





Keywords

unix_before_skip_non_zero

Indicates whether toskip (not perform) theapplication of a filepackage’s files to aUNIX target if theunix_before_prog_path program that runson that target exits witha nonzero exit code.



unix_commit_as_uidb

Specifies the UID underwhich to run theprogram specified by theunix_commit_prog_path keyword.

Commitprograms onUNIX targets


unix_commit_input_from_src

Indicates whether thefiles specified by theunix_commit_input_path keyword resides onthe source host.



unix_commit_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_commit_prog_path keyword (onlyvalid if you set theunix_commit_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_commit_prog_path keyword. Thedefault is no pathname.


1–64 Version 3.6

Keywords File P

ackage Definitions

unix_commit_prog_from_src

Indicates whether theprograms specified bytheunix_commit_prog_path keyword resides onthe source host.



unix_commit_prog_path

Specifies the full path ofprograms to be run oneach UNIX target duringa file package commitoperation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



unix_default_dir_gidb

Specifies the defaultGID for all directoriesdistributed in the filepackage.

Security onUNIX targets

Any decimal numbervalid as a GID on thetarget system or thename of a group onthe TMR server. Thedefault is to preservethe GID of the source.

unix_default_dir_uidb

Specifies the defaultUID for all directoriesdistributed in the filepackage.


Any decimal numbervalid as a UID on thetarget system or thename of a user on theTMR server. Thedefault is to preservethe UID of the source.



Keywords

unix_default_file_gidb

Specifies the defaultGID for all files andlinks distributed in thefile package.


Any decimal numbervalid as a GID on thetarget system or thename of a group onthe TMR server. Thedefault is to preservethe GID of the source.

unix_default_file_uidb

Specifies the defaultUID for all files andlinks distributed in thefile package.


Any decimal numbervalid as a user id onthe target system orthe name of a user onthe TMR server. Thedefault is to preservethe UID of the source.

unix_on_error_as_uidb

Specifies the UID of theuser under which to runthe programs specifiedby theunix_on_error_prog_path keyword.

On errorprograms onUNIX targets


unix_on_error_input_from_src

Specifies whether thefiles specified by theunix_on_error_input_path keyword resides onthe source host.




1–66 Version 3.6

Keywords File P

ackage Definitions

unix_on_error_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_on_error_prog_path keyword (onlyvalid if you set theunix_on_error_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_on_error_prog_pathkeyword. Thedefault is no pathname.

unix_on_error_prog_from_src

Specifies whether theprograms specified bytheunix_on_error_prog_path keyword resides onthe source host.



unix_on_error_prog_path

Specifies a full path ofprograms to be run on aUNIX target if an errorstops the distribution ofa file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.





Keywords

unix_platform_prefix

Specifies a destinationpath for UNIX targets.

Destinationpaths onUNIX targets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) onUNIX targets. Thereis no default value.

unix_removal_as_uidb

Specifies the UID of theunder which to run theprograms specified bytheunix_removal_prog_path keyword.

Removalprograms onUNIX targets


unix_removal_input_from_src

Indicates whether thefiles specified by theunix_removal_input_path keyword resides onthe source host.



unix_removal_input_path

Specifies the full path offiles to be passedthrough standard inputto the programsspecified by theunix_removal_prog_path keyword (onlyvalid if you set theunix_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by theunix_removal_prog_path keyword.The default is no pathname.


1–68 Version 3.6

Keywords File P

ackage Definitions

unix_removal_prog_from_src

Indicates whether theprograms specified bytheunix_removal_prog_path keyword resides onthe source host.



unix_removal_prog_path

Specifies the full path ofprograms to be run on aUNIX target beforeremoving a filepackage’s files fromthose targets.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win_after_input_from_src

Indicates whether thefiles specified by thewin_after_input_pathkeyword resides on thesource host.

Afterprograms onWindowstargets




Keywords

win_after_input_path

Specifies a full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_after_prog_pathkeyword (only valid ifyou set thewin_after_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_after_prog_path keyword. Thedefault is no pathname.

win_after_option Indicates whether toreboot the target afterthe program runs, restartWindows on the targetafter the program runs,or neither. If the afterprogram fails, a rebootor restart will not beperformed.


reboot = Reboot thetarget after theprogram runsrestart = RestartWindows after theprogram runsNULL = Do notreboot, or restartWindows (default)

win_after_prog_from_src

Indicates whether theprograms specified bythewin_after_prog_pathkeyword resides on thesource host.




1–70 Version 3.6

Keywords File P

ackage Definitions

win_after_prog_path

Specifies the full path ofprograms to be run on aWindows target after afile package’s files aredistributed.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win_after_removal_input_from_src

Specifies whether thefiles specified by thewin_after_removal_input_path keywordresides on the sourcehost.

After removalprograms onWindowstargets




Keywords

win_after_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_after_removal_prog_path keyword(only valid if you set thewin_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.

After removalprograms onWindowstargets

One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_after_removal_prog_path keyword.The default is no pathname.

win_after_removal_option

Indicates whether toreboot the target afterthe program runs, restartWindows on the targetafter the program runs,or neither. If theafter_removal programfails, the target is notrebooted or restarted.

Afterremovalprograms onWindowstargets


win_after_removal_prog_from_src

Specifies whether theprograms specified bythewin_after_removal_prog_path keywordresides on the sourcehost.




1–72 Version 3.6

Keywords File P

ackage Definitions

win_after_removal_prog_path

Specifies a full path ofprograms to be run oneachWindows target afterremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win_before_input_from_src

Indicates whether thefiles specified by thewin_before_input_path keyword resides onthe source host.

Beforeprograms onWindowstargets


win_before_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_before_prog_pathkeyword (only valid ifyou set thewin_before_prog_pathkeyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_before_prog_path keyword. Thedefault is no pathname.



Keywords

win_before_prog_from_src

Indicates whether theprograms specified bythewin_before_prog_pathkeyword resides on thesource host.



win_before_prog_path

Specifies the full path ofprograms to be run on aWindows target beforethe file package isdistributed to that target.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win_before_skip_non_zero

Indicates whether thedistribution to theWindows target shouldbe skipped (notperformed) if theprogram specified by thewin_before_prog_pathkeyword exits with anonzero exit code.



win_commit_input_from_src

Indicates whether thefiles specified by thewin_commit_input_path keyword resides onthe source host.

Commitprograms onWindowstargets



1–74 Version 3.6

Keywords File P

ackage Definitions

win_commit_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_commit_prog_path keyword (onlyvalid if you set thewin_commit_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_commit_prog_path keyword. Thedefault is no pathname.

win_commit_option Indicates whether toreboot the target afterthe commit operationcompletes, restartWindows on the targetafter the commitoperation completes, orneither. If the commitprogram fails, a rebootor restart will not beperformed.



win_commit_prog_from_src

Indicates whether thewin_commit_prog_path resides on thesource host.





Keywords

win_commit_prog_path

Specifies the full path ofprograms to be run oneach Windows targetduring a file packagecommit operation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win_on_error_input_from_src

Specifies whether thefiles specified by thewin_on_error_input_path keyword resides onthe source host.

On errorprograms onWindowstargets


win_on_error_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_on_error_prog_path keyword (onlyvalid if you set thewin_on_error_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_on_error_prog_path keyword.The default is no pathname.


1–76 Version 3.6

Keywords File P

ackage Definitions

win_on_error_option

Indicates whether toreboot the target afterthe program runs, restartWindows on the targetafter the program runs,or neither. If the on errorprogram fails, the targetis not rebooted orrestarted.



win_on_error_prog_from_src

Specifies whether theprograms specified bythewin_on_error_prog_path keyword resides onthe source host.



win_on_error_prog_path

Specifies a full path ofprograms to be run on aWindows target if anerror stops thedistribution of a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.





Keywords

win_optional_dist Indicates whether thedistribution is optionalor mandatory.If the distribution isoptional, the user at thetarget gets a pop-updialog at distribution orremoval time. From thisdialog, the user canchoose whether to havethe file packagedistributed to orremoved from his or hermachine. If thedistribution ismandatory, no suchdialog is presented to theuser—the file package isautomaticallydistributedor removed. If the userdoes not respond withinthe time specified inwin_optional_dist_timeout, the distributionor removal takes place.

Optionaldistribu- tionsto Windowstargets

y= Provides a dialogat distribution orremoval time on thetarget in which theuser can choosewhether to have thefile packagedistributed to orremoved from his orher machinen = Automaticallydistributes or removesthe file package withno option to overrideprovided to the user atthe target (default)

win_optional_dist_timeout

Indicates the time inseconds that the optionaldistribution dialog isdisplayed on the target.If the user does notrespond within thespecified time period,the distribution orremoval occurs. This isonly valid ifwin_optional_dist isset toy.

Optionaldistribu- tionsto Windowstargets

Any integer in therange 1 through 6000.The default is 120.


1–78 Version 3.6

Keywords File P

ackage Definitions

win_platform_prefix

Specifies a destinationpath for PCs runningWindows.

Destinationpaths onWindowstargets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) onWindows targets.There is no defaultvalue.

win_removal_input_from_src

Indicates whether thefiles specified by thewin_removal_input_path keyword resides onthe source host.

Removalprograms onWindowstargets


win_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin_removal_prog_path keyword (onlyvalid if you set thewin_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin_removal_prog_path keyword. Thedefault is no pathname.



Keywords

win_removal_option Indicates whether toreboot the target afterthe removal, restartWindows on the targetafter removal, or neither.If the removal programfails, a reboot or restartwill not be performed.



win_removal_prog_from_src

Indicates whether theprograms specified bythewin_removal_prog_path keyword resides onthe source host.



win_removal_prog_path

Specifies the full path ofprograms to be run onthe Windows targetbefore removing a filepackage from that target.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win95_after_input_from_src

Indicates whether thefiles specified by thewin95_after_input_path keyword resides onthe source host.

Afterprograms onWindows 95targets



1–80 Version 3.6

Keywords File P

ackage Definitions

win95_after_input_path

Specifies a full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_after_prog_path keyword (onlyvalid if you set thewin95_after_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_after_prog_path keyword. Thedefault is no pathname.

win95_after_option Indicates whether toreboot the target afterthe program runs, restartWindows 95 on thetarget after the programruns, or neither. If theafter program fails, areboot or restart will notbe performed.


reboot = Reboot thetarget after theprogram runsrestart = RestartWindows 95 after theprogram runsNULL = Do notreboot, or restartWindows 95 (default)

win95_after_prog_from_src

Indicates whether theprograms specified bythewin95_after_prog_path keyword resides onthe source host.





Keywords

win95_after_prog_path

Specifies the full path ofprograms to be run oneach Windows 95 targetafter a file package’sfiles are applied to thattarget.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win95_after_removal_input_from_src

Specifies whether thefiles specified by thewin95_after_removal_input_path keywordresides on the sourcehost.

After removalprograms onWindows 95targets



1–82 Version 3.6

Keywords File P

ackage Definitions

win95_after_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_after_removal_prog_path keyword(only valid if you set thewin95_after_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_after_removal_prog_pathkeyword. The defaultis no path name.

win95_after_removal_option

Indicates whether toreboot the target afterthe program runs, restartWindows 95 on thetarget after the programruns, or neither. If theafter removal programfails, the target is notrebooted or restarted.

Afte removalprograms onWindows 95targets


win95_after_removal_prog_from_src

Specifies whether theprograms specified bythewin95_after_removal_prog_path keywordresides on the sourcehost.





Keywords

win95_after_removal_prog_path

Specifies a full path ofprograms to be run on aWindows 95 target afterremoving a file package.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.

Afterremovalprograms onWindows 95targets


win95_before_input_from_src

Indicates whether thefiles specified by thewin95_before_input_path keyword resides onthe source host.

Beforeprograms onWindows 95targets


win95_before_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_before_prog_path keyword (onlyvalid if you set thewin95_before_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_before_prog_path keyword.The default is no pathname.


1–84 Version 3.6

Keywords File P

ackage Definitions

win95_before_prog_from_src

Indicates whether theprograms specified bythewin95_before_prog_path keyword resides onthe source host.



win95_before_prog_path

Specifies the full path ofprograms to be run on aWindows 95 targetbefore the file package isdistributed to that target.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win95_before_skip_non_zero

Indicates whether thedistribution to theWindows 95 targetshould be skipped (notperformed) if programsspecified by thewin95_before_prog_path keyword exits witha nonzero exit code.



win95_commit_input_from_src

Indicates whether thefiles specified by thewin95_commit_input_path keyword resides onthe source host.

Commitprograms onWindows 95targets




Keywords

win95_commit_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_commit_prog_path keyword (onlyvalid if you set thewin95_commit_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_commit_prog_path keyword.The default is no pathname.

win95_commit_option

Indicates whether toreboot the target afterthe commit operationcompletes, restartWindows 95 on thetarget after the commitoperation completes, orneither. If the commitprogram fails, a rebootor restart will not beperformed.



win95_commit_prog_from_src

Indicates whether theprograms specified bythewin95_commit_prog_path keyword resides onthe source host.




1–86 Version 3.6

Keywords File P

ackage Definitions

win95_commit_prog_path

Specifies the full path ofprograms to be run on aWindows 95 targetduring a file packagecommit operation.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



win95_on_error_input_from_src

Specifies whether thefiles specified by thewin_on_error_input_path keyword resides onthe source host.



win95_on_error_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_on_error_prog_ path keyword(only valid if you set thewin95_on_error_prog_ path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_on_error_prog_path keyword.The default is no pathname.



Keywords

win95_on_error_option

Indicates whether toreboot the target afterthe program runs, restartWindows 95 on thetarget after the programruns, or neither. If the onerror program fails, thetarget is not rebooted orrestarted.

On errorprograms onWindows 95targets


win95_on_error_prog_from_src

Specifies whether theprograms specified bythewin95_on_error_prog_ path keywordresides on the sourcehost.



win95_on_error_prog_path

Specifies a full path ofprograms to be run on aWindows 95 target if anerror stops thedistribution of a filepackage.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.




1–88 Version 3.6

Keywords File P

ackage Definitions

win95_optional_dist Indicates whether thedistribution is optionalor mandatory.If the distribution isoptional, the user at thetarget gets a pop-updialog at distribution orremoval time. From thisdialog, the user canchoose whether to havethe file packagedistributed to orremoved from his or hermachine. If thedistribution ismandatory, no suchdialog is presented to theuser—the file package isautomaticallydistributedor removed. If the userdoes not respond withinthe time specified inwin95_optional_dist_timeout, the distributionor removal takes place.

Optionaldistribu- tionsto Windows95 targets

y= Provides a dialogat distribution orremoval time on thetarget in which theuser can choosewhether to have thefile packagedistributed to orremoved from his orher machinen = Automaticallydistributes or removesthe file package withno option to overrideprovided to the user atthe target (default)

win95_optional_dist_timeout

Indicates the time inseconds that the optionaldistribution dialog isdisplayed on the target.If the user does notrespond within thespecified time period,the distribution orremoval occurs. This isonly valid ifwin95_optional_dist isset toy.

Optionaldistribu- tionsto Windows95 targets

Any integer in therange 1 through 6000.The default is 120.



Keywords

win95_platform_prefix

Specifies a destinationpath for PCs runningWindows 95.

Destinationpaths onWindows 95targets

A path that is addedto the beginning ofeach destination path(as specified bydefault_dest) onWindows 95 targets.There is no defaultvalue.

win95_removal_input_from_src

Indicates whether thefiles specified by thewin95_removal_input_ path keywordresides on the sourcehost.

Removalprograms onWindows 95targets


win95_removal_input_path

Specifies the full path offiles to be passed as thesecond argument(argv[2] or %2) to theprograms specified bythewin95_removal_prog_path keyword (onlyvalid if you set thewin95_removal_prog_path keyword).If the input files resideon the source host, youcan specify a relativepath to them. SoftwareDistribution obtains theinput files from the pathspecified by thesrc_relpath keyword.


One or more valid,complete file names,separated by commas(no spaces). Theorder of these inputfiles correspondsdirectly with the orderof the programsspecified by thewin95_removal_prog_path keyword.The default is no pathname.


1–90 Version 3.6

Keywords File P

ackage Definitions

p

win95_removal_option

Indicates whether toreboot the target afterthe removal, restartWindows 95 on thetarget after removal, orneither. If the removalprogram fails, a rebootor restart will not beperformed.



win95_removal_prog_from_src

Indicates whether theprograms specified bythewin95_removal_prog_path keyword resides onthe source host.



win95_removal_prog_path

Specifies the full path ofprograms to be run on aWindows 95 targetbefore removing a filepackage from that target.If the programs resideon the source host, youcan specify a relativepath to them. SoftwareDistribution runs theprograms from the pathspecified by thesrc_relpath keyword.



a. .NCF files are supported as NetWare configuration programs, however, they are executedasynchronously to the file package. If an.NCF configuration program starts successfully, it notifiesthe agent and the file package distribution begins. The distribution continues regardless of the.NCFprogram’s completion status.

b. User and group symbolic names are mapped to numeric UIDs and GIDs according to user and groudefinitions on the source host. If you specify a symbolic UID or GID using the export/importcapability, it is resolved on the source host. However, if you specify a symbolic UID or GID using thedesktop, it is resolved to the numeric ID on the server.



Keywords

1–92 Version 3.6

Keywords File P

ackage Definitions


Keywords

1–94 Version 3.6

Com

mands

ad ad.

to

nt

ile

2Commands

TME 10 command line interface (CLI) commands enable you toperform system operations from a UNIX or PC command line insteof using the TME 10 desktop. Most TME 10 commands begin withw and often vowels are omitted to shorten the name of a commanCommands are also developed using thew+verb+object syntax,which matches the way you might think of the action. For example,import a file package definition, use thewimprtfp command. Todistribute a file package, use thewdistfp command.

Using TME 10 CommandsIt is often necessary or convenient to invoke a TME 10 managemeapplication operation from the command line rather than from thedesktop. For example:

■ You do not have access to a desktop, for example if you areconnected to the network via modem

■ You want to group several operations in a shell script or batch f

■ An operation is not available using the desktop

■ You prefer to invoke a command from a shell

2


Command Line Syntax

ters

d

e

e

ts

re

ent

anther

Command Line SyntaxThe manual pages in this appendix use the following special characto define the command syntax:

[ ] Identify optional arguments. Arguments not enclosein brackets are required.

... Indicates that you can specify multiple values for thprevious argument.

| Indicates mutually exclusive information. You can usthe argument to the left of the separator or theargument to its right. You cannot use both argumenin a single use of the command.

{ } Delimits a set of mutually exclusive arguments whenone of the arguments is required. If the arguments aoptional, they are enclosed in square brackets ([ ]).

For example:

wdistfp { -a | -n | -s} { -b | -c | -d | -p} fp_name [subscriber...]

The ellipses (...) following thesubscriberargument indicate that youcan specify multiple subscribers. Also, you must specify one argumin each set of arguments delimited by the| (logical or) and enclosed in{ } (braces), and thefp_name argument.

Another example is thewsetfpprgs command.

wsetfpprgs { -t type| -T type} [ keyword_option...] fp_name

In this example, the–t type and–T type arguments are mutuallyexclusive; you must use one or the other. Thekeyword_optionargumentis an optional argument and you can specify it more thanonce. Thefp_nameargument is required.

Object ReferencesWhen you reference an object in a command, the reference is notabsolute object reference like those used in programming. Instead,reference is the label you gave the object when it was created. Foexample, when you refer to theEngineeringobject in a command, thisreference corresponds to theEngineering policy region.

2–2 Version 3.6

Object References

Com

mands

ou

ameome a

e.te.

for

There are two different forms of names that can be used withcommands:

■ Registered names

■ Object paths

TME 10 commands support both naming schemes. Sometimes, ywill find it more convenient to use one form over the other.

Registered NamesThe key concept behind the name registry is aregistered name. Aregistered name is a resource instance that is registered with the nregistry when it is created. Every resource has a name and is of sparticular type. For example, a UNIX machine called pescado hasnamepescadoand is of typeManagedNode. An example of aregistered name used as an argument for thewdistfp command is:

wdistfp -d @FilePackage:example_fp @ManagedNode:pescado

The syntax for specifying a resource using a registered name is@type:name, wheretypeis the resource type andnameis the instanceon which you wish to perform some operation. You must alwaysspecify the ampersand character (@) before a registered name. In theabove example, the file packageexample_fp is distributed to themanaged nodepescado.

Object PathsObject paths provide another way for you to specify an object namThey are similar to paths in file systems and can be relative or absoluAn absolute path begins with a backslash character (/). A relative pathbegins with any character including the special path components the current directory (./) and for the parent directory (../). Someexamples of object paths used as arguments for thewcd and wdistfpcommands are:

wdistfp -a -d /Regions/Distr/Source/PS_docs \/Regions/pescado-region/pescado

wcd /Library/ManagedNode

wdistfp -a -d /Library/FilePackage/PS_docs ./pescado


TME 10 Software Distribution Commands

s

The syntax for specifying a resource using an object path is/Regions/ObjectPath/[type:]name, whereObjectPathis the path to theobject,typeis the resource type, andnameis the particular instance onwhich you wish to perform some operation. Use the optionaltypespecifier if the specified resource has the same name as anotherresource of a different type.

In the above examples, thePS_docs file package is distributed to themanaged nodepescado. This file package resides in theDistr policyregion andSource profile manager, as indicated by the object pathafter /Regions. You can also specify the file package and managednode in terms of their class library (/Library ), as illustrated by thesecond and third examples.

TME 10 Software Distribution CommandsThe following table lists the TME 10 Software Distribution commandthat you can run from the command line of a managed node:

Command Purpose

wcpfpblock Copies a file package block from an existing filepackage block to the specified targets.

wcrtfpblock Creates a file package block from an existing filepackage definition on the specified target.

wdistfp Distributes, commits, or previews a file package.

wdistfpblock Distributes the files in a file package block to thespecified targets.

wexprtfp Exports a file package definition.

wgetfpattr Gets the attributes for a file package.

wimprtfp Imports a file package definition.

winstruct_file Provides TME 10 Software Distribution withinformation necessary to install and manage anapplication.

wmvapobj Moves AutoPacks from thelost-n-found collection toa profile manager.

2–4 Version 3.6


Com

mands

r

)

The following table lists the PC agent commands:

wmvfpobj Moves a file package from thelost-n-found collectionto a profile manager.

wrmfp Removes the files in a file package definition from atarget.

wrmfpblock Removes the files in a file package block from thespecified targets.

wsetfpattr Sets the attributes for a file package.

wsetfpcontents Sets the source host, file list, nested file package list, oexclude file list for a file package.

wsetfpopts Sets or modifies the options for a file package.

wsetfpprgs Sets or modifies the configuration programinformation associated with a file package.

wswdistrim Sets the tracking feature to control when SoftwareDistribution information is updated in the TME 10Inventory configuration repository.

Command Purpose

Command Purpose

waddicon Adds an icon to a Windows Program Manager group.(win, win95, nt)

waddpath Adds an entry to the path statement on a Windows NTmachine. (nt)

wclrblk Removes a block of statements from a file. (allsupported PC platforms)

wclrline Removes a single line from a file. (all supported PCplatforms)

wcpyfile Copies a file to the specified target volume and file. (nw



I

)

wdskspc Verifies the amount of disk space available. (win, win95,nt, nw)

weditini Manipulates the groups, variables and values in an .INfile. (all supported PC platforms)

wgetkey Retrieves the subkey listing in a registry hive. (win95,nt)

wgetval Retrieves a registry subkey. (win95, nt)

winsblk Inserts a block of statements into a file. (all supportedPC platforms)

winsline Inserts a single line into a file. (all supported PCplatforms)

wmrgini Merges groups and variables from one .INI file intoanother. (all supported PC platforms)

wrestart Initiates a system restart and optional reboot. (win95, nt

wrplblk Replaces a block of statements in a file. (all supportedPC platforms)

wrplline Replaces a single line in a file. (all supported PCplatforms)

wrunprog Runs a Windows program from a DOS batch file. (win)

wseterr Sets the return code from a batch file for a configurationprogram. (all supported PC platforms)

wsettrus Assigns trustee rights to directories or files. (nw)

wsetval Sets a registry key value. (win95, nt)

Command Purpose

2–6 Version 3.6

NetWare Managed Site Commands

Com

mands

o

ke

m

NetWare Managed Site CommandsThe following table lists the commands available for setting andediting properties of NetWare managed sites, for monitoring andsetting clients of TME 10 NetWare repeaters (TNWRs), and fordealing with files on the client of a NetWare managed site. Thesecommands are fully documented in theTME 10 Framework ReferenceManual.

Command Purpose

waddclnt Adds a client to the TNWRs list of available clients.(invoke from a NetWare server)

wcrtnwms Creates a NetWare managed site. (invoke from a TMRserver)

wdirnwc Lists the contents of a directory on a client of a NetWaremanage site. (invoke from a TMR server)

wexecnwc Executes a program on a client of a NetWare managedsite. (invoke from a TMR server)

wgetnwcfile Copies a file from a client of a NetWare managed site tthe TME server. (invoke from a TMR server)

wgetnwms Retrieves properties of a NetWare managed site. (invofrom a TMR server)

wlstclnt Lists all available clients of a TNWR. (invoke from aNetWare server)

wpolclnt Polls a client of a TNWR (to verify that its agent isrunning) and edits the client’sTMEAGENT.CFG file.(invoke from a NetWare server)

wputnwcfile Copies a file from the TMR server to the client aNetWare managed site. (invoke from a TMR server)

wrmvclnt Removes a client from a TNWR’s list of availableclients. (invoke from a NetWare server)

wsetnwms Sets properties of a NetWare managed site. (invoke froa TMR server)


Command Syntax

Command SyntaxThis section lists TME 10 Software Distribution commands, withsyntax and descriptions of their functions. You can access theselistings by using theman command on UNIX managed nodes or byusing the on-line help file provided for NT managed nodes.

2–8 Version 3.6

waddicon

Com

mands

5,st,e. If

am

re

se

is

t

NAME

waddicon

PURPOSE

Adds an icon to a Windows Program Manager group. (Windows,Windows 95, Windows NT only)

SYNOPSIS

waddicon –ggroup_name [–c “command_line”] [ –i icon_file][–t icon_title] [–r] [–m “message”] [ –a]

DESCRIPTION

Thewaddiconcommand adds a new icon to a Windows, Windows 9or Windows NT Program Manager group. If the group does not exiit is created. Ifwaddicon is launched as a batch from the NT servicagent, the created program group will be a common program groupwaddicon is launched from the NT console agent, the created progrgroup will be a user program group.

Note: Tivoli recommends that PC agents be run as NT serviceagents, not as console agents.

Arguments

–a Enables you to use this command asynchronously,such as in a batch file that is distributed to a PC whea user is not logged in. The command is actuallyexecuted when a user logs into the PC. You must uthe command in a batch file if you specify thisargument. This argument is supported on WindowsNT only.

–c “command_line”Specifies the command line invoked by the icon.

–g group_nameSpecifies the program group name to which the iconadded.

–i icon_file Specifies the file containing the icon. If this argumenis not specified, the Program Manager looks in theexecutable file specified by the -c argument.


waddicon

led

o

–m “message” Specifies a message to be written to theWADDICON.ERR file if an error occurs when usingthis command with the-a argument. TheWADDICON.ERR file is created in the currentworking directory of the PC agent. This argument issupported on Windows NT only.

–r Removes the specified icon. If no icon is specified,attempts to remove the entire program group.

–t icon_title Specifies the title (description) below the icon in theProgram Manager.

RETURNS

waddicon returns one of the following:

0 Indicates the successful addition of the icon.

non-zero Indicates thatwaddicon was unsuccessful at addingthe icon.

EXAMPLES

The following command example adds an icon calledWord Processorfor the word processor application to a Program Manager group calApplications.

waddicon -g “Applications” -c \WP\WPROCESS.EXE \-t “Word Processor”

To remove theWord Processor icon from theApplications group,enter the following command:

waddicon -g “Applications” -c \WP\WPROCESS.EXE \-t “Word Processor” -r

To remove theApplications group, enter the following command:

waddicon -g “Applications” -r

To add an icon to a user’s desktop (on a Windows NT machine),include the following command in a batch file and distribute the file t

2–10 Version 3.6

waddicon

Com

mands

the user’s PC. If an error occurs, the message following the-margument is written to theWADDICON.ERR file.

C:\TIVOLI\TMEAGENT\WIN32\CLI\WADDICON \-c “C:\FILES\MY_PROG.EXE” -t “My Program” \-m “Call #1 of waddicon” -a


waddpath

ent

to

n

NAME

waddpath

PURPOSE

Adds an entry to the path statement in the registry hive of the currcontrol set. (Windows NT only)

SYNOPSIS

waddpath path_value

DESCRIPTION

Thewaddpath command adds an entry to Windows NT\System\CurrentControlSet\control\SessionManager\Environ-ment key path in theHKEY_LOCAL_MACHINE registry hive.Once you add the entry, other applications will have a search paththe application.

This command returns a message indicating if it successfullycompleted or encountered an error.

Authorization

administrator

Arguments

path_value Specifies the path entry to add to the registry hive ithe current control set.

EXAMPLE

To add the\APPS\MISC\EXEC directory path to the registry hive,enter the following command:

waddpath \APPS\MISC\EXEC

2–12 Version 3.6

wclrblk

Com

mands

is

ed

sd

ute

f

sd

NAME

wclrblk

PURPOSE

Removes a block of statements from a file. (All supported PCplatforms)

SYNOPSIS

wclrblk [–r] –s “start_string” –e “ end_string” [–o output_file]filename

DESCRIPTION

Thewclrblk command removes a block of commands from a file. Thcommand is intended to remove a block of commands clearlydelimited at the beginning and end of blocks (such as a block addusingwinsblk or wrplblk ). The caller must insert the delimiting linesalong with the actual block of statements.

Arguments

–e “end_string”Specifies a string to search for in the file that signifiethe end of the block of statements. You must surrounthe string with double quotation marks.

–o output_file Specifies the name of the file that will receive theprocessed file. If this parameter is not specified, outpis written to standard output. You cannot redirect thprocessed file to the file that you are modifying.

–r Removes the delimiter lines in addition to the block ostatements.

–s “start_string”Specifies a string to search for in the file that signifiethe start of the block of statements. You must surrounthe string with double quotation marks.

filename Specifies the file from which the block should beremoved.


wclrblk

RETURNS

wclrblk returns one of the following:

0 Indicates thatwclrblk successfully removed thespecified block of statements.

non-zero Indicates thatwclrblk did not successfully remove thespecified block of statements.

EXAMPLE

To remove delimiter lines and the block of statements starting with[keyboard] and ending withtype=4from theSYSTEM.INI file, enterthe following command:

wclrblk -r -s “[keyboard]” -e “type=4” \-o C:\TEMP\OUTPUT.FIL C:\WINDOWS\SYSTEM.INI

The output is written to theOUTPUT.FIL file, as specified by the-oargument.

SEE ALSO

winsblk, wrplblk

2–14 Version 3.6

wclrline

Com

mands

y to

ut

h

NAME

wclrline

PURPOSE

Removes a single line from a file. (All supported PC platforms)

SYNOPSIS

wclrline [–f] –s “search_string” [–o output_file] filename

DESCRIPTION

Thewclrline command removes a line from a text file, as specified bthe search string. By default, output from this command is writtenstandard output.

Arguments

–f Processes only the first occurrence of the searchstring. If this argument is not specified, all linescontaining the search string are removed.

–o output_file Specifies the name of the file that will receive theprocessed file. If this parameter is not specified, outpis written to standard output.

–s “search_string”Specifies a string to search for in the file. If the searcstring is contained in a line, the line is removed fromthe file. You must surround the string with doublequotation marks.

filename Specifies the name of the file from which to read.

RETURNS

wclrline returns one of the following:

0 Indicates thatwclrline successfully removed thespecified line.

non-zero Indicates thatwclrline did not successfully removethe specified line.


wclrline

EXAMPLES

To remove the first occurrence of a line starting with[boot] from theSYSTEM.INI file, enter the following command:

wclrline -f -s “[boot]” -o C:\TEMP\OUTPUT.FIL \C:\WINDOWS\SYSTEM.INI

To remove all lines that havedevice= in them from theMYAPP.INIfile, enter:

wclrline -s “device=” -o C:\TEMP\OUTPUT.FIL \C:\WINDOWS\MYAPP.INI

Both example commands write their output to theOUTPUT.FIL file.

SEE ALSO

winsline, wrplline

2–16 Version 3.6

wcpfpblock

Com

mands

he

to a

lee

l

NAME

wcpfpblock

PURPOSE

Copies a file package block from an existing file package block to tspecified targets.

SYNOPSIS

wcpfpblock [managed_node:]fpblock_path new_fpblock_pathtarget [target ...]

DESCRIPTION

Thewcpfpblock command copies the file package blockfpblock_pathlocated on the specified managed node or the local managed nodefile specified bynew_fpblock_path on the specified targets. A targetmust be a valid managed node.

Authorization

senior or super

Arguments

managed_node:Specifies the managed node on which the original fipackage block resides. If this argument is omitted, thcommand assumes that the file resides on the locamanaged node.

fpblock_path Specifies the path to the file package block.

new_fpblock_pathSpecifies the path to the new file package block.

target Specifies a managed node to which to copy the newfile package block.


wcpfpblock

ged

Return Codes

Thewcpfpblock command returns the following codes to standardoutput:

0 Successful completion.

1 The commands failed due to an error.

EXAMPLES

To copy a file package block from the current system to the mananodegrapevine, use the following command:

wcpfpblock /tmp/example_fp.fpblock \/tmp/example_fp.fpblock @grapevine

To copy a file package from the managed nodegrapevine to themanaged nodecastle, use the following command:

wcpfpblock @grapevine:/tmp/example_fp.fpblock \/tmp/example_fp.fpblock @castle

SEE ALSO

wcrtfpblock , wdistfpblock, wrmfpblock

2–18 Version 3.6

wcpyfile

Com

mands

ly)

nton

in

NAME

wcpyfile

PURPOSE

Enables an .NCF configuration program to copy a file. (NetWare on

SYNOPSIS

wcpyfile –ssrc_path–d dest_path

DESCRIPTION

Thewcpyfile command was created in support of .NCF configuratioprograms. It enables you to copy files from one volume or directoryanother on the NetWare machine from within an .NCF configuratioprogram.

Arguments

–d dest_path Specifies the full path to the destination file.

–s src_path Specifies the full path to the source file.

EXAMPLE

From an .NCF configuration program, enter the following commandthe program to copy theSYS:\TEMP\FILE.NLM file to theSYS:\SYSTEM\FILE.NLM file:

wcpyfile -s SYS:\TEMP\FILE.NLM -d SYS:\SYSTEM\FILE.NLM


wcrtfpblock

on

.

s

s

le

to

NAME

wcrtfpblock

PURPOSE

Creates a file package block from an existing file package definitionthe specified target(s).

SYNOPSIS

wcrtfpblock {–a | –s} fp_name fpblock_path target [target ...]

DESCRIPTION

Thewcrtfpblock command creates a file package block for thespecified file package and writes it to a file on the specified targetsTargets must be valid managed nodes.

Authorization

admin, senior, or super

Arguments

–a Creates a file package block file that contains all filein the file package definition.

–s Creates a file package block that contains only fileshaving a modification time on the source host that ilater than the last successful distribution.

fp_name Specifies the object path or registered name of the fipackage for which a file package block is created.

fpblock_path Specifies the name of the file to which to write the filepackage block.

target Specifies the name of the managed node to which write the file package block.

2–20 Version 3.6

wcrtfpblock

Com

mands

Return Codes

Thewcrtfpblock command returns the following codes to standardoutput:



EXAMPLES

To create a file package block (of all files in theexample_fp filepackage) on the managed nodesgrapevine andcastle, enter:

wcrtfpblock -a @example_fp /tmp/example_fp.fpblock \@grapevine @castle

SEE ALSO

wcpfpblock, wdistfpblock, wrmfpblock


wdistfp

set

ers.ls.

le

e

ut.

NAME

wdistfp

PURPOSE

Distributes, commits, or previews a file package to a subscriber or aof subscribers.

SYNOPSIS

wdistfp { –a | –n | –s} [ –u] { –b | –c | –d | –p} fp_name[subscriber...]

DESCRIPTION

This command distributes the file package to the specified subscribIf no subscribers are specified, the file package is distributed to alsubscribers of the profile manager in which the file package resideThewdistfp command also enables you to commit and preview a fipackage.

Authorization


Arguments

–a Distributes all files in the file package.

–b Performs distribute and commit operations on thespecified subscribers (combines the-d and-carguments).

–c Performs a commit operation on the specifiedsubscribers.

–d Performs a distribute operation to the specifiedsubscribers.

–n Distributes modified files (changes in modificationtime, size, permissions, and so on) in the file packagfrom the source managed node to the target.

–p Specifies a preview operation only. A list of the files tobe sent to each subscriber is sent to standard outpWhen previewing a distribution, there are severalthings to consider:

2–22 Version 3.6

wdistfp

Com

mands

:

ile

dot

n

The output in this area will be similar to the following

Unix target directory prefix: /tmp/unixNetWare target directory prefix: SYS:/NETWAREWindows target directory prefix: D:/WINDOWS-------100644 1 0/ 3 403 Feb 28 15:13:59 1996/tmp/default_dest/data.db

Thus, this destination of thedata.db file at the UNIXtarget will be/tmp/unix/tmp/default_dest/data.db;at the NetWare target,SYS:/NETWARE/tmp/default_dest/data.db; and atthe Windows target,D:/WINDOWS/tmp/default_dest/data.db. The fileis distributed to /platform_prefix_dir/default_dest_dirdirectory (as specified by thexxx_platform_prefixanddefault_dest keywords).

You cannot preview files or directories thatwill beincluded in the file package as a result of aconfiguration program. The preview operation doesnot execute these programs. If the contents of the fpackage depend on an operation in a configurationprogram, the preview operation will not accuratelydisplay the contents of the file package.

For example, suppose you specify a before programthat will mount a CD-ROM on which a file (to bedistributed) resides, as follows:

#!/bin/shmount /dev/cdrom /srcexit 0

The files on the mounted file system are not displayeduring a preview operation because this program is nexecuted.

–s Distributes all files in the file package on the sourcemanaged node that have a modification time later thathe time of the last successful distribution.

–u Includes the file package size in the informationdistributed with the file package. This information is


wdistfp

es

le

er

er

d

ile

edfile

s

used by the TME 10 UserLink daemon to display aprogress bar on the subscriber when the user retrieva file package.

fp_name Specifies an object path or registered name of the fipackage.

subscriber Specifies an object path or registered name for amanaged node, PC managed node, or profile managon which to perform the specified operation. Thesubscriber must be subscribed to the profile managin which the file package resides (unless thelenient_distribution attribute is set using thewsetfpattr command).

Return Codes

Thewdistfp command exits with the following codes:

0 Successful distribution.

1 An error occurred (due to an exception from a methocalled during the distribution operation).

2 The distribution failed.

EXAMPLES

To distribute all files in the file package to the subscribers of the profmanager in which the file package resides, enter:

wdistfp -a -d @example_fp

To distribute and commit all files in the file package that have changon the source host since the last successful distribute to one of thepackage’s subscribers (castle), enter:

wdistfp -s -b @example_fp @castle

To commit the file package on two of the file package’s subscriber(castle andgrapevine), enter:

wdistfp -a -c @example_fp @castle @grapevine

2–24 Version 3.6

wdistfp

Com

mands

e
To preview the distribution of files that show any changes to two of thfile package’s subscribers (castle andgrapevine), enter:
wdistfp -n -p @example_fp @castle @grapevine

SEE ALSO

wrmfp


wdistfpblock

.

on,

NAME

wdistfpblock

PURPOSE

Distributes the files in a file package block to the specified targets

SYNOPSIS

wdistfpblock [–o keyword=override_arg]... [managed_node:]fpblock_path target [target ...]

DESCRIPTION

Thewdistfpblock command distributes the files in a file packageblock to the specified targets. The file package options, files, and soare contained in the file package block file. You can also optionallyoverride some of the file package keywords. See Chapter 1, “FilePackage Definitions” for descriptions and valid values of the filepackage keywords.

Authorization

senior or super

Arguments

–o keyword=override_argChanges the value of the specified keyword to thevalue specified byoverride_arg. You can override thefollowing keywords:

append_log

log_file

preproc

backup_fmt

log_host

prog_env

create_dirs

mail_id

2–26 Version 3.6

wdistfpblock

Com

mands

e

.

ris

n

et:

ris

ge

skip_older_src

install_progs

no_overwrite

stop_on_error

list_path

post_notice

In addition, you can override the platform-specifickeywords except for those that specify files that residon the source host (such assrc_after_input_path andos2_before_prog_from_src).

See Chapter 1, “File Package Definitions” for thevalues that you can set for each of these keywords

The keywords that you can override are processedwhen the fpblock is removed from the target. All othekeywords are processed when the file package blockcreated; overrides for them will have no effect.You caoverride the following keywords for directories to bedistributed if the directory does not exist at the targ

default_dir_mode

unix_default_file_uid

unix_default_file_gid

The keywords that you can override are processedwhen the fpblock is unpacked on the target. All othekeywords are processed when the file package blockcreated; overrides for them will have no effect.

managed_nodeSpecifies the managed node on which the file packablock resides.

fpblock_path Specifies the path to the file package block file.

target Specifies the name of the managed nodes, PCmanaged nodes, and profile managers to which todistribute the file package block file.


wdistfpblock

d

ed

ode

e

Return Codes

Thewdistfpblock command returns the following codes to standaroutput:



EXAMPLES

To distribute a file package block file that exists on the local managnode to a specific managed node (castle), enter:

wdistfpblock /tmp/example_fp.fpblock @castle

To distribute a file package block that exists on another managed n(grape), but override thelog_hostkeyword option (so that the log fileis written to the managed node grape instead of the managed nodspecified within the file package itself), enter:

wdistfpblock –o log_host=grape \@grape:/tmp/example_fp.fpblock @castle

SEE ALSO

wcpfpblock, wcrtfpblock , wrmfpblock

2–28 Version 3.6

wdskspc

Com

mands

nd

e

ace

NAME

wdskspc

PURPOSE

Verifies the amount of disk space available. (Windows platforms aNetWare)

SYNOPSIS

wdskspc[–s required_size] filename

DESCRIPTION

Thewdskspcreturns the amount of available disk space on the volumwherefilename resides. If you specify the-s argument, the commandsets the return code of the command to zero if the required disk spis available and non-zero if not available.

Arguments

–s required_sizeSpecifies the amount of disk space required. Therequired_sizeargument can have any of the followingsuffixes:

k: kilobytesm: megabytesg: gigabytes

If you omit this argument,wdskspc returns theamount of available disk space.

filename Returns the amount of available disk space on thevolume or disk where the specified directory or filename resides.

EXAMPLES

To check theC drive for 10 MB of available disk space, enter:

wdskspc -s 10m C:\

To check the total disk space available on the C drive, enter:


wdskspc

wdskspc C:\

To check theSYSvolume for 20 MB of available disk space on aNetWare machine, enter:

wdskspc -s 20m SYS:

2–30 Version 3.6

weditini

Com

mands

d

,

oted.

e.

e

NAME

weditini

PURPOSE

Modifies the groups, variables, and values in a .INI file. (All supportePC platforms)

SYNOPSIS

weditini [–r] –gsection_name[–n variable_name] –v value] filename

DESCRIPTION

Theweditini command edits the contents of a .INI file. Using thiscommand, you can add a variable and value to a section of the fileremove a variable or section, or replace the value of a specifiedvariable.

Arguments

–g section_nameSpecifies the name of the section in the .INI file toprocess. If you add a variable to a section that does nexist, the section is created and the variable is add

–n variable_nameSpecifies the variable name to add, replace, or remov

–r Removes the specified section or variable.

–v value Specifies the value to add or replace for the variablspecified by the–n argument.

filename Specifies the full path of the file to edit.

RETURNS

weditini returns one of the following:

0 Indicates thatweditini successfully edited the .INIfile.

non-zero Indicates thatweditini did not successfully edit the.INI file.


weditini

EXAMPLES

To add theDefaultDirectory variable to theUserSettings section intheC:\WINDOWS\SYSTEM.INI file and set its value toC:\WORK ,enter:

weditini –g UserSettings –n DefaultDirectory –v C:\WORK \C:\WINDOWS\SYSTEM.INI

To remove the groupUserSettings from theC:\WINDOWS\SYSTEM.INI file, enter:

weditini –r –g UserSettings C:\WINDOWS\SYSTEM.INI

SEE ALSO

wmrgini

2–32 Version 3.6

wexprtfp

Com

mands

rd

ust

f

le.

NAME

wexprtfp

PURPOSE

Exports a file package definition.

SYNOPSIS

wexprtfp [[–a] –f [managed_node:] filename] [–c] fp_name

DESCRIPTION

Thewexprtfp command exports the file package definition to standaoutput or, optionally, to the specified file if you use the-f argument.

If you import a partial file package definition (a file containing only aheader, the section delimiters, and the keywords to be set), you muse the-c argument when exporting the file package to export allkeywords. If you do not specify this argument, only the partial filepackage definition is exported.

Authorization

user, admin, senior, or super

Arguments

–a Overwrites the file being exported, if it exists.

–c Exports a complete file package definition, not justthose imported into the file package from a partial filepackage definition.

–f [managed_node:] filenameWrites the file package definition to the file specifiedby [managed_node:] filename, instead of standardoutput. Thefilename argument must be an absolutepath. If the file exists and you do not specify the–aargument, Software Distribution returns an error. Ocourse, the file need not exist; Software Distributionwill create it.

fp_name Specifies an object path or registered name of the fipackage whose definition is output by this operation


wexprtfp

Return Codes

Thewexprtfp command returns the following codes to standardoutput:



EXAMPLES

To export the file package definition to standard output, enter:

wexprtfp @example_fp

To export the file package definition to the/tmp/fp_desc.asciifile onthe managed nodecastle, where that file already exists, enter:

wexprtfp -a -f @castle:/tmp/fp_desc.ascii @example_fp

SEE ALSO

wimprtfp

2–34 Version 3.6

wgetfpattr

Com

mands

NAME

wgetfpattr

PURPOSE

Gets the attributes for a file package.

SYNOPSIS

wgetfpattr {–b | –d | –h | –I | –l | –m | –n | –p | –s | –S | –t | –w}fp_name

DESCRIPTION

Thewgetfpattr command gets the attributes for a file package. Allarguments to the command are mutually exclusive.

Authorization

user, admin, senior, or super

Arguments

–b Gets thebehavior_flags attribute. Possible valuesinclude:

rm_host Moves the file package to thelost-n-found directory if the filepackage’s log host or source host isremoved.

rm_fp Moves the file package to thelost-n-found directory if any of its nestedfile packages are removed.

program_inputSets thexxx_program_input_from_srckeywords to the same value as thexxx_program_prog_from_src keywordsif the xxx_program_prog_from_srckeywords are changed in the GUI.

rm_no_chkDoes not check to determine if a removed


wgetfpattr

s

2

st

e

file package was nested in the filepackage.

nm_chg_no_chkIf the file package name is changed, doenotcheck this file package to determine ifit is nested. If this value is set, other filepackages are checked, and if this filepackage is nested, the reference ischanged to the new file package name.

–d value Sets thedestination_flags attribute. SoftwareDistribution checks this flag when you save a filepackage or import a file package definition from thedesktop, or when you use thewimprtfp , wsetfpopts,or wsetfpcontents command. Possible values:

nt Ensures that a destination is set forWindows NT platforms.

nw Ensure that a destination is set forNetWare platforms.

os2 Ensures that a destination is set for OS/platforms.

unix Ensures that a destination is set for UNIXplatforms.

win Ensures that a destination is set forWindows platforms.

win95 Ensures that a destination is set forWindows 95 platforms.

any Ensures that a destination is set for at leaone platform type.

none Does not check destinations.

If the destination_flags attribute is set for any ofthese, you must set the destination directory for thecorresponding platform when setting the file packagproperties.

2–36 Version 3.6

wgetfpattr

Com

mands

to

a

–h Gets thesrc_host attribute. This is the objectreference of the managed node (UNIX or WindowsNT) that is the source host for the file package. If asource host is not defined for this file package, thevalue of this attribute isOBJECT_NIL .

–I Gets thefp_info attribute, which stores any optionalinformation about the file package. Set optionalinformation using theEdit Optional Informationdialog from theEdit menu of theFile PackageProperties window.

–l Gets thelenient_distribution attribute. Possiblevalues:

TRUE Allows distributions and removals fromthe CLI to any managed node or profilemanager, even if that managed node orprofile manager is not currently asubscriber of the file package’s profilemanager (or any of its subscribing profilemanagers).

FALSE Allows distributions and removals fromthe CLI only to managed nodes or profilemanagers that are currently subscribersthe file package’s profile manager (or anyof its subscribing profile managers). Thisis the default value.

–m Gets thedefault_push_modeattribute. This attributespecifies the mode of distribution that will beperformed for a default distribution. A defaultdistribution is performed when you selectDistribute... from the profile manager icon or theprofile manager menu, or when you drag and drop file package icon onto a subscriber icon.

all Distributes all files.

src Distributes only files that have changed onthe source managed node since the lastsuccessful distribution.


wgetfpattr

s

d

r

e

a

any Distributes files that have changed oneither the source or the target.

–n Gets thecheck_nested attribute. Values are:

TRUE Checks to see if the file package containcircular nested file package references.

FALSE Does not check for circular nested filepackage references.

–p Gets thepush_time attribute. This attribute containsthe time of the last successful distribute, distribute ancommit, or commit operation (in seconds since00:00:00 UTC, January 1, 1970).

–s Gets thecheck_no_src_host attribute. Values are:

TRUE Ensures that a source host is specified foany file package properties set operation(for examples using the GUI,wsetfpcontents, orwimprtfp ) where filesor directories are specified (that is, if thefile package does not contain just nestedfile packages).

FALSE Does not ensure that a source host wasspecified during file package propertiesset operations.

–S Gets thefp_sizeattribute, which stores the size of thefile package (in bytes). This size includes files,directories, and nested file packages included in thfile package. Calculate the size of a file package byselectingCalculate Size...the file package icon menuin the Profile Manager window.

–t Gets thedefault_push_type attribute. This attributespecifies the type of distribution that will beperformed for a default distribution. A defaultdistribution is performed when you selectDistribute... from the profile manager icon or theprofile manager menu, or when you drag and drop file package icon onto a subscriber. Values are:

2–38 Version 3.6

wgetfpattr

Com

mands

eote

len.

e

file

dist Performs a distribute operation.

commit Performs a commit operation.

both Performs both a distribute and commitoperation.

–w staging_areaGets thestage_areaattribute. This attribute specifiesthe full path to a directory on the source host where thsnapshot of the file package will reside. This snapshis created when you distribute a file package using thDistribute entries with ANY changes option.

fp_name Specifies an object path or registered name of the fipackage whose attributes are output by this operatio

Return Codes

Thewgetfpattr command returns the following codes to standardoutput:



EXAMPLES

To determine whether this file package may be distributed from thcommand line to any managed node, enter:

wgetfpattr –l @example_fp

To determine whether the source host must be specified before anylists can be specified, enter:

wgetfpattr –s @example_fp

SEE ALSO

wsetfpattr


wgetkey

is

NAME

wgetkey

PURPOSE

Retrieves the subkey listing in a registry hive. (Windows 95 andWindows NT only)

SYNOPSIS

wgetkeyregistry_key_path[registry_hive]

DESCRIPTION

Thewgetkeycommand retrieves the subkeys associated with thespecified key path from the specified registry hive. The output of thcommand is returned to standard output (on the console).

Authorization

administrator

Arguments

registry_key_pathSpecifies a registry key name from which to retrievethe subkeys.

registry_hive Specifies the registry hive from which to retrieve thesubkeys. Valid hives are:

HKEY_LOCAL_MACHINE

HKEY_CLASSES_ROOT

HKEY_CURRENT_USER

HKEY_USERS

If you do not specify this argument, the commandretrieves the subkeys fromHKEY_LOCAL_MACHINE registry hive.

2–40 Version 3.6

wgetkey

Com

mands

EXAMPLES

To retrieve the subkeys from theHKEY_LOCAL_MACHINEregistry hive under theSOFTWARE key path, enter the followingcommand. This command outputs a list of subkeys.

wgetkey SOFTWARE

To retrieve the key values from theHKEY_CURRENT_USERregistry hive under theUSERSkey path, enter the followingcommand:

wgetkey USERS HKEY_CURRENT_USER


wgetval

NAME

wgetval

PURPOSE

Retrieves a registry subkey. (Windows 95 and Windows NT only)

SYNOPSIS

wgetval [–h registry_hive] –k { key | @filename} –n value_name

DESCRIPTION

Thewgetval retrieves a subkey from a registry. The output of thiscommand is returned to standard output.

Authorization

administrator

Arguments

–h registry_hiveSpecifies the registry hive from which to retrieve thesubkey. Valid values are:

HKEY_LOCAL_MACHINE (default)

HKEY_CURRENT_USER

HKEY_CLASSES_ROOT

HKEY_USERS

–k key | @filenameSpecifies the key or file from which the subkey isretrieved.

–n value_nameSpecifies the name of the value.

EXAMPLE

To retrieve the version number of the Novell drivers, enter thefollowing command:

wgetval -h HKEY_LOCAL_MACHINE -k SOFTWARE\NOVELL \-n CurrentVersion

2–42 Version 3.6

wgetval

Com

mands

SEE ALSO

wsetval


wimprtfp

e

d

ge

le

NAME

wimprtfp

PURPOSE

Imports a file package definition.

SYNOPSIS

wimprtfp [–f [managed_node:] filename] [–h src_host] fp_name

DESCRIPTION

Thewimprtfp command imports the file package definition fromstandard input, or, optionally, from the specified file if you use the–fargument.

Authorization


Arguments

–f [managed_node:] filenameObtains the source for file package definition from thfile specified by [managed_node:] filename, ratherthan from standard input. You must specify theabsolute path of a file on the local or remote managenode.

–h src_host Sets the source host, where the files in the file packaare obtained, to the host specified bysrc_host.

fp_name Specifies an object path or registered name of the fipackage whose definition is set by this operation.

Return Codes

Thewimprtfp command returns the following codes to standardoutput:



2–44 Version 3.6

wimprtfp

Com

mands

ter:

)

EXAMPLES

To import a file package definition on the local managed node, en

wimprtfp -f /tmp/fp_desc.ascii @example_fp

To import the same file package definition (through standard inputand set the source host tocrumpet, enter:

wimprtfp -h @crumpet @example_fp < /tmp/fp_desc.ascii

SEE ALSO

wexprtfp


winsblk

s)

s

ged

ged

NAME

winsblk

PURPOSE

Inserts a block of statements into a file. (All supported PC platform

SYNOPSIS

winsblk –s “search_string” {–a “insertion_string” | @filename} |{ –b “insertion_string” | @filename} [ –o output_file] filename

DESCRIPTION

Thewinsblk command inserts a block of statements into a file. Thicommand enables you to add a block of statements delimited byunique strings, which you can later search for or remove using thewrplblk or wclrblk commands.

Arguments

–a “insertion_string” | @filenameInserts a block of statements after the line containinthe search string. This parameter cannot be specifiwith the–b argument.

If you specifyinsertion_string, you must surround thestring with double quotation marks. If you specify@filename, this command inserts the block ofstatements from the specified file.

–b “ insertion_string” | @filenameInserts a block of statements before the line containinthe search string. This parameter cannot be specifiwith the–a argument.

If you specifyinsertion_string, you must surround thestring with double quotation marks. If you specify@filename, this command inserts the block ofstatements from the specified file.

–o output_file Writes that output to the file specified byoutput_file.If this parameter is not specified, output is written tostandard output.

2–46 Version 3.6

winsblk

Com

mands

d

.

–s “search_string”Specifies a search string. If the search string iscontained in a line, the block of statements is placeeither before (using the–b argument) or after (usingthe–aargument) the line containing the search stringIf this argument is not specified, the block ofstatements is appended to the file.

filename Specifies the input file.

RETURNS

winsblk returns one of the following:

0 Indicates thatwinsblk successfully added thespecified block of statements.

non-zero Indicates thatwinsblk did not successfully add thespecified block of statements.

EXAMPLE

To insert the statements in theBLKSTMTS.FIL file after everyoccurrence of thedevice=string in theSYSTEM.INI file and redirectoutput to theOUTPUT.FIL file, enter the following command:

winsblk -s “device=” -a @C:\TEMP\BLKSTMTS.FIL \-o C:\TEMP\OUTPUT.FIL C:\WINDOWS\SYSTEM.INI

SEE ALSO

wrplblk , wclrblk


winsline

e

e

eh

d

r

NAME

winsline

PURPOSE

Inserts a single line into a file. (All supported PC platforms)

SYNOPSIS

winsline [–f] –s “search_string” {–a “insertion_string” |–b “ insertion_string” } [ –o output_file] filename

DESCRIPTION

Thewinsline command adds a line to a text file. You can insert the linbefore or after a line that contains the search string.

Arguments

–a “insertion_string”Inserts the specified string or the lines contained in thspecified file after the line that contained the searchstring. This parameter cannot be specified with the–bargument. You must surround the string with doublequotation marks.

–b “ insertion_string”Inserts the specified string or the lines contained in thspecified file before the line that contained the searcstring. This parameter cannot be specified with the–aargument. You must surround the string with doublequotation marks.

–f Processes only the first occurrence of the searchstring. If this argument is not specified, the commanprocesses each occurrence of the search string.

–o output_file Specifies that output will be written to a fileoutput_file. If this parameter is not specified, output iswritten to standard output.

–s “search_string”Specifies the search string. If the search string iscontained in a line, the insertion string is placed eithe

2–48 Version 3.6

winsline

Com

mands

s.

to

before (using the–b argument) or after (using the–aargument) the line containing the search string. Youmust surround the string with double quotation mark

filename Specifies the name of the input file.

RETURNS

winsline returns one of the following:

0 Indicates thatwinsline successfully added thespecified line.

non-zero Indicates thatwinsline did not successfully add thespecified line.

EXAMPLES

To insertlp01 after the first occurrence of the device= string in theSYSTEM.INI file and redirect output to theOUTPUT.FIL file, enterthe following command:

winsline -f -s “device=” -a “lp01” -o C:\TEMP\OUTPUT.FIL \C:\WINDOWS\SYSTEM.INI

To insertdev01 before every occurrence of thetype= string in theSYSTEM.INI file, enter:

winsline -s “type=” -b dev01 -o C:\TEMP\OUTPUT.FIL \C:\WINDOWS\SYSTEM.INI

The output from this command is redirected from standard outputthe fileOUTPUT.FIL .

SEE ALSO

wrplline , wclrline


winstruct_file

n

efor

ch

forandted.

NAME

winstruct_file

PURPOSE

Creates a TME 10 Software Distribution file package from informatiospecified in an Application Management Package (AMP).

SYNOPSIS

winstruct_file –a amp_file–sstaging_area [–t admin_tag][–D variable=value] ...

DESCRIPTION

Thewinstruct_file command, a subcommand ofwinstruct , extractsthe contents of the application management package file (.amp) into aspecified staging area. The subcommand reads the files (.aof, .gdf, andone or more.cdf) that are included in an Application ManagementPackage (AMP) file. If necessary,winstruct_file creates the CCMSinfrastructure that contains the policy region for the application. Thsubcommand also creates a profile manager and file package profileeach component containing a list of files to distribute.

Thewinstruct_file subcommand ignores a repeated instruction, whipermits the instruction process to continue for the remaininguninstructed tools. For example, suppose you execute thewinstructcommand set for an application, but the process does not completesome reason. When you correct the problem and issue the commagain, the instruction process continues from the point where it hal

You can execute this command directly—winstruct_file can beinvoked independently of the otherwinstruct subcommands—or youcan execute thewinstruct command to invokewinstruct_file . See theTME 10 Framework Reference Manual for additional informationaboutwinstruct commands.

Authorization

senior or super

2–50 Version 3.6

winstruct_file

Com

mands

.

ne

gheed

ol

oryo ame

Arguments

–a amp_file Specifies the path and file name of an AMP.

–sstaging_areaSpecifies a directory into which thewinstruct_filecommand extracts the contents of the AMP.

–t admin_tag Specifies an administrator tag for the instruct actionUnique administrator tags enable the instructing ofmultiple versions of an AMP.

–D variable=valueSpecifies the name of a Management Tool Extensiogroup variable and its value. You can specify multiplvariables, but you must enter–D for each variable andvalue pair.

EXAMPLE

To instruct TME 10 Software Distribution with information formanaging an application, enter all on one line:

winstruct_file -a /applications/amps/super_app.amp-s /install/staging -t rev1 -D comp_src_dir1=cdrom1-D comp_src_dir2=/src/app/comp_files

This command extracts the contents of thesuper_app AMP into the/install/stagingdirectory and reads the.aof, .gdf, and.cdf descriptionfiles. The instruction process is labeled with the “rev1” tag. The tadistinguishes this version of the AMP from others. In this example, tapplication files are not included in the AMP, but are instead locaton a CD-ROM disk, specified with the–D argument. For eachcomponent in the AMP, the command checks the Management ToExtension group (an AMS group) forvariable=value pairs andcommand line arguments. This data determines the source direct(or directories) for the application files. Each component can refer tdifferent–D argument, and different components can refer to the saargument. Enter as many–D arguments as required, using a new–Dfor each variable and value pair.

SEE ALSO

winstruct


wmrgini

r.

NAME

wmrgini

PURPOSE

Merges groups and variables from one .INI file into another. (Allsupported PC platforms)

SYNOPSIS

wmrgini dest_file merge_file

DESCRIPTION

Thewmrgini command merges the contents of one .INI file in anotheFor each variable inmerge_file, the command creates or replaces anidentical variable indest_file.

Arguments

dest_file Specifies the name of the destination file.

merge_file Specifies the name of the file to merge.

EXAMPLE

To merge theSYSTEM.INI file into theWIN.INI file, enter thefollowing:

wmrgini C:\TEMP\WIN.INI C:\TEMP\SYSTEM.INI

SEE ALSO

weditini

2–52 Version 3.6

wmvapobj

Com

mands

e

s

ck

NAME

wmvapobj

PURPOSE

Moves an AutoPack from thelost-n-found collection.

SYNOPSIS

wmvapobj ap_name[ap_name...] target_collection

DESCRIPTION

Thewmvapobj command moves the specified AutoPack(s) from thlost-n-found collection to the specified collection. An AutoPackresides in thelost-n-found collection if its source host was removedfrom the TME 10 environment. You can specify multiple AutoPackon the same command line.

Arguments

ap_name Specifies the AutoPack to be moved fromlost-n-found. You can specify more than oneAutoPack. Do not precede the name of the AutoPawith @.

target_collectionSpecifies the target collection. You can specify thename of a profile manager or policy region. Do notprecede the name of the collection with@.

EXAMPLE

To move theWord6 andPSP AutoPacks from thelost-n-foundcollection to theReady-to-distrib profile manager, enter the followingcommand:

wmvapobj Word6 PSP Ready-to-distrib


wmvfpobj

e

ify

ge

NAME

wmvfpobj

PURPOSE

Moves a file package from thelost-n-found collection.

SYNOPSIS

wmvfpobj fp_name[fp_name...] target_collection

DESCRIPTION

Thewmvfpobj command moves the specified file package(s) from thlost-n-found collection to the specified collection. A file packageresides in thelost-n-found collection if its source host or parent filepackage was removed from the TME 10 environment. You can specmultiple file packages on the same command line.

Arguments

ap_name Specifies the file package to be moved fromlost-n-found. You can specify more than one filepackage. Do not precede the name of the file packawith @.

target_collectionSpecifies the target collection. You can specify thename of a profile manager or policy region. Do notprecede the name of the collection with@.

EXAMPLE

To move theFrame4 file package from thelost-n-found collection totheMarketing profile manager, enter the following command:

wmvfpobj Frame4 Marketing

2–54 Version 3.6

wrestart

Com

mands

e

its

ter

NAME

wrestart

PURPOSE

Initiates a system restart and optional reboot. (Windows NT only)

SYNOPSIS

wrestart [–c] [–b] [–t timeout_value] [–m “confirm_message” ]

DESCRIPTION

Thewrestart command initiates an operating system restart andoptional machine reboot.

Arguments

–c Prompts the user for confirmation before restarting thsystem or rebooting.

–b Reboots the system after shutdown.

–m “confirm_message”Specifies the confirmation message that will bedisplayed.

–t timeout_valueSpecifies the number of seconds this command wafor user confirmation before initiating a restart.

EXAMPLES

To prompt the user for confirmation before restarting the system, enthe following command:

wrestart -c

To display a warning message before restarting the system in 60seconds, enter:

wrestart -m “WARNING: The system will reboot in 60 \seconds!!” -t 60


wrmfp

et

vede

esrride

n

the

t

lyd

NAME

wrmfp

PURPOSE

Removes the files in a file package definition from a subscriber or sof subscribers.

SYNOPSIS

wrmfp [–d | –r] fp_name [subscriber...]

DESCRIPTION

Removes the file package from the specified subscriber or set ofsubscribers. If no subscribers are specified, the file package is remofrom all subscribers of the profile manager in which the file packagresides.

The–d and–r arguments specify whether to remove empty directoriat the target managed node. You can use these arguments to ovethe current value for theRemove Empty Directories option (therm_empty_dirs keyword) in the file package definition. If neither ofthese arguments is specified, the command performs the operatiospecified by theRemove Empty Directoriesoption in the file packagedefinition. Note that the–d and–r arguments only override therm_empty_dirs keyword in the parent file package. Removing thedirectories for nested file packages is always based on the value ofrm_empty_dirs keyword in that nested file package.

Authorization


Arguments

–d Does not remove the empty directories that are notexplicitly specified in the file package from the targemanaged node.

–r Removes the empty directories that are not explicitspecified in the file package from the target managenode. Empty directories are deleted up to, but not

2–56 Version 3.6

wrmfp

Com

mands

le

er

er

d

rs,

ers

including, the/xxx_platform_prefix/default_dirdirectory

fp_name Specifies an object path or registered name of the fipackage.

subscriber Specifies an object path or registered name for amanaged node, PC managed node, or profile managon which to perform the specified operation. Thesubscriber must be subscribed to the profile managin which the file package resides (unless thelenient_distribution attribute is set using thewsetfpattr command).

Return Codes

Thewrmfp command exits with the following codes:

0 Successful removal.

1 An error occurred (due to an exception from a methocalled during the removal).

2 The removal failed.

EXAMPLES

To remove the file package from all of the file package’s subscribeenter the following command:

wrmfp @example_fp

To remove the file package from one of the file package’s subscrib(castle), and to force the removal of any empty directories notexplicitly specified in the file package, enter:

wrmfp -r @example_fp @castle


wrmfpblock

ck.

sor 1,e

u

NAME

wrmfpblock

PURPOSE

Removes the files and directories distributed from a file package blo

SYNOPSIS

wrmfpblock [–o keyword=override_arg]...[managed_node:]fpblock_path target ...

DESCRIPTION

Thewrmfpblock command removes the files and directories in thedistributed file package block from the specified targets. You can aloptionally override some of the file package keywords. See Chapte“File Package Definitions” for descriptions and valid values of the filpackage keywords.

Authorization

senior or super

Arguments

–o keyword=override_argSets the specified keyword to the specified value. Yocan override the following keywords:

append_log

log_file

preproc

backup_fmt

log_host

prog_env

create_dirs

mail_id

skip_older_src

install_progs

2–58 Version 3.6

wrmfpblock

Com

mands

e

.

ris

he

no_overwrite

stop_on_error

list_path

post_notice

In addition, you can override the platform-specifickeywords except for those that specify files that residon the source host (such assrc_after_input_path andos2_before_prog_from_src).

See Chapter 1, “File Package Definitions” for thevalues that you can set for each of these keywords

The keywords that you can override are processedwhen the fpblock is removed from the target. All othekeywords are processed when the file package blockcreated; overrides for them will have no effect.

[managed_node:] fpblock_pathSpecifies the name of the managed node on which tfile package block resides. You can specifymanaged_node: to specify the path to the file packageblock file from which the files and directories weredistributed.

target Specifies the name of the managed nodes, PCmanaged nodes, or profile managers from which toremove the distributed files and directories.

Return Codes

Thewrmfpblock command returns the following codes to standardoutput:




wrmfpblock

EXAMPLE

To remove the files in a file package block from the subscribergrape,enter the following command:

wrmfpblock –o log_host=grape /tmp/example_fp.fpblock \@castle

SEE ALSO

wcpfpblock, wcrtfpblock , wdistfpblock

2–60 Version 3.6

wrplblk

Com

mands

s)

srly

ded

eh

le

f

eh

NAME

wrplblk

PURPOSE

Replaces a block of statements in a file. (All supported PC platform

SYNOPSIS

wrplblk [–r] –s “start_string” –e “end_string” [–o output_file]{ –i “ replace_string” | @filename} filename

DESCRIPTION

Thewrplblk command replaces a block of commands in a file. Thicommand is intended to replace a block of commands that are cleadelimited at the beginning and end of the block (such as those adusing thewinsblk command.

Arguments

–e “end_string”Specifies a search string that signifies the end of thblock of statements. You must surround the string witdouble quotation marks.

–i { “ replace_string” | @filename}Specifies a string to replace the text in between thedelimited statements, or a file containing a block ofstatements. You must surround the string with doubquotation marks.

–o output_file Writes the output of this command to theoutput_filefile, instead of standard output.

–r Replaces the delimiter lines in addition to the block ostatements.

–s “start_string”Specifies a search string that signifies the start of thblock of statements. You must surround the string witdouble quotation marks.

filename Specifies the input file.


wrplblk

EXAMPLE

To replace a block of statements beginning with[boot] and endingwith end in theSYSTEM.INI file with statements in theRPLBLK.FIL file, enter the following command:

wrplblk -s “[boot]” -e “end” -o C:\TEMP\OUTPUT.FIL \-i @C:\TEMP\RPLBLK.FIL C:\WINDOWS\SYSTEM.INI

The output of this command is redirected to theOUTPUT.FIL file.

SEE ALSO

winsblk, wclrblk

2–62 Version 3.6

wrplline

Com

mands

is

d

e

g

e

NAME

wrplline

PURPOSE

Replaces a single line in a file. (All supported PC platforms)

SYNOPSIS

wrplline [–f] –s “search_string” [–o output_file]–r “ replace_string” filename

DESCRIPTION

Thewrplline command replaces a line in a text file. The line to bereplaced is found using a search string. Output from this commandwritten to standard output.

Arguments

–f Processes only the first occurrence of the searchstring. If this argument is not specified, the commanprocesses each occurrence of the search string.

–o output_file Writes the output of this command to theoutput_filefile, instead of standard output.

–r “ replace_string”Specifies a string to replace the line that contained thsearch string. You must surround the string withdouble quotation marks.

–s “search_string”Specifies a search string. If the search string iscontained in a line, the line is replaced with the strinspecified by the–r argument. You must surround thestring with double quotation marks.

filename Specifies the name of the file in which to replace thline.


wrplline

EXAMPLE

To replace every occurrence of a line beginning withdevice=in theSYSTEM.INI file with thetype= string, enter the followingcommand:

wrplline -s “device=” -o C:\TEMP\OUTPUT.FIL -r “type=” \C:\WINDOWS\SYSTEM.INI

The output of this command is written to theOUTPUT.FIL file.

SEE ALSO

wclrline , winsline

2–64 Version 3.6

wrunprog

Com

mands

),n to

d

NAME

wrunprog

PURPOSE

Runs a Windows program from a DOS batch file. (Windows only)

SYNOPSIS

wrunprog –nl “ command_line”

DESCRIPTION

Thewrunprog command invokes a Windows program from a DOSbatch file. Usually, you cannot run Windows programs from a DOSconfiguration batch program. Thewrunprog command instructs thePC agent to run the specified command line from the Windowsenvironment.

When launched from the service agent,wrunprog runs with SYSTEMauthorization. When launched from the console agent (diagnosticwrunprog can launch only processes that the user has authorizatiorun.

Note: Tivoli recommends that PC agents be run as NT serviceagents, not as console agents.

Arguments

–nl Executes this command asynchronously; that is, itspawns the command then returns immediately.

“ command_line”Specifies the program (and arguments) to be invokeby the PC agent.

EXAMPLE

To run theNotepad program, enter the following command:

wrunprog C:\WINDOWS\NOTEPAD.EXE


wseterr

ll

asnt

liiles

to

NAME

wseterr

PURPOSE

Sets the return code from a batch file for a configuration program. (Asupported PC platforms)

SYNOPSIS

wseterr return_code

DESCRIPTION

Thewseterr command sets the return code for a batch file invokeda configuration program. This return code is passed to the PC Agewhich, in turn, determines the success or failure of the script. Tivorecommends that you specify this command at the end of all batch fto return the proper code to Software Distribution.

Arguments

return_code Specifies the return code to be returned.

EXAMPLE

To pass the–1 return code to the PC agent, which returns the codeSoftware Distribution, enter the following command:

wseterr -1

2–66 Version 3.6

wsetfpattr

Com

mands

NAME

wsetfpattr

PURPOSE

Sets the attributes for a file package.

SYNOPSIS

wsetfpattr [–b value] [–d value] [–h src_host] [–I fp_info] [–l value][–m dist_mode] [–n value] [–p push_time] [–svalue] [–S fp_size][–t dist_type] [–w staging_area] fp_name

DESCRIPTION

Thewsetfpattr command sets the attributes for a file package.

Authorization

admin, senior or super

Arguments

–b value Sets thebehavior_flagsattribute. Possible values are:

rm_host Moves the file package to thelost-n-found collection, if the filepackage’s log host or source host isremoved.

rm_fp Moves the file package to thelost-n-foundcollection if any of its nestedfile packages are removed.

program_inputSets thexxx_program_input_from_srckeyword to that same value as thexxx_program_prog_from_src keyword,if it was changed in the GUI.

rm_no_chkDoes not check to determine if a removedfile package was nested in the filepackage.


wsetfpattr

s

e,

2

e,

st

nm_chg_no_chkIf the file package name is changed, doenotcheck this file package to determine ifit is nested. If this value is set, other filepackages are checked, and if this filepackage is nested, the reference ischanged to the new file package name.

You can OR any of the previous values (for examplrm_no_chk | nm_chg_no_chk).

none Sets all of the values toFALSE.

–d value Sets thedestination_flags attribute. SoftwareDistribution checks this flag when you save a filepackage or import a file package definition from thedesktop, or when you use thewimprtfp , wsetfpopts,or wsetfpcontents command. Possible values:

nt Ensures that a destination is set forWindows NT platforms.

nw Ensure that a destination is set forNetWare platforms.

os2 Ensures that a destination is set for OS/platforms.

unix Ensures that a destination is set for UNIXplatforms.

win Ensures that a destination is set forWindows platforms.

win95 Ensures that a destination is set forWindows 95 platforms.

You can OR any of the previous values (for examplnt | win | win95).

any Ensures that a destination is set for at leaone platform type.

none Does not check destinations.

You cannot ORany andnone with other values.

2–68 Version 3.6

wsetfpattr

Com

mands

s

to

a

–h src_host Sets thesrc_host attribute.

–I Sets thefp_info attribute, which stores any optionalinformation about the file package. This information iset from the desktop using theEdit OptionalInformation dialog from theEdit menu of theFilePackage Propertieswindow. You must use doublequotes if thefp_info string contains spaces.

–l value Sets thelenient_distribution attribute. Possiblevalues:

TRUE Allows distributions and removals fromthe CLI to any managed node or profilemanager, even if that managed node orprofile manager is not currently asubscriber of the file package’s profilemanager (or any of its subscribing profilemanagers).

FALSE Allows distributions and removals fromthe CLI only to managed nodes or profilemanagers that are currently subscribersthe file package’s profile manager (or anyof its subscribing profile managers).

–m dist_mode Sets thedefault_push_mode attribute. This attributespecifies the mode of distribution that will beperformed for a default distribution. A defaultdistribution is performed when you selectDistribute... from the profile manager icon or theprofile manager menu, or when you drag and drop file package icon onto a subscriber icon. You canspecify one of the following modes:

all Distribute all files.

src Distribute only files that have changed onthe source managed node.

any Distribute files that have changed oneither the source or the target.

–n value Sets thecheck_nested attribute. Values are:


wsetfpattr

,

r

e

pe:

TRUE Checks for circular links for any filepackage properties set operation (usingthe GUI, thewsetfpcontentscommand,or thewimprtfp command), where nestedfile packages are modified.

FALSE Does not check for circular links duringfile package properties set operations.

–p push_time Sets thepush_time attribute.push_time contains thetime of the last successful distribute, commit, orremoval operation (in seconds since 00:00:00 UTCJanuary 1, 1970).

–svalue Sets thecheck_no_src_host attribute. Values are:

TRUE Ensures that a source host is specified foany file package properties set operation(for examples using the GUI,wsetfpcontents, orwimprtfp ) where filesor directories are specified (that is, if thefile package does not contain just nestedfile packages).

FALSE Does not check that a source host wasspecified during file package propertiesset operations.

–S Sets thefp_sizeattribute, which stores the size of thefile package (in bytes). This size includes files,directories, and nested file packages included in thfile package. Calculate the size of a file package fromthe desktop by selecting Calculate Size... the filepackage icon menu in the Profile Manager window.

–t dist_type Sets thedefault_push_type attribute. This attributespecifies the type of distribution that will beperformed for a default distribution. A defaultdistribution is performed when you select theDistribute... option from the profile manager icon orthe profile manager menu, or when you drag and droa file package icon onto a subscriber icon. Values ar

2–70 Version 3.6

wsetfpattr

Com

mands

eote

le

m

re

dist Performs a distribution.

commit Performs a commit operation.

both Performs both a distribute and commitoperation.

–w staging_areaSets thestage_areaattribute. This attribute specifiesthe full path to a directory on the source host where thsnapshot of the file package will reside. This snapshis created when you distribute a file package using thDistribute entries with ANY changes option. Thestaging_area argument must be a full path to adirectory, not a file.

fp_name Specifies an object path or registered name of the fipackage whose attributes are set by this operation.

Return Codes

Thewsetfpattr command returns the following codes to standardoutput:



EXAMPLES

To specify that this file package may be distributed to or removed froany managed node from the command line, enter:

wsetfpattr -l TRUE @example_fp

To specify that the source host does not need to be specified befospecifying file lists, enter:

wsetfpattr -s FALSE @example_fp

SEE ALSO

wgetfpattr


wsetfpcontents

list

gist,

d

a

ied

in

NAME

wsetfpcontents

PURPOSE

Sets the source host, file list, nested file package list, or exclude filefor a file package.

SYNOPSIS

wsetfpcontents [–T] [–E [managed_node:]exclude_path][–F [managed_node:] filelist_path] [–h src_host][–N [managed_node:]nested_path] fp_name

wsetfpcontents –t [–E] [–F] [–h] [–N] fp_name

DESCRIPTION

Thewsetfpcontentscommand manipulates the contents of an existinfile package by setting the source host, file list, nested file package land exclude file list. If you specify the–t argument, you must specifyadditional arguments alone (see the second synopsis statement).

Authorization


Arguments

–E [managed_node:]exclude_pathChanges the exclude file list to those files anddirectories listed in the file specified by[managed_node:]exclude_path.

–F [managed_node:]filelist_pathChanges the file list to those files and directories listein the file specified by [managed_node:]filelist_path.See “Files and Directories Section” on page 1-3 forlist of valid entries for the file list.

–h src_host Changes the source host, where the files in the filepackage are obtained, to the managed node specifby src_host. This argument is optional unless you areadding source files or directories to the file package;

2–72 Version 3.6

wsetfpcontents

Com

mands

s

g

le

d

that case, you must specify a source host using thiargument.

–N [managed_node:]nested_pathChanges the nested file package list to those filepackages listed in the file[managed_node:]nested_path.

–T Sets the file package list and source host withoutinvoking the validation methods in the policy. The–Toption is set by default.

–t Sets the file package list and source host after invokinthe validation methods in the policy defaults (if anyare set) or TME 10 defaults.

fp_name Specifies the object path or registered name of the fipackage to be modified.

Return Codes

Thewsetfpcontentscommand returns the following codes to standaroutput:



EXAMPLES

To set the source host tocrumpet, enter the following command:

wsetfpcontents -h @crumpet @example_fp

To set the exclude file list specified in the/tmp/exclude.listfile, enter:

wsetfpcontents -E /tmp/exclude.list @example_fp

To set the file list to the default defined by thefp_def_flist policymethod, enter:

wsetfpcontents -t -F @example_fp

SEE ALSO

wsetfpopts, wsetfpprgs


wsetfpopts

g

dlt

NAME

wsetfpopts

PURPOSE

Sets or modifies the options for a file package.

SYNOPSIS

wsetfpopts {–T type | –t type} { keyword_options} fp_name

DESCRIPTION

Thewsetfpoptscommand manipulates file package options by settinkeyword options, either to a specified value or to their default. Itcannot manipulate the contents of a file package (such aswsetfpcontents), nor the configuration program informationassociated with a file package (likewsetfpprgs).

Authorization


Arguments

keyword_optionsSets the keyword values for the file package. If usewith the–t argument, the keyword is reset to its defauvalue. If used with the–T argument, the keyword is setto a user-specified value as indicated below. Validvalues are as follows:

path A fully-specified path for a file.

y | n YES or NO, respectively.

string A command to be performed whenappropriate for the specified keyword.

gid The numeric group ID.

uid The numeric user ID.

int An integer.

path A fully-specified path for a file ordirectory.

2–74 Version 3.6

wsetfpopts

Com

mands

:

len.

.

d

Pmode A file permission setting (see thechmodman page).

time A date value for the date and time(conforming todate semantics).

mail_id An E-mail address for a user; for [email protected].

log_host Label of the managed node.

fp_name Specifies an object path or registered name of the fipackage whose options are modified by this operatio

–t type Sets the specified keyword option to its default valueThe type argument specifies the type of platform onwhich the keyword is set. Software Distribution looksfor default settings in the file package’s policy regionfirst. If the default is not set there, SoftwareDistribution adopts the program defaults as describein Chapter 1, “File Package Definitions.”

Do not specify arguments with–t typekeywordoptions—for example,-t unix -v does not require anyarguments after the-v keyword option. Valid types areshown below, with their valid keyword options:

gen All platforms; keyword options are notplatform-specific (apply to all platforms).Valid keyword options forgen are:–a,–A, –b, –B, –c, –C, –d, –D, –e, –E, –f, –F,–h, –H, –i, –I, –j, –k, –l, –L, –m, –M, –n,–N –o, –P, –q, –Q, –r, –R, –s, –S, -v, and–x. See below for keyword optiondescriptions.

unix Keyword options that apply specifically toUNIX type target machines. Validkeyword options forunix are:–g, –G, –p,–u, and–U. See below for keyword optiondescriptions.

nw Keyword options that apply specifically toNetWare target machines. Valid keyword


wsetfpopts

nt

options fornw are–p, –V, –X, –y, –Y, –z,and –Z. See below for keyword optiondescriptions.

win Keyword options that apply specifically toWindows target machines. Valid keywordoptions forwin are:–w, –W and–p. Seebelow for keyword option descriptions.

win95 Keyword options that apply specifically toWindows 95 target machines. Validkeyword options forwin95 are:–w, –Wand–p. See below for keyword optiondescriptions.

nt Keyword options that apply specifically toWindows NT target machines. The validkeyword option fornt is –p. See below forkeyword option descriptions.

os2 Keyword options that apply specifically toOS/2 target machines. The valid keywordoption foros2is –p. See below forkeyword option descriptions.

–T type Sets the specified keyword option to the specifiedargument. Thetype argument specifies the type ofplatform on which the keyword is set. Valid types aregen, unix, nw, win, win95, nt, andos2, as discussedabove.

General Keyword Options

Use the general following keyword options with the–T genargument:

–a [y | n] Sets theappend_logkeyword, which toggles whetherto append a notice to a log file when an operation isperformed (y) or to replace the previous notice (n).

-A Sets the new keyword,ams_inst_sw_comp_handle,to denote the AMS Installed Software ComponentHandle, which identifies the installed softwarecomponent handle created for the software componeby the Tivoli Developer’s Toolkit. Software

2–76 Version 3.6

wsetfpopts

Com

mands

t.

e

e

s)

the

Distribution passes the value of this keyword as thethird argument to before and after configurationprograms.

–b string Sets thebackup_fmt keyword, which specifies abackup path for files if they already exist at the targeFor example, if you specifystring to be/backup/%p/%f%n . %p provides the base path,%fprovides the filename, and%n is an auto-incrementing numeric value. Thus, if you specify/etc/motd as the backup file, the resulting file’s pathbecomes/backup/etc/motd1. The next time the file isdistributed, the resulting backup file is named/backup/etc/motd2, and so on.

–B uid Sets thelog_file_uid keyword, which sets the UID ofthe log file specified by thelog_file keyword.

–c [y | n] Sets thedo_compress keyword, which toggleswhether to compress the file package beforedistributing it (y) or not (n).

–C [y | n] Sets thecreate_dirs keyword. This keyword toggleswhether to create intermediate directories at thedestination for the files in a file package if thosedirectories do not exist (y) or not (n).

–d [y | n] Sets thedescend_dirs keyword, which toggleswhether to traverse component directories in the filpackage listing (y) or not (n). If y, The directories andall files and directories therein are distributed.

–D path Sets thedefault_dest keyword, which specifies thedefault destination directory (entered as an absolutpath) for all entries in the file package.

–email_id Sets themail_id keyword, which is the completee-mail address (such as [email protected]) of person(to whom to send mail. For multiple mail recipients,separate addresses by a single space and enclosecollection of addresses in double quotes.


wsetfpopts

t

d.

e

d

–E string Sets theprog_env keyword, which specifies a stringas theputenv value before a configuration programruns on a UNIX machine. Thestringargument is a listof name=value pairs wherename is an environmentvariable set byvalue. Refer to Chapter 1, “FilePackage Definitions” for more information on theprog_env keyword.

–f [y | n] Sets thefollow_links keyword, which toggles whetherto follow symbolic links to the original files (therebycopying the files to the target instead of the links) (y),or to create new links to the original files at thedestination, and not distribute the files (n).

–F [y | n] Sets thefile_cksumskeyword, which toggles whetherto compute the checksum on individual files to detecdifferences between the source and target (y).

–h log_host Sets thelog_host keyword, which specifies the labelof the managed node where the log file is generate

–H gid Sets thelog_file_gid keyword, which sets the GID ofthe log file specified by thelog_file keyword.

–i time Sets thedefault_mtime keyword, which specifies thedefault modification time (conforming todatesemantics) for all entries distributed in the filepackage.

–I [y | n] Sets theinstall_progs keyword, which toggleswhether to remove the configuration programs on thtarget machine after they run. If you specifyy, theprograms are not removed.

–j mode Sets thelog_file_mode keyword, which sets the filemode of the log file specified by thelog_file keyword.

–k [y | n] Sets thekeep_pathskeyword, which toggles whetherto concatenate the entire source file path into thedestination file path (y). The default isn.

–l path Sets thelist_path keyword, which specifies adirectory on the target host where the list of distribute

2–78 Version 3.6

wsetfpopts

Com

mands

files to that target are stored. The file is namedfpname.log.

–L path Sets thelog_file keyword, which appends notices tothe specified complete path of a file if the–aargument(theappend_log keyword) is set toy, or replacesnotices if set to n. The managed node for this file isspecified by the–h argument. If no host is specified,the TMR server is used. If the file does not exist, anattempt is made to create it.

–m mode Sets thedefault_file_modekeyword, which specifiesthe mode of files (according tochmod numericspecification) for files that are distributed.

–M mode Sets thedefault_dir_modekeyword, which specifiesthe mode of directories (according tochmod (2)numeric specification) for directories that aredistributed.

–n [y | n] Sets theno_overwrite keyword, which toggles to notoverwrite files existing on the target with those in thefile package (y).

–N [y | n] Sets thenested_first keyword, which unpacks fileswithin nested file packages first at the target (y). Thedefault is to unpack them last (n).

–o [y | n] Sets theskip_older_src keyword, which does notdistribute source files in the file package if they areolder than those on the target (y).

–P [y | n] Sets thepost_noticekeyword, which toggles whetherto post notices to the Software Distribution noticegroup when file package operations are performed (y).

–q string Sets thepostproc keyword, which specifies aprocessing filter to be run before the file package issent out from the host (but after it is packaged).

–Q string Sets thepreproc keyword, which specifies aprocessing filter to be run before the distribution isunpacked at the target.


wsetfpopts

o

et

n

is

e

–r [y | n] Sets therm_empty_dirs keyword, which toggleswhether to remove all empty target directories, up t/xxx_platform_prefix/default_dest at the target afterthe file package is removed (y) or not (n). The defaultis n.

–R [y | n] Sets therm_extraneous keyword, which toggleswhether to remove files in an existing destinationdirectory that are extraneous to the file package (y) ornot (n) during a distribution (of all file packageentries). The default isn. If the–b argument (thebackup_fmt keyword) is used, the removed files arefirst copied to a backup directory.

–s [y | n] Sets thestop_on_error keyword, which toggleswhether to stop processing the distribution for a targif an error occurs during distribution to that target (y)or not (n). The default isy.

–Spath Sets thesrc_relpath keyword, which specifies theabsolute path for all relative paths used in the filepackage definition.

-v int Sets theprogs_timeout keyword, which sets atimeout value for all configuration programs specifiedin the file package. Specifyint in seconds; the defaultis -1, which enables the configuration program to ruuntil completion (no timeout).

–x [y | n] Sets thedo_checksum keyword, which performs achecksum parity check on the file package when it distributed.

UNIX Keyword Options

–g gid Sets theunix_default_file_gid keyword, which setsthe default group ID (any decimal value valid as a GIDon a UNIX target or name of a group valid on the TMRserver) for all files and links distributed in the filepackage. The default is to preserve the group ID of thsource.

2–80 Version 3.6

wsetfpopts

Com

mands

e

he

he

or

or

xt

–G gid Sets theunix_default_dir_gid keyword, which setsthe default group ID (any decimal value valid as a GIDon a UNIX target or name of a group valid on the TMRserver) for all directories distributed in the filepackage. The default is to preserve the group ID of thsource.

–u uid Sets theunix_default_file_uid keyword, which setsthe default user ID (any decimal value valid as a UIDon a UNIX target or name of a user valid on the TMRserver) for all files and links distributed in the filepackage. The default is to preserve the user ID of tsource.

–U uid Sets theunix_default_dir_uid keyword, which setsthe default user ID (any decimal value valid as a UIDon a UNIX target or name of a user valid on the TMRserver) for all directories distributed in the filepackage. The default is to preserve the user ID of tsource.

–p path Sets theunix_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to UNIX targets.

NetWare Keyword Options

–p path Sets thenw_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to NetWare targets.

–V [y | n] Sets thenw_bindery keyword, which indicateswhether to login to the NetWare 4.x server in binderymode, thus, emulating a NetWare 3.x machine. If youset this keyword (y), thenw_context andnw_treekeywords are ignored. The default for this option isn.

–x context Sets thenw_contextkeyword, wherecontextspecifiesthe directory services context for a distribution to aNetWare 4.x server. Thecontext argument must be astring that specifies a valid directory services conteon the NetWare target.


wsetfpopts

e

e

ed

1

or

–y tree Sets thenw_tree keyword, wheretree specifies adirectory services tree to which to distribute a filepackage on a NetWare target. Thetreeargument mustbe a string that specifies a valid directory services treon the NetWare target.

–Y [y | n] Sets thenw_force_disconnect keyword, whichspecifies whether to break a lock on a file and replacthe file during a distribution to a NetWare target. Thedefault for this option isn.

–z [y | n] Sets thenw_broadcast_mode keyword, whichspecifies whether to broadcast the message specifiby thenw_broadcast_message keyword to allNetWare targets of a distribution (y) or only thosetargets that have locked files which will be distributed(n). The default isn.

–Z message Sets thenw_broadcast_message keyword, wheremessage is a string up to 255 characters that isbroadcast to NetWare targets prior to distribution.

Windows Keyword Options

–w [y | n] Sets thewin_optional_dist keyword, which specifiesan optional (y) or mandatory (n) distribution. Optionaldistribution displays a dialog at distribution orremoval time on the target from which the user canchoose to receive the distribution or removal. Thedefault setting isn. If the setting isy and the user doesnot respond, the distribution or removal isautomatically performed withinwin_optional_dist_timeout seconds.

–W int Sets thewin_optional_dist_timeoutkeyword, whichspecifies the number of seconds (any decimal fromto 6000) that thewin_optional_dist dialog isdisplayed. The default is 120 seconds.

–p path Sets thewin_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to Windows targets.

2–82 Version 3.6

wsetfpopts

Com

mands

n

l

or

or

or

Windows 95 Keyword Options

–w [y | n] Sets thewin95_optional_dist keyword, whichspecifies an optional (y) or mandatory (n) distribution.Optional distribution displays a dialog at distributionor removal time on the target from which the user cachoose to receive the distribution or removal. Thedefault setting isn. If the setting isy and the user doesnot respond, the distribution or removal isautomatically performed withinwin95_optional_dist_timeout seconds.

–W int Sets thewin95_optional_dist_timeout keyword,which specifies the number of seconds (any decimafrom 1 to 6000) that thewin95_optional_dist dialogis displayed. The default is 120 seconds.

–p path Sets thewin95_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to Windows 95 targets.

Windows NT Keyword Options

–p path Sets thent_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to Windows NT targets.

OS/2 Keyword Options

–p path Sets theos2_platform_prefix keyword, whichprepends the specified path to all destination paths fdistributions to OS/2 targets.

Return Codes

Thewsetfpopts command returns the following codes to standardoutput:




wsetfpopts

n

ble

inglueers.

EXAMPLES

To set the value of theappend_log keyword toy, enter the following:

wsetfpopts -T gen -a y @example_fp

To reset the value of theappend_log keyword to its default, enter:

wsetfpopts -t gen -a @example_fp

To set the value of theunix_default_file_uid keyword, enter:

wsetfpopts -T unix -u 300 @example_fp

To set theprogs_timeout keyword, enter:

wsetfpopts -T unix -v 600 @example_fp

The -v keyword sets a client-level timeout value for all configuratioprograms specified in the file package.

To set theprog_envkeyword to a value that will make the destinationpath for the UNIX targets, the mail IDs that will receive informationabout the status of this operation, and the file package name availato any configuration programs running on UNIX targets, enter thefollowing command:

wsetfpopts -T gen -E UNIX_DEST=\$unix_platform_prefix\ \MAIL_USERS=\’\$mail_id\’\ FPNAME=\’\$fpname\’ \@”example_fp 1”

You must escape (using back slashes) all spaces in the string followthe–E argument so that the shell treats the string as one logical vafor the argument. You must also escape all (shell) special charactThis prevents the shell from interpreting, for example,$mail_id as ashell variable. Finally, because the values of themail_id keyword andthe file package name might contain spaces, you must quote theMAIL_USERS andFPNAME variables (using single quotation

2–84 Version 3.6

wsetfpopts

Com

mands

his
marks) to ensure that the complete values are set. After you run tcommand, theprog_env variable is set to the following:
prog_env=”UNIX_DEST=$unix_platform_prefixMAIL_USERS=’$mail_id’ FPNAME=’$fpname’”

SEE ALSO

wsetfpcontents, wsetfpprgs


wsetfpprgs

on

ben

s.omeify

ndot

nt

d

e

at

NAME

wsetfpprgs

PURPOSE

Sets or modifies the before, after, remove, after removal, commit, orerror program information associated with a file package.

SYNOPSIS

wsetfpprgs {–t type| –T type} [ keyword_options] fp_name

DESCRIPTION

This command enables you to specify the configuration program torun on the source host or target. If you specify multiple configuratioprograms of the same type, you must separate them with commaLikewise, to specify input files for multiple programs, you must alsseparate them with commas. The programs must reside on the satarget or source and are processed in the order in which you specthem. If a program does not require an input file but subsequentprograms do, you must specify the input files in the correct order apreceded by the same number of commas as the programs. Do nfollow commas with spaces.

If you specified multiple before programs and one fails, subsequebefore programs will run if you did not enable theStop distributionon error option on theFile Package Properties window(unix_before_skip_non_zero=y). Otherwise, the distribution stopsand subsequent programs will not run. If you specified multipleprograms of any other type and one fails, the distribution stops anSoftware Distribution will not run subsequent programs.

Thewsetfpprgs command also enables you to specify whetherprograms and input files reside on the source host or a target. If thprograms and input files reside on the source host (using the–A, –B,–C, –D, –E, –F, –G, –I, –J, –K, –L, –N, and–R arguments), you canspecify a relative path to them. Software Distribution runs theprograms and obtains the input files from the path specified by thesrc_relpath keyword. If the programs and input files reside on thetarget, you must specify a full path to each. By default, programs th

2–86 Version 3.6

wsetfpprgs

Com

mands

ams

e

.

run on a target reside on that target. Source before and after progrreside on the source.

Thewsetfpprgscommand cannot manipulate the files of a file packag(wsetfpcontents), nor the file package options (wsetfpopts).

Authorization


Arguments

–t type Sets the specified keyword option to its default valueThe type argument specifies the type of platform onwhich the program is run. Software Distribution looksfor default settings in the file package’s policy regionfirst. If the default is not set there, SoftwareDistribution adopts the defaults as described inChapter 1, “File Package Definitions.” Do not specifyarguments with the keyword option.

Do not specify arguments with–t typekeywordoptions—for example,-t unix -v does not require anyarguments after the-v keyword option. Valid types areshown below, with their valid keyword options:

src Keyword options that apply to running aprogram on the source host. Validkeyword options forsrc are:–a, –b, –i, –s,–u, and–U. See below for keyword optiondescriptions.

unix Keyword options that apply to running aprogram on a UNIX target machine. Validkeyword options forunix are:–a, –A, –b,–B, –c, –C, –d, –D, –e, –E, –f, –F, –g, –G,–i, –I, –j, –J, –k, –K, –l, –L, –r, –R, –s,–u, –U –v, –V, –w, and–W. See below forkeyword option descriptions.

nw Keywords that apply to running a programon a NetWare target machine. Validkeyword options fornw are:–a, –A, –b,–B, –c, –C, –d, –D, –e, –E, –f, –F, –g, –G,


wsetfpprgs

e

–i, –I, –j, –J, –k, –K, –l, –L, –M, –n, –N,–r, –R, and–s. See below for keywordoption descriptions.

win Keywords that apply to running a programon a Windows target machine. Validkeyword options forwin are:–a, –A, –b,–B, –c, –C, –d, –D, –e, –E, –f, –F, –g, –G,–i, –I, –j, –J, –k, –K, –l, –L, –o, –O, –p,–P, –q, –r, –R, and–s. See below forkeyword option descriptions.

win95 Keywords that apply to running a programon a Windows 95 target machine. Validkeyword options forwin95 are:–a, –A,–b, –B, –c, –C, –d, –D, –e, –E, –f, –F, –g,–G, –i, –I, –j, –J, –k, –K, –l, –L, –o, –O,–p, –P, –q, –r, –R, and–s. See below forkeyword option descriptions.

nt Keywords that apply to running a programon a Windows NT target machine. Validkeyword options fornt are:–a, –A, –b,–B, –c, –C, –d, –D, –e, –E, –f, –F, –g, –G,–i, –I, –j, –J, –k, –K, –l, –L, –o, –O, –P,–q, –r, –R, and–s. See below for keywordoption descriptions.

os2 Keywords that apply to running a programon an OS/2 target machine. Valid keywordoptions foros2are:–a, –A, –b, –B, –c,–C, –d, –D, –e, –E, –f, –F, –g, –G, –i, –I,–j, –J, –k, –K, –l, –L, –r, –R, and–s. Seebelow for keyword option descriptions.

–T type Sets the specified keyword option to the specifiedargument. Thetype argument specifies the type ofplatform on which the program is run. Valid values arsrc, unix, nw, win, win95, nt, andos2, as describedabove.

2–88 Version 3.6

wsetfpprgs

Com

mands

to

ds:

1,

e

keyword_optionsSpecifies the configuration program keyword valuesbe set for the file package. If used with the–t specifier,the keyword is reset to its default value. If used withthe–T specifier, the keyword is set to a user-specifievalue as indicated below. Valid values are as follow

path A fully-specified path for a file.

y | n YES or NO, respectively.

uid A numeric user ID.

Each of the keyword options can specify differentkeywords, depending on the type specified with the–Targument. For this reason,xxx is used in the keyworddescription in place of the host or target type.

For example, for the keyword option–a (listed asxxx_after_prog_path) the keyword is set tosrc_after_prog_path if you specify type assrc.

Specific keywords are described in detail in Chapter“File Package Definitions”

–a path Sets thexxx_after_prog_path keyword,which runspath on each target (or thesource host) after a file package’s files arapplied.

–A [y | n] Sets thexxx_after_prog_from_srckeyword, wherey indicates thatxxx_after_prog_path resides on thesource host, andn that it reside on eachtarget.

–b path Sets thexxx_before_prog_pathkeyword,which runspath on each target (or thesource host) before a file package’s filesare applied.

–B [y | n] Sets thexxx_before_prog_from_srckeyword, wherey indicates thatxxx_before_prog_path resides on the


wsetfpprgs

.

source host, andn that it resides on eachtarget.

–c path Sets thexxx_commit_prog_pathkeyword, which runspath on each targetduring a commit operation.

–C [y | n] Sets thexxx_commit_prog_from_srckeyword, wherey indicates thatxxx_commit_prog_path resides on thesource host, andn that it resides on eachtarget.

–d path Sets thexxx_after_removal_prog_pathkeyword, which runspath on the targetafter removing the file package.

–D [y | n] Sets thexxx_after_removal_prog_from_srctoggle, wherey indicates thatxxx_after_removal_prog_path resideson the source host, andn that it resides oneach target.

–epath Sets thexxx_after_removal_input_pathkeyword, which passespath as standardinput (orarg[2] on PCs) toxxx_after_removal_prog_path. This keyword isonly applicable if the–d argument(xxx_after_removal_prog_path) is set.

–E [y | n] Sets thexxx_after_removal_input_from_srctoggle, wherey indicates thatxxx_after_removal_input_path resideson the source host, andn that it resides oneach target.

–f path Sets thexxx_on_error_prog_pathkeyword, which runspathon the target ifan error stops a file package distribution

2–90 Version 3.6

wsetfpprgs

Com

mands

–F [y | n] Sets thexxx_on_error_prog_from_srctoggle, wherey indicates thatxxx_on_error_prog_path resides on thesource host, andn that it resides on eachtarget.

–g path Sets thexxx_on_error_input_pathkeyword, which passespath as standardinput (or arg[2] on PCs) toxxx_on_error_prog_path. This keywordis only applicable if the–f argument(xxx_on_error_prog_path) is set.

–G [y | n] Sets thexxx_on_error_input_from_srctoggle, wherey indicates thatxxx_on_error_input_path resides on thesource host, andn that it resides on eachtarget.

–i path Sets thexxx_after_input_path keyword,which passespath as standard input (orarg[2] on PCs) toxxx_after_prog_path.This keyword is only applicable if the –aargument (xxx_after_prog_path) is set.

–I [y | n] Sets thexxx_after_input_from_srckeyword, wherey indicates thatxxx_after_input_path resides on thesource host, andn that it resides on eachtarget.

–j path Sets thexxx_before_input_pathkeyword, which passespath as standardinput (orarg[2] on PCs) toxxx_before_prog_path. This keyword isonly applicable if the–b argument(xxx_before_prog_path) is set.

–J [y | n] Sets thexxx_before_input_from_srckeyword, wherey indicates thatxxx_after_prog_path resides on the


wsetfpprgs

e

source host, andn that it resides on eachtarget.

–k path Sets thexxx_commit_input_pathkeyword, which passespath as standardinput (orarg[2] on PCs) toxxx_commit_prog_path. This keyword isapplicable only if the–c argument(xxx_commit_prog_path) is set.

–K [y | n] Sets thexxx_commit_input_from_srckeyword, wherey indicates thatxxx_commit_input_path resides on thesource host, andn that it resides on eachtarget.

–l path Sets thexxx_removal_input_pathkeyword, which passespath as standardinput (orarg[2] on PCs) toxxx_removal_prog_path. This keywordis applicable only if the–r argument(xxx_removal_prog_path) is set.

–L [y | n] Sets thexxx_removal_input_from_srctoggle, wherey indicates thatxxx_removal_input_path resides on thesource host, andn that it resides on eachtarget.

–M [y | n] Sets a NetWare specific option, thenw_login_replace keyword, whereyindicates that the trustee login scripts aroverwritten, andn that they should beappended. This function only occursduring commit operations. The default isn. This option is applicable only whennw_login_prog_path is not NULL.

–n path Sets a NetWare specific option, thenw_login_prog_path keyword, whichspecifies the path to a login script. You

2–92 Version 3.6

wsetfpprgs

Com

mands

cannot specify multiple programs for thiskeyword.

–N [y | n] Sets a NetWare specific option, thenw_login_get_from_srckeyword, wherey indicates thatnw_login_prog_pathresides on the source host, andn that itresides on each target.

–o [REBOOT | RESTART | NONE]Sets thexxx_after_option keyword.When this keyword is set toREBOOT,the target reboots after the distribution.RESTART restarts Windows, Windows95, or Windows NT after the distribution.NONE does not reboot or restart thetarget. This keyword is only valid forWindows, Windows 95, or Windows NTmachines. If an after program is specifiedand it fails, the system is not restarted.

–O [REBOOT | RESTART | NONE]Sets thexxx_commit_option keyword.When this keyword is set toREBOOT,the target reboots after the commitoperation runs.RESTART restartsWindows, Windows 95, or Windows NTafter the commit.NONE does not rebootor restart the target. This keyword is onlyvalid for Windows, Windows 95, orWindows NT machines. If a commitprogram is specified and it fails, thesystem is not restarted.

–p [REBOOT | RESTART | NONE]Sets thexxx_removal_option keyword.When this keyword is set toREBOOT,the target reboots after the removaloperation runs.RESTART restarts thetarget after the removal (on Windows,Windows 95, or Windows NT machines).


wsetfpprgs

NONE does not reboot or restart thetarget. This keyword is only valid forWindows, Windows 95, or Windows NTmachines. If a removal program isspecified and it fails, the system is notrestarted. Also, if you specify the–Pargument, the most drastic actionspecified is performed. For example, ifyou set–p REBOOT and–P NONE, thetarget is rebooted.

–P [REBOOT | RESTART | NONE]Sets thexxx_after_removal_optionkeyword. When this keyword is set toREBOOT, the target reboots after theremoval operation runs.RESTARTrestarts the target after the removal (onWindows, Windows 95, or Windows NTmachines).NONE does not reboot orrestart the target. This keyword is onlyvalid for Windows, Windows 95, orWindows NT machines. If an afterremoval program is specified and it fails,the system is not restarted. Also, if youspecify the–p argument, the most drasticaction specified is performed. Forexample, if you set–p REBOOT and–PNONE, the target is rebooted.

–q [REBOOT | RESTART | NONE]Sets thexxx_on_error_option keyword.When this keyword is set toREBOOT,the target reboots after the removaloperation runs.RESTART restarts thetarget after the removal (on Windows,Windows 95, or Windows NT machines).NONE does not reboot or restart thetarget. This keyword is only valid forWindows, Windows 95, or Windows NTmachines. If an on error program is

2–94 Version 3.6

wsetfpprgs

Com

mands

specified and it fails, the system is notrestarted.

–r path Sets thexxx_removal_prog_pathkeyword, which runspath on the targetbefore removing the file package from thesubscribers.

–R [y | n] Sets thexxx_removal_prog_from_srckeyword, wherey indicates thatxxx_removal_prog_path resides on thesource host, andn that it resides on eachtarget.

–s [y | n] Sets thexxx_before_skip_non_zerokeyword, wherey indicates thatdistribution is skipped ifxxx_before_prog_path exits with anon-zero exit code, andn indicates that itis not skipped.

–u uid Sets thesrc_after_as_uid orunix_after_as_uid keyword, which setsthe user ID under which to runsrc_after_prog_path or unix_after_prog_path.

–U uid Sets thesrc_before_as_uid orunix_before_as_uidkeyword, which setsthe user ID under which to runsrc_before_prog_pathorunix_before_prog_path.

–v uid Sets theunix_commit_as_uid keyword,which sets the user ID under which to rununix_commit_prog_path.

–V uid Sets theunix_removal_as_uidkeyword,which sets the user ID under which to rununix_removal_prog_path.

–w uid Sets theunix_after_removal_as_uidkeyword, which sets the user ID under


wsetfpprgs

leme.

which to rununix_after_removal_prog_path.

–W uid Sets theunix_on_error_as_uidkeyword,which sets the user ID under which to rununix_on_error_prog_path.

fp_name Specifies an object path or registered name of the fipackage, as an absolute path or as a registered na

Return Codes

Thewsetfpprgs command returns the following codes to standardoutput:



EXAMPLES

To set the value of thent_after_prog_path keyword, enter thefollowing commands:

wsetfpprgs -T nt -a /tmp/myprog32.exe @example_fp

To reset the value of thent_after_prog_path keyword back to itsdefault, enter:

wsetfpprgs -t nt -a @example_fp

SEE ALSO

wsetfpcontents, wsetfpopts

2–96 Version 3.6

wsettrus

Com

mands

es

ey

Ware

e

NAME

wsettrus

PURPOSE

Sets the trustee rights for files and directories. (NetWare only)

SYNOPSIS

NetWare 3.x

wsettrus –utrustee–d path–r rights

NetWare 4.x

wsettrus –utrustee–d path–r rights [–c context–t tree]

wsettrus –aadmin_login–p password

DESCRIPTION

Thewsettrus command sets the trustee rights for files and directorion a NetWare server. You can include this command in an afterprogram to set user and group rights of files and directories after thare distributed by Software Distribution.

Use this commands on a NetWare 3.x server as specified by the firstsynopsis statement. Use the second and third statements on a Net4.x server. The third synopsis statement enables you to set thepassword for the specified administrator. Set the password from thcommand line on the NetWare server or prior to the administratorlogin’s use by Software Distribution.

Arguments

–a admin_loginSpecifies the administrator’s login for which you aresetting the password. Use this argument inconjunction with the–p argument.

–c context Specifies the directory services context for which toset the rights. You must specify the–t argument withthis argument.


wsettrus

d

t

g

:

–d path Specifies the fill path of the file or directory for whichyou are setting trustee rights.

–p password Sets the password of the administrator login specifieby the–a argument. This password is encrypted andmust be set prior to Software Distribution using theadministrator’s login.

–r rights Sets the rights for the user or group specified by the–uargument. The following rights are available.

R (read),W (write), C (create),E (erase),A (accesscontrol),F (file scan),M (modify), andS (supervisor)

–t tree Specifies the directory services tree for which to sethe rights. You must specify the–cargument with thisargument.

–u trustee Specifies the user or group for which you are settinrights.

EXAMPLES

The following command example sets the password for theJrAdminadministrator login on a NetWare 4.x machine.

wsettrus -a JrAdmin -p toilNtrouble

To set theWRM rights (write, read and modify rights) for the userMageeon theSYS:\PUBLIC directory, enter the following command

wsettrus -u Magee -d SYS:\PUBLIC -r WRM

To set supervisory (S) rights forSmith on theSYS:\PUBLICdirectory. These rights are set in theo=my_companycontext of themarketing tree of the NetWare 4.x server.

wsettrus -u Smith -d SYS:\PUBLIC -r S -c o=my_company \-t marketing

2–98 Version 3.6

wsetval

Com

mands

y

e:

e

NAME

wsetval

PURPOSE

Sets a registry key value. (Windows 95 and Windows NT only)

SYNOPSIS

wsetval [–h registry_hive] { –k key |@filename} –n value_name{ –v “value_string” | @filename}

DESCRIPTION

Thewsetvalcommand replaces a key value in the registry. If the keor value does not exist, it is created.

Authorization

administrator

Arguments

–h registry_hiveSpecifies the registry hive to update. Valid values ar

HKEY_LOCAL_MACHINE (default)

HKEY_CURRENT_USER

HKEY_CLASSES_ROOT

HKEY_USERS

–k key | @filenameSpecifies the key in which the value is inserted. If thfirst character of the key is@, the key is read fromfilename.

–n value_nameSpecifies the name of the value.

–v “value_string” | @filenameSpecifies the value or file that contains the value.


wsetval

EXAMPLE

To add theNOTEPAD subkey under the existingSOFTWARE key,and assign theNOTEPADVAR key value name in theHKEY_LOCAL_MACHINE hive, enter the following command:

wsetval -h HKEY_LOCAL_MACHINE -k SOFTWARE\NOTEPAD \-n NOTEPADVAR -v C:\TEMP\NTPADVAR.FIL

2–100 Version 3.6

wswdistrim

Com

mands

e

e

lled

ngs.

NAME

wswdistrim

PURPOSE

Sets the tracking feature to control when the TME 10 Inventoryconfiguration repository is updated with information about SoftwarDistribution operations.

SYNOPSIS

wswdistrim {-c | -d}

DESCRIPTION

Thewswdistrim command is used to disable and then re-enable thtracking feature from the command line to control when SoftwareDistribution information is posted to the configuration repository.When this feature is enabled, the TME 10 Inventory configurationrepository is updated with information about file packages,AutoPacks, and file package blocks (fpblocks) that have been instaor removed in the TME 10 environment.

Tivoli suggests that you disable the tracking feature prior to deployia file package for which you do not want to track distribution statisticRe-enable the tracking feature to resume tracking distributioninformation in the configuration repository.

Authorization

senior or super

Arguments

–c Re-enables the tracking feature.

–d Disables the tracking feature.

EXAMPLES

To disable the tracking feature, enter:

wswdistrim -d


wswdistrim

To re-enable the tracking feature, enter:

wswdistrim -c

2–102 Version 3.6

Policy

s

foriesasn.

ckgeofe arceby a

or

ct

aek

3Policy

TME 10 policy enables you to control the default values ofnewly-created resources (default policy) and to maintain guidelinewhen administrators modify or operate on resources (validationpolicy). Specifically, the TME 10 Software Distribution default andvalidation policies enable you to set defaults and enforce guidelinesfile package and AutoPack properties and operations. These policare implemented as shell scripts or programs—UNIX scripts (suchBourne, K, and Perl shells), awk programs, C programs, and so o

Default policies set the default values for file package and AutoPaproperties. These policies are useful if you want to preset file packaand AutoPack properties with specific values. For example, if mostyour file packages will have the same source host, you could defindefault policy so that every newly-created file package has its souhost set to that machine. You can change properties set to a valuedefault policy (if you do not violate validation policy).

Similarly, validation policy ensures that file package and AutoPackproperties or operations always adhere torules. For example, you cancreate a script for theap_val_name policy method specifying thatAutoPack names cannot contain punctuation marks or slashes. Fexample, if an administrator attempts to name an AutoPackdata\upgrades, the validation fails and the administrator must seleanother name, such asdata-upgrades.

Software Distribution policy is policy-region based. When you set default or validation policy, that policy method generally runs on thTMR server in the policy region in which the file package or AutoPac

3


Default Policy Methods

s inain

e

r

nst

dslicy

ant.e

e C

ntsin

eod.the

ect

resides. The policy applies to all file package or AutoPack resourcethat policy region. The names of the methods and their inputs remthe same.

Note: Policy methods that do NOT run in the policy region where thresource resides includefp_val_src_host andap_val_autopack_ host_file. These methods run in the policyregion where the source host resides for the file package oAutoPack, respectively.

Finally, it is important to mention that because these resources caonly reside on UNIX or NT managed nodes, the policy methods mube UNIX or NT scripts, programs, or executables. Tivoli recommenthat, because policies are stored in the database, you write your pomethods in an interpreter language to save space. Executables(compiled programs) are generally larger. An interpretive program coften be used across multiple platforms; executables often cannoThus, use UNIX scripts or programs on UNIX managed nodes. Us.BAT, .EXE, or .COM files, in addition to UNIX scripts or programsif the necessary tools are available, on the NT machine. Do not usshell scripts.

For more information on default and validation policy and policyregions, see theTME 10 Framework User’s Guide.

Default Policy MethodsDefault policy methods are shell scripts or programs invoked bySoftware Distribution when you create a new file package andAutoPack. By creating scripts or programs and replacing the conteof these policy methods, you can automatically set the properties newly-created file packages and AutoPacks.

When Software Distribution invokes a default policy method, the namof the file package or AutoPack being created is passed to the methSoftware Distribution expects the default policy methods to exit withe code0, so you must write your policy methods to do so. Reservother exit codes for hard errors, such as insufficient memory, incorrusage, and so on.

3–2 Version 3.6


Policy

as
The default policy methods available with Software Distribution arefollows:
Method Purpose

ap_def_autopack_file Generates the default AutoPack file of theAutoPack.

ap_def_autopack_host Generates the default source host for theAutoPack. This source host is the managednode on which the AutoPack file resides.

fp_def_excludes Generates the default list of files anddirectories to be excluded from a filepackage.

fp_def_flist Generates the default list of files to beincluded in the file package.

fp_def_nestedlist Generates the default list of nested filepackages and directories to be included in thefile package.

fp_def_options Generates the default options for the filepackage.

fp_def_src_host Generates the default source host for the filepackage.



llply

te

ill

Default Policy Methods for AutoPacksWhen you set or edit an AutoPack default policy, you will see thedefault value in the indicated section of the following dialog.

The following default policy method examples are UNIX Bourne shescripts that set various AutoPack properties. Those scripts that simecho a value are only responsible for setting one file package orAutoPack option.

To set the default AutoPack file for a newly-created AutoPack, creathe following script for theap_def_autopack_file policy method.

#!/bin/shecho /usr/local/autopacks/name.pakexit 0

To set the default source host where all newly-created AutoPacks wreside topescado, create the following script for theap_def_autopack_host policy method:

#!/bin/shecho pescadoexit 0

ap_def_autopack_file

ap_def_autopack_host

3–4 Version 3.6


Policy

he

leingodte

Default Policy Methods for File PackageThe following illustration maps the file package default policymethods to theFile Package Propertieswindow. When you set or edita policy, you will see the default value in the indicated section of tdialog. Note that values set by thefp_def_excludespolicy method arenot available from the desktop.

Note: The file package options available on the platform-specificoptions dialogs are set by thefp_def_options policy.

The following illustration maps the default policy methods to the fipackage definition. If you choose to set file package properties usexport/import, you will see the values set by a default policy methin the indicated section of the exported file package definition. No

fp_def_options

fp_def_src_host

fp_def_flist

fp_def_nestedlist



ll

ge

that the value of thefp_def_src_hostpolicy method is not available inthe file package definition.

The following default policy method examples are UNIX Bourne shescripts that set various file package properties. Those scripts thatsimply echo a value are only responsible for setting one file packaor AutoPack option.

To set the source host tojazz for all newly-created file packages, createthe following script for the fp_def_src_host policy method:

#!/bin/shPATH=/bin:/usr/binecho jazzexit 0

To set therm_empty_dirs, descend_dirs, do_compress, andappend_logkeywords toy and set thekeep_pathskeyword ton, andto set the UNIX destination directory to/staging/fp_name, create thefollowing script for the fp_def_options policy method:

#!/bin/shPATH=/bin:/usr/bin

header

fp_def_options

fp_def_flist

fp_def_nestedlist

fp_def_excludes

3–6 Version 3.6


Policy

fp_name=”$1”cat <<EOFrm_empty_dirs=ydescend_dirs=ykeep_paths=ndo_compress=yappend_log=yunix_platform_prefix=/staging/$fp_nameEOFexit 0

To exclude the/etc/logdirectory,/etc/defaultdirectory, and any file ordirectory namedcore from file packages, create the following scriptfor thefp_def_excludes policy method:

#!/bin/shPATH=/bin:/usr/binecho /etc/logecho /etc/defaultecho coreexit 0

To nest thenew scripts, barcprogs, anddocs file packages in allnewly-created file packages, create the following script for thefp_def_nestedlist policy method:

#!/bin/shPATH=/bin:/usr/bincat <<EOFnew scriptsbarcprogsdocsEOFexit 0

To include the/app/README and/pub/support files in all new filepackages, create this script for thefp_def_flist policy method:

#!/bin/shPATH=/bin:/usr/bincat <<EOF/app/README/pub/supportEOFexit 0


Validation Policy Methods

ckanou

an

re

en

or

k

her

s

icy

s

e

of

Validation Policy MethodsValidation policy methods are called when file package or AutoPaproperties are set or modified. Validation policy also ensures that attempted file package or AutoPack operation is allowed. When ymodify or perform an operation on a file package using theFilePackage Propertieswindow, export/import, the command line, or theDistribute File Package dialog, the file package validation policymethods are invoked. When you modify or perform an operation onAutoPack using theSet AutoPack Properties, Distribute AutoPack,or Remove AutoPackdialog, the AutoPack validation policy methodsare invoked.

Validation policy methods are shell scripts or programs that SoftwaDistribution automatically calls when you perform any of theseactions. Initially, the validation policy methods are not set. Thus, whyou create, modify, or perform an operation on a file package orAutoPack, none of the properties are checked. By creating scriptsprograms and replacing the contents of these validation policymethods, you can control changes to the file package or AutoPacproperties.

Validation policy methods receive as input the proposed value of tfile package or AutoPack property or the attempted file package oAutoPack operation. They returnTRUE if the input passes validationor FALSE if not. For example, Software Distribution always invokethe fp_val_options policy method to verify proposed file packageoptions. If an option does not adhere to the guidelines set by this polmethod, the validation fails and the method returnsFALSE.

TME 10 Software Distribution expects the validation policy methodto exit with the code0 if successful even if the input does not passvalidation. Reserve other error codes for hard errors, such asinsufficient memory, incorrect usage, and so on.

In general, policy methods run in the policy region of the file packagor AutoPack. However, thefp_val_src_host, fp_val_delete_src_host,andap_val_autopack_host_file policy methods run in the policyregion of the source host, which may differ from the policy region the file package or AutoPack.

3–8 Version 3.6


Policy

e
The following validation policy methods are available with SoftwarDistribution:
Method Purpose

ap_val_autopack_host_file Validates the proposed source host andsource file for an AutoPack.

ap_val_name Validates the proposed name when youchange the name of an existing AutoPack.

ap_val_operation Validates the operations performed on theAutoPack.

fp_val_delete_src_host Validates the removal of the source host fora file package. When the source host of afile package is changed from one host toanother, this method first validates theunsetting of the original source host.

fp_val_excludes Validates the files and directories to beexcluded from the file package.

fp_val_flist Validates the files and directories to beincluded in the file package.

fp_val_name Validates the proposed name of the filepackage.

fp_val_nestedlist Validates the nested file packages to beincluded in the file package.

fp_val_operation Validates the operations performed on filepackages.

fp_val_options Validates file package properties.

fp_val_src_host Validates the proposed source host of thefile package.



at

Validation Policy Methods for AutoPacksWhen you set or edit an AutoPack, the validation policy method thcorresponds to that property is invoked.

ap_val_operation

ap_val_autopack_host_file

ap_val_name

ap_val_operation

3–10 Version 3.6


Policy

tory

The following examples provide UNIX shell scripts for variousAutoPack validation policy methods.

To ensure that a newly-created AutoPack does not reside in a direcwith “xyz” in its name, and to ensure that the source host is notpescado, create the following script for theap_val_autopack_host_file policy method:

#!/bin/shLABEL=$1HOST=$2FILEPATH=$3

# Note: it is easier to use grep -q here but the# NT version of grep doesn’t support the -q switch

ignore=`echo $FILEPATH | grep xyz`if [ $? -eq 0 ]; then echo FALSE exit 0fiif [ $HOST = pescado ]; then echo FALSE exit 0fiecho TRUEexit 0

ap_val_operation



the
To ensure that the proposed name of an existing AutoPack containsletters “auto,” create the following script for theap_val_namepolicymethod:
#!/bin/shset +eLABEL=$1NEW_LABEL=$2ignore=`echo $NEW_LABEL | grep auto`if [ $? -eq 0 ]; then echo TRUE else echo FALSEfiexit 0

To ensure that AutoPack files cannot be copied from thebirchmanaged node, create the following script for theap_val_operationpolicy method.

#!/bin/shOPERATION=$1if [ $OPERATION == “COPY” ]; then SRCHOST=$3 if [ $SRCHOST == “birch” ]; then echo FALSE exit 0 fifiecho TRUEexit 0

3–12 Version 3.6


Policy

t

Validation Policy Methods for File PackagesThe following illustrations map the file package validation policymethods to theFile Package Properties window, theRemove FilePackagedialog, and theDistribute File Package dialog. When youset or edit a file package property, the validation policy method thacorresponds to that property is invoked.

fp_val_name

fp_val_src_host

fp_val_nestedlist

fp_val_options

fp_val_del_src_host

fp_val_list



Note: The file package options available on the platform-specificoptions dialogs are validated by thefp_val_options policy.

fp_val_operation

3–14 Version 3.6


Policy

to

The following illustration maps the validation policy methods to thefile package definition. If you choose to set file package propertiesusing export/import, the validation policy method that correspondsa changed property is invoked. Thefp_val_name, thefp_val_operation, thefp_val_delete_src_host, and the

fp_val_operation



e

m

on)he

s

ill

as as

fp_val_src_hostpolicy method are not invoked by changes to the filpackage definition.

The following examples provide UNIX shell scripts and a C prografor various validation policy methods.

To ensure that an attempted operation (except for a commit operatiis valid anytime except for Monday-Friday, 8 a.m. - 5 p. m., create tfollowing script to set thefp_val_operation policy method. Thisscript is invoked at the start of a Software Distribution distribute,distribute and commit, commit, preview, or remove operation.

The script indicates validation failure if the current day and time iswithin this 8 a.m. - 5 p. m.time period. In such a case, the script exitwith a return code of0 and echoesFALSE. The script will also fail ifit is called with the incorrect number of arguments. In this case, it wexit with a return code of0 and echoFALSE.

When this program is called, the name of the file package is passedthe first argument to the program. The type of operation is passedthe second argument.

#!/bin/shexport PATH

header

fp_val_options

fp_val_flist

fp_val_nestedlist

fp_val_excludes

3–16 Version 3.6


Policy

s (so,

ut.e

FP_NAME=$1FP_OP=$2DAY=`date +%w`HOUR=`date +%H`

# Allow a commit operationif [ $FP_OP = “COMMIT” ]; then echo TRUE exit 0fi

# If it’s Sunday or Saturday, return SUCCESSif [ $DAY = 0 ] || [ $DAY = 7 ] ; then echo TRUE exit 0fi

# If the day is Monday-Friday, ensure that the hour is not# between 0800 (8am) and 1700 (5pm)if [ $HOUR -ge 8 ] && [ $HOUR -lt 17 ]; then echo FALSE exit 0fiecho TRUEexit 0

To ensure that the file names in the flist are not longer than eightcharacters and their extensions are no longer that three characterthat they conform to Windows file name conventions, for example)create the following Perl script for thefp_val_flist policy method. Thisscript does not check files contained in directories, commands, orwildcard character file names included in the flist.

When this program is called, the flist is passed through standard inpThe name of the file package is passed as the first argument to thprogram.

#!/usr/local/bin/perlwhile (<STDIN>){ # Truncate override options ($PathName) = split(/\W*\s+\W*/, $_);

# Get the basename of the path $FileName = &Basename($PathName);

# Separate into a filename and an extension ($Name, $Ext) = split(/\./, $FileName); if (length($Name) > 8) { print “FALSE”;



ardt to

ting

xit

orrm

exit(0); } if (length($Ext) > 3) { print “FALSE”; exit(0); }}

# Validation succeeded!print “TRUE”;exit(0);

## Return the basename for the specified path#sub Basename { local($filename) = @_; $filename =~ s#.*/##; $filename;}

To validate the file package optionsdescend_dirs, stop_on_error,andpost_notice, create the following C program for thefp_val_options policy method.

When this program is called, the option list is passed through standinput. The name of the file package is passed as the first argumenthe program.

If the file package does not pass validation, error messages indicathe reason are written to the/tmp/filepackname.err file, FALSE iswritten to standard output, and the program exits with a nonzero ecode. If the file package passes validation,TRUE is written to standardoutput and the program exits with exit code0.

The executable for this program will always run on the TMR server fthe associated policy region, so it should be compiled for that platfotype. The error file will also be created on the TMR server.

#include <sys/types.h>#include <stdio.h>#include <string.h>

typedef struct validate_entry { char *keyword; char *value;} val_entry_t;

val_entry_t validate_table[] = { “descend_dirs”, “y”,

3–18 Version 3.6


Policy

“stop_on_error”, “y”, “post_notice”, “y”};

#define VAL_SIZE(sizeof(validate_table)/sizeof(val_entry_t))#define MAX_LINE 1024char buf[MAX_LINE];#define ERRFILE_PREFIX “/tmp/”#define ERRFILE_EXT “.err”

static voidoutput_bad_keyword(char *fpname, char *keyword, char*bad_val, char *exp_val);

main(argc, argv) int argc; char **argv;{ int i; char *s; char *value_ptr; char *keyword_ptr;

/* Read lines from stdin. Eack keyword/value pair will * be on a new line */

while ((s = gets(buf)) != NULL) { keyword_ptr = buf;

/* Options should always appear in the form: keyword=value * If this line contains a keyword value pair, then

* separate the keyword and value into separate strings */ if ((value_ptr = strchr(buf, ‘=’)) == NULL) {

/* If we didn’t find an equal sign, just skip this line, * we’re not interested in it. */ continue; } *value_ptr++ = ‘\0’; for (i = 0; i < VAL_SIZE; i++) { /* Look through our local table to see if this is a * keyword we want to validate. If so, ensure * it matches our required value */ if ((strcmp(keyword_ptr, validate_table[i].keyword) == 0) &&

(strcmp(value_ptr, validate_table[i].value) != 0)) { /* The option did not match our required value. * Fail the validation */ output_bad_keyword(argv[1], keyword_ptr, validate_table[i].value, value_ptr); printf(“FALSE”); exit(0); } } } /* Everything looks ok */ printf(“TRUE”);



exit(0);}

/* Write to error file indicating which keyword failedvalidation */static voidoutput_bad_keyword(fpname, keyword, bad_val, exp_val) char *fpname; char *keyword; char *bad_val; char *exp_val;{ FILE *err_fd; char *err_fname;

err_fname = (char *)malloc(strlen(fpname) + strlen(ERRFILE_PREFIX) + strlen(ERRFILE_EXT) + 1); if (err_fname == NULL) { return; } sprintf(err_fname, “%s%s%s”, ERRFILE_PREFIX, fpname, ERRFILE_EXT);

if ((err_fd = fopen(err_fname, “w”)) != NULL) { fprintf(err_fd, “Validation failed for file package:%s\n”, fpname); fprintf(err_fd, “ Keyword is: %s\n”, keyword); fprintf(err_fd, “ Expected value is : %s\n”, exp_val); fprintf(err_fd, “ Value in file package is: %s\n”, bad_val ? bad_val : “NULL”); fclose(err_fd); }}

In addition, the following Perl script validates thedo_compress,descend_dirs, log_file, andappend_log file package options:

#!/etc/Tivoli/bin/perl

# FP_VAL_OPTIONS: Validate File Package Options# usage: fp_val_options fp_name < options

# The following associative array defines the keywords# of interest and their required values:%check = ( ’do_compress’, ’y’, ’descend_dirs’, ’y’, ’log_file’, ’fuji:/home/dist/dist_log’, ’append_log’, ’y’,);

# Check usage

3–20 Version 3.6


Policy

file

if ( @ARGV ne 1 ) { die(“usage: fp_val_options fp_name < options\n”);} else { ($fp_name) = @ARGV; # (unused)}

$status = ‘TRUE’;

# Iterate over each line on standard input.# Split each line into keyword and value around the “=”.# If the keyword is present in the check array (as an index),# make sure the value matches the required one as defined# in the array. Otherwise, set the status and exit the# while loop.while ( <STDIN> ) { chop; # discard trailing new line ($keyword, $value) = split(‘=’, $_, 2); if (defined $check{$keyword} && $value ne $check{$keyword} ) { $status = ‘FALSE’; last; }}

print “$status\n”;exit 0;

Validation Policy Methods and TME 10 CommandsValidation policy methods are also invoked when you set or changepackage properties using the command line. The following tabledescribes which commands invoke each validation policy method.

Note: Commands that set or edit AutoPack properties are notavailable; AutoPack policy methods cannot be invoked fromthe command line.

Policy Methods Commands

fp_val_delete_src_host wimprtfp -h

wsetfpattr -h

wsetfpcontents -h


Policy Objects

he

t

For more information on thewcrtfpblock , wdistfp, wimprtfp ,wrmfp , wsetfpattr, wsetfpcontents, wsetfpopts, or wsetfpprgscommand, see Chapter 2, “Commands.” For further information on twcrtprf command, refer to theTME 10 Framework User’s Guide.

Policy ObjectsThe default and validation policy methods that govern theFilePackage andAutoPack resources are defined in a policy defaulobject and a policy validation object. The objects for theFilePackageresource are both calledBasicFilePackage; the objects for the

fp_val_excludesfp_val_flist

wimprtfp

wsetfpcontents -E

wimprtfp

wsetfpcontents -F

fp_val_name wcrtprf

fp_val_nestedlist wimprtfp

wsetfpcontents -N

fp_val_operation wcrtfpblock

wdistfp

wrmfp

fp_val_options wimprtfp

wsetfpopts

wsetfpprgs

fp_val_src_host wimprtfp -h

wsetfpattr -h

wsetfpcontents -h

Policy Methods Commands

3–22 Version 3.6

Policy Objects

Policy

has

e

nd

tothe

ere

se

yg a

AutoPack resource are calledBasicAutoPack. A policy object is a setof policy methods for a specific resource class. Each resource typetwo policy objects that define its default and validation policymethods.

EachBasicFilePackage andBasicAutoPack policy object and thecontained policy methods are provided with Software Distribution.You can, however, create additional policy objects for theFilePackageandAutoPack resources. Multiple policy objects enable you to defindifferent policies that are enforced in different policy regions.

For example, suppose you have two policy regions calledData andSoftware. To create policies that govern the AutoPack operations aproperties in each policy region, you can create separate policyobjects, such asDataAPpolicy andSoftwareAPpolicy. After youdefine the policies in each policy object and link the policy objectsthe policy regions, any newly-created AutoPacks would adhere toguidelines you defined.

To define a new policy object and its policy methods, you mustperform the following procedures:

■ Create a new policy object.

■ Replace the contents of the new policy object methods.

■ Assign the new policy object to the policy region in which the filpackages or AutoPacks will reside or to the policy region whethe file package source host resides.

The following sections provide detailed instructions on each of theprocedures for theAutoPack resource. Use these sections to createnew policies for theFilePackage resource by substituting“FilePackage” for “AutoPack” and by replacing the appropriate policmethod name in each step. This is also true for “Example—SettinDefault Policy Method” on page 3-28. See theTME 10 FrameworkUser’s Guide for detailed information about checking policy in apolicy region.

Creating a New Policy ObjectTo define different policies for multiple policy regions, you mustcreate new policy objects. If you do not define policy for a policy


Policy Objects

sk:

lt

lt

ylar

region, TME 10 Software Distribution uses theBasicFilePackageandBasicAutoPack policy objects and their policy methods by default.

The following table shows the context and role required for this ta

You must use the command line to create a new policy object.

Enter the followingwcrtpol command line to create an AutoPackpolicy default object:

wcrtpol -d AutoPack DataAPpolicy

where:

–d Creates a policy default object.

AutoPack Specifies the resource type of the new policy defauobject.

DataAPpolicy Specifies the name of the new AutoPack policy defauobject.

To create an AutoPack policy validation object, enter the followingcommand:

wcrtpol -v AutoPack DataAPpolicy

where:

–v Creates a policy validation object.

AutoPack Specifies the resource type of the new policyvalidation object.

DataAPpolicy Specifies the name of the new AutoPack policyvalidation object.

After you create a new policy object, you can view the existing policmethods to validate AutoPack properties or operations for a particupolicy region using the following commands:

Activity Context Required Role

Create a new policy object TMR senior or super

3–24 Version 3.6

Policy Objects

Policy

yng

IXor

use

sk:

s

.

wlspolm Lists the policy methods for the specified resource.You can list the default or validation policy methodswith this command.

wgetpolm Retrieves the contents of the specified default orvalidation policy method.

For more information about thewcrtpol , wlspolm, and wgetpolmcommands, see theTME 10 Framework Reference Manual.

Replacing the Contents of a Policy MethodTo define different policies from those inherited by the parent policobject, you must create a script or program and replace the existipolicy method with it.

Note: Policy methods run on managed nodes and thus must be UNor NT scripts, programs, or executables. Use UNIX scriptsprograms on UNIX managed nodes. Use.BAT, .EXE, or.COM files, in addition to UNIX scripts or programs if thenecessary tools are available, on the NT machine. Do not C shell scripts.


You must use the command line to replace the content of a policymethod.

Enter the followingwputpolm command line to replace the contentof theap_def_autopack_file policy method with the contents of theData_def_file.sh script:

wputpolm -d AutoPack DataAPpolicy ap_def_autopack_file \< Data_def_file.sh

where:

-d Specifies that the method is a policy default method


Replace the content of apolicy method

TMR senior or super


Policy Objects

ts

d.

ts

AutoPack Specifies theAutoPack resource type for which thepolicy is defined.

DataAPpolicy Specifies theDataAPpolicy policy object thatcontains the default policy method being replaced.

ap_def_autopack_fileReplaces the contents of theap_def_autopack_filedefault policy method.

< Data_def_file.shRedirects theData_def_file.shscript to the command.The contents of this file replace the existing contenof theap_def_autopack_file policy method.

To replace the contents of theap_val_autopack_host_file policymethod with the contents of theData_val_file.sh script, enter thefollowing command:

wputpolm -v AutoPack DataAPpolicy ap_val_autopack_host_file< Data_val_file.sh

where:

-v Specifies that the method is a policy validationmethod.


DataAPpolicy Specifies theDataAPpolicy policy object thatcontains the validation policy method being replace

ap_val_autopack_host_fileReplaces the contents of theap_val_autopack_host_file validation policymethod.

< Data_val_file.shRedirects theData_val_file.shscript to the command.The contents of this file replace the existing contenof theap_val_autopack_host_file policy method.TheData_val_file.shfile must reside in the directoryfrom which you call thewputpolm command.

3–26 Version 3.6

Policy Objects

Policy

ct

sk:

icy

For more information about thewputpolm command, see theTME 10Framework Reference Manual.

Assigning Policy to a Policy RegionTo change the default policy for a policy region, you must assignpolicy to the policy region after you have created a new policy objeand replaced policy methods.


You can use the desktop or command line to assign policy to a polregion. See theTME 10 Framework User’s Guide for instructions touse the desktop.

To use thewsetpr command to change the default policy in theDatapolicy region to those methods defined in theDataAPpolicy policyobject, enter the following command:

wsetpr -d DataAPpolicy AutoPack @PolicyRegion:Data

where:

–d DataAPpolicyChanges the default policy to that defined in theDataAPpolicy object.


@PolicyRegion:DataSpecifies theData policy region for which to assignthe policy.


Assign policy to a policyregion

Policy Region senior or super


Example—Setting a Default Policy Method

n

wfor

”.

re

To use the command line to change the validation policy in theDatapolicy region to those methods defined in theDataAPpolicy policyobject, enter the following command:

wsetpr -v DataAPpolicy AutoPack @PolicyRegion:Data

where:

–v DataAPpolicyChanges the validation policy to that defined in theDataAPpolicy object.


@PolicyRegion:DataSpecifies theData policy region for which to assignthe policy.

For more information about thewsetpr command, see theTME 10Framework Reference Manual.

Example—Setting a Default Policy MethodThe following example provides the complete command line solutioof how to set the file package policy default for thebackup_fmt andappend_logkeywords, and how to create and assign policy to a nefile package policy object. Use these sections to create new policiestheAutoPack resource by substituting “AutoPack” for “FilePackageand by replacing the appropriate policy method name in each step

1. List the policy default methods for theFilePackage class byentering the following command from a root prompt:

wlspolm -d FilePackage

where:

–d Lists the policy default methods for theFilePackage resource type.

FilePackage Specifies the resource whose policy methods ato listed.

3–28 Version 3.6


Policy

e

ied

The following default policies are returned:

fp_def_excludesfp_def_flistfp_def_nestedlistfp_def_optionsfp_def_src_host

The fp_def_options policy method is used to set file packageoptions (keywords).

2. List the policy default objects that exist for theFilePackageclass. TME 10 supports multiple policy default and validationobjects so that, for example, you can have one set of policyobjects in policy regionX and a different set in policy regionY.Use the following command to list the policy default objects:

wlspol -d FilePackage

where:

–d Lists the policy default objects for theFilePackage resource type. (To list the policyvalidation objects, use the–v argument.)

FilePackage Specifies the resource whose policy objects arto listed.

This command returns only theBasicFilePackage object if youhave not created additional policy default objects.

3. Extract the current contents of thefp_def_optionspolicy defaultmethod to make sure that another administrator has not modifit.

wgetpolm -d FilePackage BasicFilePackagefp_def_options

where:

–d Lists the contents of thefp_def_options policydefault method.

FilePackage Specifies theFilePackageresource whose policyis to be returned.



e

uthe

BasicFilePackageSpecifies theBasicFilePackage policy objectwhose policy is to be returned.

fp_def_optionsSpecifies the policy method whose contents arto be returned.

The contents of this policy method are output to standard outpby default. If the previous command does not return anything, tpolicy method is not set.

4. Create a script that sets thebackup_fmt keyword. The followingscript, called/tmp/options.sh, accomplishes this and sets thelog_file keyword.

#!/bin/shcat <<EOFbackup_fmt=/backups/%p/%f.%nlog_file=/dist_logs EOFexit 0

5. Replace the contents of thefp_def_options policy method withthe new script using the following command:

wputpolm -d FilePackage BasicFilePackage \fp_def_options </tmp/options.sh

where:

–d Specifies that thefp_def_optionspolicy methodis a default policy method.

FilePackage Specifies theFilePackageresource for which thepolicy is set.

BasicFilePackageSpecifies theBasicFilePackagepolicy object forwhich the policy is set.

fp_def_optionsSpecifies thefp_def_options policy methodwhose contents are to be replaced.

3–30 Version 3.6


Policy

e

</tmp/options.shRedirects the/tmp/options.sh script to thecommand. This command reads its input fromstandard input.

6. Associate the new policy method in theBasicFilePackagepolicyobject with theSource policy region:

wsetpr -d BasicFilePackage FilePackage \@PolicyRegion:Source

where:

–d BasicFilePackageChanges the default policy to that defined in thBasicFilePackageobject.

FilePackage Specifies theFilePackage resource type forwhich the policy is defined.

@PolicyRegion:SourceSpecifies to change the policy for theSourcepolicy region.

After setting the policy, every file package created in policyregions whose default policy for theFilePackage resource typeis set toBasicFilePackage will have thebackup_fmt andlog_file keywords set as specified in the sample script.


Policy Methods

on

deicyd.ee

Policy MethodsThe following default and validation policy methods enable you tocontrol resources and to maintain guidelines when resources aremodified or operated on. These methods can differ from policy regito policy region. That is, one policy region could have one set ofvalidation policy methods and another policy region could haveanother.

Note: The authorization roles listed for each policy method incluthe roles required to perform the action that calls each polmethod, not the role required to create or edit a policy methoFor the authorization roles required to create or edit policy, sthe roles listed for thewcrtpol , wgetpolm, andwputpolmcommands.

3–32 Version 3.6


Policy

s.

ed

oli

t,

NAME


PURPOSE

Generates the default AutoPack file of all newly-created AutoPack

SYNOPSIS

ap_def_autopack_fileap_name

RESOURCE

AutoPack

DESCRIPTION

This method generates the default AutoPack file of all newly-creatAutoPacks. The value displayed in thePath field on theSet AutoPackProperties dialog is the returned value of this method.

Authorization

senior or super

Arguments

ap_name The name of the AutoPack.

Exit Status

Though you can specify any exit code in your policy methods, Tivrecommends that you use the following codes:

E_OK Successful completion.

E_USAGE The method encountered an illegal option, argumenor parameter.

E_FAIL The method failed due to an error.

SEE ALSO




.

here

li

t,

NAME


PURPOSE

Generates the default source host where the AutoPack will reside

SYNOPSIS

ap_def_autopack_hostap_name

RESOURCE

AutoPack

DESCRIPTION

This method generates the default source host, a managed node, wthe newly-created AutoPack will reside. The value displayed in theSource Host field on theSet AutoPack Properties dialog is thereturned value of this method.

Authorization

senior or super

Arguments


Exit Status

Though you can specify any exit code in your policy methods, Tivorecommends that you use the following codes:




SEE ALSO


3–34 Version 3.6


Policy

ck.

t (a

ck

e

NAME


PURPOSE

Validates the proposed source host and AutoPack file of an AutoPa

SYNOPSIS

ap_val_autopack_host_fileap_name src_host src_file

RESOURCE

AutoPack

DESCRIPTION

This method validates the proposed AutoPack file and source hosmanaged node) of a newly-created AutoPack. Theap_val_autopack_host_file method runs in the source host’s policyregion and is invoked when an administrator saves the AutoPackproperties specified on theSet AutoPack Properties dialog.

This method must have an exit status of0 and writeTRUE to standardoutput. Otherwise, validation is considered unsuccessful.

Authorization


Arguments


src_host The name of the managed node where the AutoPafile specified by thesrc_file argument resides.

src_file The full path where the AutoPack’s file resides on thsource host.

RETURNS

Output

Theap_val_autopack_host_file method should write the followingstrings to standard output:



li

t,

TRUE Successful validation.

FALSE Failed validation.

Exit Codes


E_OK Successful completion. UseE_OK even if the outputis FALSE; this exit code indicates that the policymethod ran successfully.



SEE ALSO


3–36 Version 3.6

ap_val_name

Policy

kichod

ed.

NAME

ap_val_name

PURPOSE

Validates the proposed name of an AutoPack.

SYNOPSIS

ap_val_nameold_name new_name

RESOURCE

AutoPack

DESCRIPTION

This method validates the new name specified by thenew_nameargument given to the AutoPack specified by theold_nameargument.Theap_val_namemethod is invoked when the name of the AutoPacis changed. It is also invoked when an AutoPack is created, in whcase there is no old name so the new name is passed to the methtwice.


Authorization


Arguments

old_name The name of the AutoPack whose name was chang

new_name The new name being validated.

RETURNS

Output

Theap_val_name method should write the following strings tostandard output:




ap_val_name

li

t,

Exit Codes





3–38 Version 3.6

ap_val_operation

Policy

orofs is

the

anul,nline.

NAME

ap_val_operation

PURPOSE

Validates the AutoPack operation.

SYNOPSIS

ap_val_operation{ DISTRIBUTE | REMOVE } name

ap_val_operation COPY name src_host src_file dest_host dest_file

RESOURCE

AutoPack

DESCRIPTION

This method validates an AutoPack operation—distribute, removal,copy. It is called when an AutoPack operation is attempted. The listtarget PC managed nodes for the distribute and remove operationavailable to this method through standard input, with each PCmanaged node or NT managed node listed on a line by itself. Notesynopsis statements above; only thename argument is present if youare distributing or removing the AutoPack.

The copy operation calls this method when an administrator movesAutoPack from one location to another. If validation is not successfthe operation will not occur. There is no list of targets for this operatiobecause the source and destination are provided on the command


Authorization


Arguments

DISTRIBUTE | REMOVE | COPYThe operation to be performed on the AutoPack.

name The name of the AutoPack that is the subject of theoperation being validated.


ap_val_operation

PCe

ande.

li

t,

src_host The host from which the AutoPack is being copied.The source host can be either a managed node or amanaged node. This argument is present only for thCOPY operation.

src_file The AutoPack being copied. The source AutoPack creside on either a managed node or PC managed noThis argument is present only for theCOPYoperation.

dest_host The managed node to which the AutoPack is beingcopied. This argument is present only for theCOPYoperation.

dest_file The name of the AutoPack on the destination hostwhere the AutoPack file is being copied. Thisargument is present only for theCOPY operation.

RETURNS

Output

Theap_val_operation method should write the following strings tostandard output:



Exit Codes





3–40 Version 3.6

fp_def_excludes

Policy

ile

dsetine.

oli

t,

le

NAME

fp_def_excludes

PURPOSE

Generates the default files and directories to be excluded from a fpackage.

SYNOPSIS

fp_def_excludes

RESOURCE

FilePackage

DESCRIPTION

This method generates a list of files and directories to be excludefrom the file package and outputs it to standard output. When youthe files and directories to be excluded, you must list them one per l

Authorization

senior or super

Exit Status





SEE ALSO

fp_val_excludes

See Chapter 1, “File Package Definitions” for more information on fipackage definition format.


fp_def_flist

the

inhe.

li

t,

le

NAME

fp_def_flist

PURPOSE

Generates the default list of files and directories to be included in file package.

SYNOPSIS

fp_def_flist

RESOURCE

FilePackage

DESCRIPTION

This method generates the list of files and directories to be includedthe file package and outputs it to standard output. When you set tfiles and directories to be included, you must list them one per line

Authorization

senior or super

Exit Codes





SEE ALSO

fp_val_flist


3–42 Version 3.6

fp_def_nestedlist

Policy

d inhe

oli

t,

le

NAME

fp_def_nestedlist

PURPOSE

Generates the default list of nested files to be included in the filepackage.

SYNOPSIS

fp_def_nestedlist

RESOURCE

FilePackage

DESCRIPTION

This method generates the list of nested file packages to be includethe file package and outputs it to standard output. When you set tvalue of this method, list each file package, one per line.

Authorization

senior or super

Exit Codes





SEE ALSO

fp_val_nestedlist



fp_def_options

tondch

li

t,

le

NAME

fp_def_options

PURPOSE

Generates the default options for the file package.

SYNOPSIS

fp_def_options

RESOURCE

FilePackage

DESCRIPTION

This method generates the file package options and outputs themstandard output. These options include logging, file permission, ageneral distribution. When you set the values of this method, list eaon a separate line in the form ofkeyword=value.

Authorization

senior or super

Exit Codes





SEE ALSO

fp_val_options


3–44 Version 3.6

fp_def_src_host

Policy

putsust

oli

t,

le

NAME

fp_def_src_host

PURPOSE

Generates the default source host for the file package.

SYNOPSIS

fp_def_src_host

RESOURCE

FilePackage

DESCRIPTION

This method generates the source host for the file package and outit to standard output. When you set the value of this method, you mspecify a valid managed node name.

Authorization

senior or super

Exit Codes





SEE ALSO

fp_val_src_hostand fp_val_delete_src_host



fp_val_delete_src_host

od,st

e

l

NAME


PURPOSE

Validates the removal of the source host for a file package.

SYNOPSIS

fp_val_delete_src_hostfp_name src_host

RESOURCE

FilePackage

DESCRIPTION

This method validates that an administrator can change (therebyremoving) the source host, as specified by thesrc_hostargument, of anexisting file package, as specified by thefp_nameargument. It is calledwhen the source host for a file package is changed. Use this methfor example, to enforce a restriction that a certain file package muhave a specific host as its source host.


Authorization


Arguments

fp_name The name of the file package whose source host ischanged (removed).

src_host The name of the managed node that is currently thsource host for the file package. If no source host iscurrently specified for the file package, this value wilbeNO_SOURCE_HOST.

3–46 Version 3.6


Policy

oli

t,

le

RETURNS

Output

The fp_val_delete_src_host method writes the following strings tostandard output:



Exit Codes





SEE ALSO

fp_def_src_hostand fp_val_src_host



fp_val_excludes

ge.

d

e.ane

pty

e

NAME

fp_val_excludes

PURPOSE

Validates the files and directories to be excluded from a file packa

SYNOPSIS

fp_val_excludesfp_name

RESOURCE

FilePackage

DESCRIPTION

This method validates the list of files and directories to be excludefrom the file package specified by thefp_name argument. Use thismethod to control the list of files to be excluded from the file packagWhen a file package property such as the contents, an option, or excluded file is changed, this method and these listed methods arinvoked:

fp_val_flist

fp_val_nestedlist

fp_val_options

fp_val_src_host

The list of files to be excluded is available to the method throughstandard input. The files are listed one per line. This list can be emif there are no files to be excluded.


Authorization


Arguments

fp_name The name of the file package for which the files to bexcluded are validated.

3–48 Version 3.6

fp_val_excludes

Policy

oli

t,

le

RETURNS

Output

The fp_val_excludesmethod writes the following strings to standardoutput:



Exit Codes





SEE ALSO

fp_val_flist, fp_val_nestedlist, fp_val_options, fp_val_src_host



fp_val_flist

ing

ts,d

NAME

fp_val_flist

PURPOSE

Validates the files and directories to be included in a file package.

SYNOPSIS

fp_val_flist fp_name

RESOURCE

FilePackage

DESCRIPTION

This method validates the files, directories, and commands describthe contents to be included in the file package as specified by thefp_nameargument. When a file package property such as the contenan option, or an excluded file is changed, this method and the listemethods are invoked:

fp_val_excludes

fp_val_nestedlist

fp_val_options

fp_val_src_host

The list of files, directories, or commands are provided throughstandard input, one per line.


Authorization


Arguments

fp_name The name of the file package whose contents arevalidated.

3–50 Version 3.6

fp_val_flist

Policy

li

t,

le

RETURNS

Output

The fp_val_flist method writes the following strings to standardoutput:



Exit Codes

Although you can specify any exit code in your policy methods, Tivorecommends that you use the following codes:




SEE ALSO

fp_val_excludes, fp_val_nestedlist, fp_val_options,fp_val_src_host



fp_val_name

nt.thet set

NAME

fp_val_name

PURPOSE

Validates the proposed name of a file package.

SYNOPSIS

fp_val_namefp_name new_name

RESOURCE

FilePackage

DESCRIPTION

This method validates the new name specified by the new_nameargument given to the file package specified by the fp_name argumeThis method is invoked when the file package is created or when name of the file package is changed. Note that this method does nothe default name.


Authorization

senior or super

Arguments

fp_name The name of the file package whose name waschanged.

new_name The new name being validated.

RETURNS

Output

The fp_val_name method writes these strings to standard output:



3–52 Version 3.6

fp_val_name

Policy

oli

t,

le

Exit Codes





SEE ALSO



fp_val_nestedlist

.

file

ilele is

tedty.

e

NAME

fp_val_nestedlist

PURPOSE

Validates the nested file packages to be included in a file package

SYNOPSIS

fp_val_nestedlistfp_name

RESOURCE

FilePackage

DESCRIPTION

This method validates the nested file packages to be included in thepackage specified by thefp_nameargument. Use this method tocontrol the list of nested file packages for the file package. When a fpackage property such as the contents, an option, or an excluded fichanged, this method and these listed methods are invoked:

fp_val_excludes

fp_val_flist

fp_val_options

fp_val_src_host

The list of nested file packages to be included is available to thismethod through standard input. Each file package to be nested is lison a line by itself. If no file packages are to be nested, this list is emp


Authorization


Arguments

fp_name The name of the file package for which the nested filpackage to be included are validated.

3–54 Version 3.6

fp_val_nestedlist

Policy

oli

t,

le

RETURNS

Output

Thefp_val_nestedlistmethod writes the following strings to standardoutput:



Exit Codes





SEE ALSO

fp_val_excludes, fp_val_flist, fp_val_options, fp_val_src_host



fp_val_operation

,ndes ise isn

e

NAME

fp_val_operation

PURPOSE

Validates the file package operations.

SYNOPSIS

fp_val_operation fp_name fp_operation

RESOURCE

FilePackage

DESCRIPTION

This method validates a file package operation, such as distributedistribute and commit, commit, preview, or removal. It is called whea file package operation is attempted. The list of target managed noand PC managed nodes on which the operation will be performedavailable to this method through standard input. Each managed nodlisted on a line by itself. If validation is not successful, the operatiowill not occur.


Authorization


Arguments

fp_name The name of the file package that is the subject of thoperation being validated.

fp_operation The file package operation, modified by thedistribution type, which determines what kind ofdistribution takes place (see thewdistfp command ortheDistribution Options dialog box in theDistributeFile Packagedialog in the GUI). Distribution optionsonly pertain to theDIST, DIST_AND_COMMIT

3–56 Version 3.6

fp_val_operation

Policy

t:

oli

t,

le

andPREVIEW file package operation options. Thepossible file package operations are:

COMMITDIST:ALLDIST:ANY_CHANGESDIST:SOURCE_CHANGESDIST_AND_COMMIT:ALLDIST_AND_COMMIT:ANY_CHANGESDIST_AND_COMMIT:SOURCE_CHANGESPREVIEW:ALLPREVIEW:ANY_CHANGESPREVIEW:SOURCE_CHANGESREMOVE

RETURNS

Output

The fp_val_operationmethod writes these strings to standard outpu



Exit Codes





SEE ALSO

wdistfp



fp_val_options

.ane

ut,

tedtain

NAME

fp_val_options

PURPOSE

Validates file package options.

SYNOPSIS

fp_val_options fp_name

RESOURCE

FilePackage

DESCRIPTION

This method validates the options that are set for the file packageWhen a file package property such as the contents, an option, or excluded file is changed, this method and these listed methods arinvoked:

fp_val_excludes

fp_val_flist

fp_val_nestedlist

fp_val_src_host

The list of options is available to the method through standard inpeach listed on a line by itself in the formatfp_keyword=value.

Use this policy method, for example, to ensure that log files are creaon certain managed nodes. You can also prevent distributions to certargets or ensure that file packages are not removed using thefp_val_options method.


Authorization

senior or super

3–58 Version 3.6

fp_val_options

Policy

oli

t,

le

Arguments

fp_name The name of the file package whose options arevalidated.

RETURNS

Output

The fp_val_options method writes the following strings to standardoutput:



Exit Codes





SEE ALSO

fp_val_excludes, fp_val_flist, fp_val_nestedlist, fp_val_src_host



fp_val_src_host

eed,

file

NAME

fp_val_src_host

PURPOSE

Validates the proposed source host of a file package.

SYNOPSIS

fp_val_src_hostfp_name src_host

RESOURCE

FilePackage

DESCRIPTION

This method validates the new source host specified by thesrc_hostargument for the file package specified byfp_name. It is called whenthe source host for a file package is changed. When a file packagproperty such as the contents, an option, or an excluded file is changthis method and these listed methods are invoked:

fp_val_excludes

fp_val_flist

fp_val_nestedlist

fp_val_options

Use this method, for example, to enforce a restriction that a certainpackage must have a specific host as its source host.


Authorization


Argument

fp_name The file package name whose source host waschanged.

src_host The name of the managed node being validated.

3–60 Version 3.6

fp_val_src_host

Policy

d

oli

t,

le

RETURNS

Output

The fp_val_src_host method writes the following strings to standaroutput:



Exit Codes


E_OK Successful completion.UseE_OK even if the outputis FALSE; this exit code indicates that the policymethod ran successfully.



SEE ALSO

fp_def_src_host, fp_val_delete_src_host, fp_val_excludes,fp_val_flist, fp_val_nestedlist, fp_val_options



fp_val_src_host

3–62 Version 3.6

Configuration P

rograms

antly,

the

ns.tem a

ftergen.

s

ly

arearest

4Configuration Programs

Deploying client/server application software often involves more thsimply distributing files and directories to target machines. Frequenthe application requires configuration, which can be as simple assupplying a license key or as complex as stopping and restarting server daemon to change the database schema.

TME 10 Software Distribution enables you to specify configurationprograms that are run at various points during file package operatioThese programs run either on the source host or on the client sysbefore or after a file package distribution. Specifically, you can runconfiguration program before a distribution on the source host ortarget, after a distribution on the source host or target, before and aremoving a file package on the target, upon commit of the file packaon the target, or if an error stops a distribution or removal operatio

For a file package, you can specify multiple configuration programfor each target (and platform-type). Specify target configurationprograms using the desktop, command line, or with the export andimport capability. Specify source before or after programs using onthe command line or the export and import capability. See theTME 10Software Distribution User’s Guide for detailed information aboutsetting source and target configuration programs.

This chapter discusses how the program arguments and input filesprocessed, and describes limitations of programs written for NetWsystems (NLMs). It also provides many example programs to assiyou in your file package operation.

4


Processing Command Line Arguments

se

u toafter

re

nd

by

to

Processing Command Line ArgumentsWhen Software Distribution runs a configuration program, it passecommand line arguments to the program to specify the file packagoperation in progress. These command line arguments enable yodesignate, for example, the same program as both the before andprogram. This program is created to accomplish different thingsdepending on whether it is run before or after a distribution. SoftwaDistribution passes command line arguments to configurationprograms in the same way that commands invoked from the commaline are passed their arguments. Currently, Software Distributionpasses the following parameters to a configuration program:

■ A literal string describing the configuration program type.

■ The path to the input file, as specified in theyyy_xxx_input_pathkeywords. If an input file is not specified, aNULL literal stringis passed.

■ A literal string value of theams_inst_sw_comp_handlekeyword. This keyword specifies the AMS Installed SoftwareComponent Handle, which identifies the installed softwarecomponent handle that is created for the software componentthe Tivoli Developer’s Toolkit. For more information about thiskeyword, see the manual page for thewsetfpopts command inChapter 2, “Commands.”. If a value is not specified for thiskeyword, aNULL literal string is passed.

For example, if you set the following keywords in a file packagedescription:

unix_after_prog_path=”/tmp/user_conf_prog.sh”unix_after_input_path=”/tmp/user_conf_prog.in”ams_inst_sw_comp_handle=

Software Distribution will spawn anafter configuration program withthe following arguments:

/tmp/user_conf_prog.sh after /tmp/user_conf_prog.in NULL

It is possible that in future releases Tivoli will add other parametersSoftware Distribution configuration programs. Therefore, Tivolistrongly recommends that configuration programsnotperform a check

4–2 Version 3.6

Processing Input Files Configuration P

rograms

o

meas.youentnd

put.,

eh tothe

m.

s

turem

for the exact number of parameters that are passed. If you need tcheck for missing arguments in a configuration program, Tivolirecommends the following script:

if [ $# -lt 3 ]; then echo “Missing arguments” exit 1fi

Processing Input FilesBecause you can specify multiple configuration programs of the satype, you can also specify multiple input files, separated by commThe programs and input files are processed in the order in which specify them. If a program does not require an input file but subsequprograms do, you must specify the input files in the correct order apreceded by the same number of commas as the programs.

When the source or target configuration programs run on UNIXmachines, the input files (if specified) are processed as standard inBecause standard input is handled differently across PC platformstarget configuration programs that run on a DOS, NetWare, OS/2,Windows, Windows 95, or Windows NT platform do not receive thinput files as standard input. Rather, the programs receive the patthe input file as a second command line argument, as described inprevious section.

Return Codes of Configuration ProgramsSoftware Distribution writes the return status of each configurationprogram to the log file specified by theLog Information Optionssection of theFile Package Propertieswindow. This return status asreported in the log file is not the same as the exit status of the progra

UNIX Configuration ProgramsFor configuration programs run from a UNIX host, the return statuwritten to the log file is reported according to the semantics of thewaitsystem call. These semantics can vary depending on the architectype of the host (source or target) from which a configuration progra


Return Codes of Configuration Programs

ram

on

f

t.s toith

t

is running, as specified by thesrc_program_prog_path andunix_program_prog_path keywords. For example, if the log file states:

script complete: status=400

and the source host were an HP machine, the exit status of the progwould be4 if the src_program_prog_path keyword was set.

See the system documentation of the source host for information thewait system call.

NetWare Configuration ProgramsTo specify configuration programs for NetWare targets, you mustdevelop NetWare loadable modules (NLMs). However, because otechnical limitations in the NetWare NLM software developer’s kit(SDK), you cannot pass a return code from a child NLM to its parenTo remedy this problem, the PC agent exports a symbol that refera function call within the agent. This function sets the return code wthe agent before it returns. The following code example shows theprototype for theSetErrorCode function:

int SetErrorCode (int error_code);

To avoid compiler warnings, include theSetErrorCode prototype inthe source file from which it is called. The following code fragmenshows how to integrate the function into an NLM:

#include “...” . . .int SetErrorCode (int error_code); . . .main (){int ec; . . . return (SetErrorCode(ec));}

4–4 Version 3.6

PC Environment Space Configuration P

rograms

n

r

d

After you modify the NLM to call theSetErrorCode function, youmust link the NLM and use animport linker directive to resolve thesymbol as follows:

import SetErrorCode

Note: Consult your compiler documentation for more information ohow to use theimport directive.

If you specified an input file for one of the before, after, removal, ocommit NLMs, you must open the specified input file as part of theNLM’s processing.

PC Configuration ProgramsFor .EXE, .COM , and.CMD configuration programs run on PCs,return codes other than0 (indicate successful completion) are reporteaccording to those included in theERROR.TIV file in theTEMPdirectory. If the configuration program is a.BAT file, you must use thewseterr command to return an error code.

See Chapter 2, “Commands” for information on thewseterrcommand.

PC Environment SpaceWhen a configuration program runs on a PC, it can exhaust theenvironment space if the program sets environment variables.Suppose, for example, the configuration program sets theTEMP, TZ ,MOUSE, andPATH variables and invokes theMYCMD command(resides in the\TOOLS\BIN directory), as follows:

set TEMP=C:\TEMPset TZ=CST6CDTset MOUSE=C:\MOUSEset PATH=%PATH%;C:\TOOLS\BIN;C:\WORD\EXCELMYCMD -i TOOLS\BIN -d cexit 0

When the program runs, it sets theTEMP andTZ variables then runsout of environment space. Hence, theMOUSE andPATH variablesare not set. When the program then tries to run theMYCMDcommand, it cannot because thePATH variable is not set correctly.


UNIX Example Scripts

to

heou

u

tion

If a program cannot find a command, you can specify the full paththe command. Thus, in the previous program, you could specifyC:\TOOLS\BIN\MYCMD instead of simplyMYCMD . You can alsoincrease the environment space by editing the following line in theCONFIG.SYS file:

SHELL=C:\COMMAND.COM C:\ /P /E:1536

where/E:1536 reserves 1536 bytes for environment space.

UNIX Example ScriptsUse the following Bourne shell scripts to reboot a target after adistribution, remove files from a destination directory, and change tpermissions of a log file. Although these are Bourne shell scripts, ycan implement configuration programs as Perl scripts, Korn shellscripts, or compiled executables.

These example scripts are available by using anonymousftp fromftp.tivoli.com . Connect to theftp.tivoli.com site to access scripts inthe/pub/support/courier/2.5directory. TheREADME.txt file in thisdirectory describes which file corresponds to which example. If yoare unfamiliar with anonymousftp or do not have Internet access,contact your Tivoli support provider for a copy of the programs.

Rebooting After a File Package DistributionUse the following script as a target after program to reboot a targeafter a file package is successfully distributed. Because the distributmust successfully complete, you cannot reboot the machineimmediately after the distribution. You must schedule the reboot toallow the file package distribution to finish. Also, if you enable theStop distribution on error option (thestop_on_error keyword) ofthe file package, this program will not run on a target, unless thedistribution was completely successful.

If you create this script and name it/usr/bin/reboot_bfr.sh, you canspecify it for theGNU Emacs file package as follows:

wsetfpprgs -T unix -a /usr/bin/reboot_bfr.sh @"GNU Emacs"

4–6 Version 3.6

UNIX Example Scripts Configuration P

rograms

he

ush to

it

gh

This script requires root permissions so that it can submit UNIXatjobs. Root must not be listed in the/usr/lib/cron/at.deny file. Also, theunix_before_as_uid keyword must not be set so that this afterprogram runs as root, thereby allowing theodadmin call to succeed.

#!/bin/sh

echo "/etc/reboot now >/dev/null 2>&1" | at no w + 5 minutes>/dev/null 2>&1

exit 0

Note: Consult your system documentation for information about treboot command, such as where it resides and its validarguments. This script will run on SunOS machines (thereboot command resides in the/etc directory).

Removing Files from the Destination DirectoryUse the following target before program to remove everything in adirectory to which an application will be distributed. This script isuseful if you want to ensure that the destination directory of adistribution is completely empty and nothing remains from a previodistribution. This script also ensures that the components of the patthe destination directory are available and that the path is not/ (root).Thus, if you created this before program on the target and named/usr/bin/before.sh, you can specify it for theGNU Emacs filepackage using the followingwsetfpprgs command:

wsetfpprgs -T unix -b /usr/bin/before.sh @"GNU Emacs"

This before program assumes that theprog_env keyword is set asfollows. If so, the components of the path should be available throuthe environment variables set by Software Distribution.

prog_env="default_dir=$default_dest \unix_dest_dir=$unix_platform_prefix"

You must set theprog_envkeyword for theGNU Emacsfile packageby using export/import or thewsetfpopts command.

wsetfpopts -T gen -E \"unix_dest_dir="\$"unix_platform_prefix \default_dir="\$"default_dest" @"GNU Emacs"



t

isis

Create the script as follows:

#!/bin/sh

DEST_DIR=$unix_dest_dir/$default_dircd $DEST_DIRCWD=`pwd`

if [ "$CWD" = "/" ]then # # The destination is the root directory! # Do not want to remove everything under here. # exit 1fi

## Remove the old version of the application to be# distributed. A file package removal performed on the file# package for the previous version should remove everything.# However,remove everthing as a safeguard in case someone# forgot to do that.#cd ..rm -rf $DEST_DIR

exit 0

Running an Installation Script After a DistributionUse the following Bourne shell script as a UNIX after program tharuns the installation script provided with the application in a filepackage. If you create this script and name it/usr/bin/install_aft.sh,you can specify it for theGNU Emacsfile package using the followingcommand:

wsetfpprgs -T unix -a /usr/bin/install_aft.sh @"GNU Emacs"

Because the installation script is distributed with the file package, thprogram runs the script directly from the destination directory. For thprogram to function correctly, theprog_env keyword of the filepackage must define the following:

■ TheU_PATH variable, which is the UNIX platform prefixdefined for the file package

■ TheD_PATH variable, which is the default destination definedfor the file package

4–8 Version 3.6

UNIX Example Scripts Configuration P

rograms

.

file

■ TheSERVER environment variable, which is set to the hostname of the machine where the application server is running

Therefore, use the following command to set theprog_env keywordfor the file package:

wsetfpopts -T gen -E "U_PATH="\$"unix_platform_prefix \D_PATH="\$"default_dest SERVER=corp.com" @example_fp


#!/bin/sh

# Set the name of the installation script. According to# TME 10 Software Distribution behavior, the installation# path is constructed by combining the "platform prefix" (if# set) with the "default destination" (if set).#APPINST=$U_PATH/$D_PATH/bin/appinst.sh

# The application installation script takes one command# argument which is the hostname of the application server.# This is passed as the only argument upon invocation. The# script is also interactive, expecting answers to the# following questions:## 1) What is the full path where the application has been# installed?# 2) Is this an upgrade from a previous release? [y or n]# 3) Should a full or partial install be performed? [full or# partial]# 4) Should the application daemon be started automatically# upon system reboot? [y or n]## The correct answers are provided by a "shell here# document" specified in this script.#$APPINST $SERVER << app_after_script$D_PATHnfullnapp_after_script

exit $?

Checking the Architecture TypeUse the following Bourne shell script as a UNIX before program toverify that a target managed node is a valid architecture type for thepackage. If so, the program exits0 and the distribution continues. If



tot:

es

s

not, it exits non-zero and the distribution is not performed. For thisfunction correctly, the following file package properties must be se

■ Theunix_before_skip_non_zero keyword is set toy.

■ Theprog_env keyword must define theTARGET environmentvariable as the TME 10 interpreter type of the valid architecturfor the file package. See theTME 10 Framework Planning andInstallation Guidefor a current list of supported interpreter typefor this release.

■ Theunix_before_as_uid keyword must not be set so that thisbefore program runs as root, thereby allowing theodadmin callto succeed.

To set theprog_envkeyword, use the followingwsetfpoptscommandto set theTARGET variable for an HP-UX 10.0 machine:

wsetfpopts -T gen -E "TARGET=hpux10" @example_fp

If you create this script and name it/usr/bin/charch_bfr.sh, use thefollowing wsetfpprgs command to specify it for theexample_fp filepackage:

wsetfpprgs -T unix -b /usr/bin/charch_bfr.sh @example_fp


#!/bin/sh

PATH=/bin:/usr/bin:$PATHexport PATH

ARCH=`odadmin | grep "Interpreter type" |awk '{print\$NF}'`

if [ x"$ARCH" = x"$TARGET" ] ; then exit 0elseecho "The interpreter type for this client ($ARCH) does not

match $TARGET" >&2 exit 1fi

4–10 Version 3.6

PC Example Programs Configuration P

rograms

d

d

n

t.a

u

s

age

ing

PC Example ProgramsThe following batch files check environment space, disk space, anprepare a Windows NT machine for a file package distribution. PCconfiguration programs can be written as.COM , .BAT, or .EXE files.You can also write.CMD files for OS/2 targets and you must writeNLMs for NetWare targets.

Note: Because end-of-line markers in text files differ on UNIX anPC platforms and TME 10 Software Distribution does nottranslate data contained in distributed files, files (configuratioprograms) distributed from a UNIX source host to a targetmust contain end-of-line markers appropriate for the targeTherefore, if you create text files intended for a PC target onUNIX machine, you must manually insert PC end-of-linemarkers at the end of each line in the files. The end-of-linemarker on UNIX machines is the newline character (ASCIIcode0x0a). The end-of-line marker on PC platforms is thecarriage return character (ASCII code0x0d) followed by thenewline character.

These example scripts are available by using anonymousftp fromftp.tivoli.com . Connect to theftp.tivoli.com site to access scripts inthe/pub/support/courier/2.5directory. TheREADME.txt file in thisdirectory describes which file corresponds to which example. If yoare unfamiliar with anonymousftp or do not have Internet access,contact your Tivoli support provider for a copy of the programs.

Checking Disk SpaceUse this batch file as a before program to ensure that a system haenough disk space to install and configure an application. Thisprogram requires that you know how much space the software packrequires (9 MB in this example). It also checks to see if the filesalready exist at the target.

If you create the program and name it/temp/dskspace.bat, specifythis program on a Windows machine as a target before program usthewsetfpprgs command.

wsetfpprgs -T win -b /temp/dskspace.bat @example_fp


PC Example Programs

Create the program as follows:

ECHO OFFREM -------------------------------------------------------------REM Set variablesREM -------------------------------------------------------------REM Check space needed on hard disk.REM SPACE: usage is 10m for 10 megabytes, 10k for 10 kilobytes andREM 10g for gigabytes.REMset SPACE=9m

REMREM DIR: Directory to examine (i.e. where the softwareREM package will be installed, such as... c:\config).REMset DIR=c:\config

REMREM LOG: Log file locationREMset LOG=c:\tivoli\config.logREMREM PATH: Path to the Tivoli command utilitiesREMset PATH=c:\tivoli\cli\win16;%PATH%REM -------------------------------------------------------------REM Initialize Log FileREM -------------------------------------------------------------ECHO.>%LOG%ECHO Running Tivoli pre_check process on this machine for theOurCorp>>%LOG%ECHO software package>>%LOG%ECHO.>>%LOG%ECHO.>>%LOG%REM -------------------------------------------------------------REM Check system for space on C driveREM If not enough room on C drive, error code = 3REM -------------------------------------------------------------wdskspc -s %SPACE% %DIR%if errorlevel 1 goto nospacegoto goodend:nospace

echo . >>%LOG%echo .>>%LOG%echo There is not enough space on the hard drive>>%LOG%echo to install the OurCorp software.>>%LOG%echo Please make more space available on this machine.>>%LOG%echo .>>%LOGwseterr 3goto end

:goodendREM -------------------------------------------------------------REM Set exit code to 0REM -------------------------------------------------------------wseterr 0goto end

:end

4–12 Version 3.6


rograms

get:

m

isk

n

itgh

Preparing a Windows NT Target Before a DistributionYou can use this program to prepare a target for installation of asoftware package. The program performs the following on each tar

■ Ensures the target is running the Windows NT operating syste

■ Deletes a file on the target that was placed there to reserve dspace

■ Ensures that the target has sufficient disk space

■ Kills programs that are running and are part of the distributio

If you create the following program on the source host and name /tmp/prepare.exe, you can specify it as a target before program usinthewsetfpprgs command. For example, if the file package for whicyou want to run this program is calledCustomer Serv Sys, you canspecify the program as follows:

wsetfpprgs -T src -b /tmp/prepare.exe @"Customer Serv Sys"

Also, to use this program, you must define theDEV_APPS,DIR_ARCH_UTILS , DIR_CLI , DIR_CSS_RESERVE,NEWSEED_DSKSPACE, and environment variables in WindowsNT.


@echo off

REM ******************************************************REM ** Set up error codes and environment variablesREM ******************************************************copy %2 c:\errcodes.bat >nulcall c:\errcodes.batset SCRIPT_ERROR_CODE=%ERROR_NONE%

REM ******************************************************REM ** Validate Operating SystemREM ******************************************************if %DEBUG%==TRUE echo *** Checking Operating System. \>c:\temp\debug.outif not %SystemRoot%x==x goto NTdetectedif %DEBUG%==TRUE echo *** Unknown Operating System \>>c:\temp\debug.outset SCRIPT_ERROR_CODE=%ERROR_INVALID_OS%goto end

REM ******************************************************REM ** Validate Disk Space - wdskspc always returns theREM ** number of bytes available on the specified device.


PC Example Programs

REM ** If the -s parameter is specified, then wseterr setsREM ** errorlevel to 1. We detect that and return a 6 toREM ** indicate not enough space.REM ******************************************************:NTdetectedif %DEBUG%==TRUE echo *** Operating System Verified \>>c:\temp\debug.outREM ******************************************************REM ** Determine if this is a CSS Update or a New CSS SeedREM ** with wgetval. If wgetval does not detect the NTREM ** registry entry for SOFTWARE\FPC\CSS\Tivoli, theREM ** ERRORLEVEL is 1 and this is a new seed.REM ******************************************************%DIR_CLI%\wgetval -k "SOFTWARE\CSS\Tivoli" -n Versionif ERRORLEVEL 1 goto NewSeedgoto UpdateSeedREM ******************************************************REM ** NewSeedREM ** If the machine has never received the softwareREM ** before, we are checking for the availability of 150mbREM ******************************************************:NewSeedREM ** unprotect CSSSPACE.001 and delete itif %DEBUG%==TRUE echo *** New CSS Seed Required >>c:\temp\debug.outif not exist %DIR_CSS_RESERVE% goto NewSeedDiskSpaceCheckif %DEBUG%==TRUE echo *** Deleting Place Holder >>c:\temp\debug.out%SYSTEM_WIN32%\attrib -r -h %DIR_CSS_RESERVE%del %DIR_CSS_RESERVE%:NewSeedDiskSpaceCheckif %DEBUG%==TRUE echo *** Checking Disk Space. >>c:\temp\debug.out%DIR_CLI%\wdskspc -s %NEWSEED_DSKSPACE% %DRV_APPS%if %DEBUG%==TRUE echo *** Bytes available. >>c:\temp\debug.out

if not ERRORLEVEL 1 goto DiskSpaceVerifiedif %DEBUG%==TRUE echo *** Inadequate Disk Space >>c:\temp\debug.outset SCRIPT_ERROR_CODE=%ERROR_DISK_SPACE%goto end

REM ******************************************************REM ** UpdateSeedREM ** If the machine has received the software before, weREM ** are checking for the incremental space needed toREM ** apply the update.REM ******************************************************:UpdateSeedREM ** Unprotect CSSSPACE.002 and delete itif %DEBUG%==TRUE echo *** CSS Update Required >>c:\temp\debug.outif not exist c:\dos\cssspace.* goto UpdateDiskSpaceCheckif %DEBUG%==TRUE echo *** Deleting Place Holder >>c:\temp\debug.out%SYSTEM_WIN32%\attrib -r -h c:\dos\cssspace.*del c:\dos\cssspace.*:UpdateDiskSpaceCheckif %DEBUG%==TRUE echo *** Checking Disk Space. >>c:\temp\debug.out%DIR_CLI%\wdskspc -s %CURR_INCR_DSKSPACE% %DRV_APPS%if %DEBUG%==TRUE echo *** Bytes available. >>c:\temp\debug.outif not ERRORLEVEL 1 goto DiskSpaceVerifiedif %DEBUG%==TRUE echo *** Inadequate Disk Space >>c:\temp\debug.outset SCRIPT_ERROR_CODE=%ERROR_DISK_SPACE%goto end

REM ******************************************************REM ** Kill CSS specific processes - Call KILL.EXE toREM ** terminate any processess that might interfere with

4–14 Version 3.6


rograms

the

REM ** the distribute. We are interested in any process thatREM ** begins with:REM ** CU* = CSS ApplicationsREM ** KT* = FOUNDATION 2.4 RuntimeREM ** AZ* = ArchitectureREM ** CSR = Architecture Client/Service requestorREM ******************************************************:DiskSpaceVerifiedif %DEBUG%==TRUE echo *** Adequate Disk Space >>c:\temp\debug.outif not exist %DIR_ARCH_UTILS%\wkill.exe goto killerr%DIR_ARCH_UTILS%\wkill CU*%DIR_ARCH_UTILS%\wkill CSR%DIR_ARCH_UTILS%\wkill AZ*%DIR_ARCH_UTILS%\wkill KT*

REM ******************************************************REM ** Kill FailedREM ******************************************************:killerrif %DEBUG%==TRUE echo *** Kill of Active Processes Failed \>>c:\temp\debug.outset SCRIPT_ERROR_CODE=%ERROR_KILL_FAILED%goto end

REM ******************************************************REM ** Wrap UpREM ******************************************************:endif %DEBUG%==TRUE echo *** %1 Script Complete, Error Code:%SCRIPT_ERROR_CODE% >>c:\temp\debug.outif %DEBUG%==TRUE echo *** Release %RELEASE_VERSION% Before \Script Complete >>c:\temp\debug.out%DIR_CLI%\wseterr %SCRIPT_ERROR_CODE%

Configuring Distributed PC SoftwareUse this batch file as a commit program to configure the softwareproduct (OurCorp in this example), as follows:

■ Create and add icons to theOurCorp group in Windows

■ Add C:\ourcorp to the path in theAUTOEXEC.BAT file

■ Add set statements to theAUTOEXEC.BAT file

This batch file expects a file calledC:\OURCORP\IL.INI to exist andcontain the statements to be added to the WindowsINI file.

If you create the program and name it/usr/bin/config.bat, specify thisprogram as a target commit program on a Windows machine usingwsetfpprgs command on the source host command line.

wsetfpprgs -T win -c /usr/bin/config.bat @example_fp


PC Example Programs


ECHO OFFREM--------------------------------------------------------------REM Error codes:REM 1 = could not add icons to OurCorp groupREM 3 = could not add path statement to autoexec.batREM 4 = could not add set statements to autoexec.batREM 5 = could not add statements to win.iniREMREM Set variables for checkingREM--------------------------------------------------------------REM LOG: The log file locationREMset LOG=c:\tivoli\ourcorp.log

REMREM BAKDIR: The directory in which to store backup copies ofREM system files we will modify.REMset BAKDIR=c:\tivoli\files.bak

REMREM PATH: Path to the Tivoli utilitiesREMset PATH=c:\tivoli\cli\win16;%PATH%

REM--------------------------------------------------------------REM Initialize Log FileREM--------------------------------------------------------------ECHO.>>%LOG%ECHO======================================================>>%LOG%ECHO.>>%LOG%ECHO Running Tivoli post_check process on this machine for the \OurCorp>>%LOG%ECHO software>>%LOG%ECHO.>>%LOG%ECHO.>>%LOG%

REM -------------------------------------------------------------REM Add a new group and icons to windowsREM Group: "OurCorp"REM Icons: Prism, Pivot, Readme and Test programREM -------------------------------------------------------------ECHO.>>%LOG%ECHO Removing OurCorp Group if it exists >>%LOG%ECHO.>>%LOG%waddicon -g "OurCorp Apps" -r>>%LOG%ECHO.>>%LOG%ECHO Adding Icons and Group to windows >>%LOG%ECHO.>>%LOG%

REM -------------------------------------------------------------REM Add Information Catalog Icon. The group, OurCorp Applications,REM will be created automatically if it does not exist.REM -------------------------------------------------------------ECHO Adding Information Cataloag>>%LOG%

4–16 Version 3.6


rograms

waddicon -c j:\ourcorp\catalog\prod\ourcorp.exe -t "Information \Catalog" -g "OurCorp Apps" >>%LOG%

REM -------------------------------------------------------------REM Add BrioQuery icon to the OurCorp Group.REM -------------------------------------------------------------ECHO Adding BrioQuery icon to the OurCorp Applications Group>>%LOG%waddicon -g "OurCorp Apps" -c c:\ourcorp\exe\Brioqry.exe -t \"BrioQuery Explorer">>%LOG%

REM -------------------------------------------------------------REM Back up system files before modifying themREM -------------------------------------------------------------echo Backing up system files before modifying them>>%LOG%mkdir c:\tivoli\files.bakecho Making backup copies of files>>%LOG%copy c:\windows\win.ini %BAKDIR%\win.infcopy c:\config.sys %BAKDIR%\config.inf

REM -------------------------------------------------------------REM Update the win.ini fileREM -------------------------------------------------------------echo Adding the OurCorp text to the win.ini file >>%LOG%wmrgini c:\windows\win.ini c:\ourcorp\il.inidel c:\ourcorp\il.ini

REM -------------------------------------------------------------REM Update the autoexec.bat file with the following:REM set nd_path=c:\ourcorp\oi\libREM set brioqry=c:\ourcorp\queryREM SET Path=c:\ourcorp\exe;%PATH%REM -------------------------------------------------------------ECHO.>>%LOG%ECHO.>>%LOG%echo Updating the autoexec.bat file >>%LOG%

REM ------------------------------------------------------------REM First, make a backup of the original.REM ------------------------------------------------------------copy c:\autoexec.bat c:\autoexec.bkp

:delprismfind /i /c "SET PRISM=" c:\autoexec.bkp >>%LOG%if errorlevel 1 goto noprismECHO.>>%LOG%ECHO PRISM already set in autoexec. Deleting...>>%LOG%ECHO.>>%LOG%wclrline -s "set prism=" -o c:\autoexec.ina c:\autoexec.bkp >> \%LOG%:noprismECHO UPDATING AUTOEXEC.BAT>>%LOG%find /i /c "SET PATH=c:\ourcorp\exe;%%PATH%%" \c:\autoexec.ina>>%LOG%if errorlevel 1 goto nospathgoto msg:nospathfind /i /c ";c:\ourcorp\exe" c:\autoexec.ina>>%LOG%if errorlevel 1 goto noipathgoto msg:noipathfind /i /c "=c:\ourcorp\exe;" c:\autoexec.ina>>%LOG%if errorlevel 1 goto nopath:msg


PC Example Programs

ECHO.>>%LOG%ECHO Path already updated...Skipping>>%LOG%ECHO.>>%LOG%goto ndpath:nopathECHO Adding "SET PATH" line>>%LOG%winsline -f -s "c:\dos;" -a "SET PATH=c:\ourcorp\exe;%%PATH%%" \-o c:\autoexec.inb c:\autoexec.ina >>%LOG%:ndpathif not exist c:\autoexec.inb copy c:\autoexec.ina c:\autoexec.inbfind /i /c "SET ND_PATH=c:\ourcorp\oi\lib" c:\autoexec.inb>>%LOG%if errorlevel 1 goto nondpathECHO.>>%LOG%ECHO ND_PATH already updated...Skipping>>%LOG%ECHO.>>%LOG%goto brioqry:nondpathECHO Adding "ND_PATH" line>>%LOG%winsline -f -s "c:\dos;" -a "SET ND_PATH=c:\ourcorp\oi\lib" -o \c:\autoexec.inc c:\autoexec.inb >>%LOG%:brioqryif not exist c:\autoexec.inc copy c:\autoexec.inb c:\autoexec.incfind /i /c "SET BRIOQRY=c:\ourcorp\query" c:\autoexec.inc>>%LOG%if errorlevel 1 goto nobrioECHO.>>%LOG%ECHO BrioQry already updated...Skipping>>%LOG%ECHO.>>%LOG%ECHO Coping autoexec.inc to autoexec.bat....>>%LOG%copy c:\autoexec.inc c:\autoexec.batgoto config:nobrioECHO Adding "BrioQry" line>>%LOG%winsline -f -s "c:\dos;" -a "SET BrioQry=c:\ourcorp\query" -o \c:\autoexec.bat c:\autoexec.inc >>%LOG%

REM==============================================================REM Updating the config.sys file with the following:REM Files=50REM--------------------------------------------------------------

:configECHO.>>%LOG%ECHO.>>%LOG%REM Updating the config.sys fileecho Updating the config.sys file >> %LOG%find /i /c "FILES=50" c:\config.sys>>%LOG%if errorlevel 1 goto nofilesECHO.>>%LOG%ECHO FILES=50 already updated...Skipping>>%LOG%ECHO.>>%LOG%goto chkfiles:nofilesfind /i /c "FILES=" c:\config.sys>>%LOG%if errorlevel 1 goto setfilesECHO.>>%LOG%ECHO FILES= already there, updating..>>%LOG%ECHO.>>%LOG%ECHO Updating "Files=" line>>%LOG%wrplline -f -s "files=" -o c:\config.out -r "files=50" \c:\config.syscopy c:\config.out c:\config.sys

4–18 Version 3.6


rograms

goto chkfiles:setfilesecho Updating Config.sys>>%LOG%echo FILES=50>>c:\config.sys

:chkfiles

REM =============================================================REM Checking for existance of old files and then deleting them.REM Files:REM briodbs.prfREM prism.iniREM brio.iniREM pivot.iniREM -------------------------------------------------------------REMREM Checking for briodbs.prf

ECHO.>>%LOG%ECHO Checking for c:\windows\briodbs.prf..>>%LOG%ECHO.>>%LOG%IF NOT EXIST C:\WINDOWS\BRIODBS.PRF GOTO CHKPRISMECHO c:\windows\briodbs.prf exists. Deleting...>>%LOG%DEL C:\WINDOWS\BRIODBS.PRF:chkprism

REM Checking for prism.ini

ECHO.>>%LOG%ECHO Checking for c:\windows\prism.ini..>>%LOG%ECHO.>>%LOG%IF NOT EXIST C:\WINDOWS\prism.ini GOTO CHKBRIOECHO c:\windows\prism.ini exists. Deleting...>>%LOG%DEL C:\WINDOWS\prism.ini

:chkbrio

REM Checking for brio.ini

ECHO.>>%LOG%ECHO Checking for c:\windows\brio.ini...>>%LOG%ECHO.>>%LOG%IF NOT EXIST C:\WINDOWS\BRIO.ini GOTO CHKpivotECHO c:\windows\brio.ini exists. Deleting...>>%LOG%DEL C:\WINDOWS\BRIO.ini

:chkpivot

REM Checking for pivot.ini

ECHO.>>%LOG%ECHO Checking for c:\windows\pivot.ini..>>%LOG%ECHO.>>%LOG%IF NOT EXIST C:\WINDOWS\pivot.ini GOTO doneECHO c:\windows\pivot.ini exists. Deleting...>>%LOG%DEL C:\WINDOWS\pivot.ini

:done

REMECHO DELETING OLD FILES >>%LOG%REM


PC Example Programs

del c:\config.out>>%LOG%DEL c:\autoexec.inz >>%LOG%DEL c:\autoexec.ina >>%LOG%DEL c:\autoexec.inb >>%LOG%DEL c:\autoexec.inc >>%LOG%

REM DONE

4–20 Version 3.6

Custom

izations

tes

f

t

ds

ing

ns.

5Customizations

This chapter describes how to customize TME 10 SoftwareDistribution with TME 10 Application Extension Facility and TME 10Application Development Environment. Using the ApplicationExtension Facility, you can add gadgets to a dialog, create attribuand methods for theFilePackageandAutoPack resources, and createcustom icons and bitmaps. Using the Application DevelopmentEnvironment, you can programmatically change the functionality othe methods for theFilePackage, AutoPack, ManagedNode,PcManagedNode, default policy, and validation policy resources.

Before using either application, you should be familiar with theinformation presented in theTME 10 Application Extension FacilityUser’s Guideand the TME 10 Application Development Environmendocumentation.

TME 10 Application Extension FacilityTME 10 Application Extension Facility provides a way for you to adattributes and gadgets to the file package and AutoPack dialogs, awell as other TME 10 resources. This chapter discusses customizonly TME 10 Software Distribution. See theTME 10 ApplicationExtension Facility User’s Guide for information about customizingother TME 10 applications and resources.

You must have Application Extension Facility installed in your TME10 environment before attempting to use the Application ExtensioFacility commands or before performing any of the following action

5


TME 10 Application Extension Facility

hhat

st

e

Retrieving Dialog DescriptorsDialogs and windows are stored as binary dialog descriptors, whicare generated by the DSL compiler. DSL is a compiled language tenables you to specify, compile, and install dialogs within anapplication. When you customize a Software Distribution dialog orwindow, you create a new version of the dialog descriptor. You muthen install the new dialog descriptor for the resource.

The following table lists the descriptors available with the SoftwarDistributionFilePackage resource. You can list these descriptornames using thewlsdialog –r FilePackage command.

Descriptor Name Dialog or Window

confirm2 Export File Package Confirmation dialogOverwrite File Confirmation dialogSelect Source Host dialogUse Defaults Confirmation dialog

confirm3 File Package Close dialog

distribute_filepack Distribute File Package dialog

netware_rights Add NetWare Server Trustee Rights dialog

optional_info Edit Optional Information dialog

options_dos File Package MS/DOS Options dialog

options_netware File Package NetWare Options dialog

options_nt File Package Windows NT Options dialog

options_os2 File Package OS/2 Options dialog

options_unix File Package UNIX Options dialog

options_windows File Package Windows Options dialog

options_win95 File Package Windows 95 Options dialog

properties_filepack File Package Properties window

remove_filepack Remove File Package dialog

5–2 Version 3.6


Custom

izations

es

s,

rey,

or

The following table lists the descriptors available with the SoftwarDistributionAutoPack resource. You can list these descriptor nameusing thewlsdialog –r AutoPackcommand.

All other dialog descriptors are inherited from the TME 10Framework.

To customize a dialog, you must perform the following actions:

■ Retrieve the dialog descriptor

■ Reverse-compile the descriptor

■ Edit the DSL source code

■ Compile the new dialog descriptor

■ Install the custom descriptor

To customize Software Distribution, you must use theFilePackageorAutoPack resource type. For more information on dialog descriptorsee theTME 10 Application Extension Facility User’s Guide.

Changing Existing Dialog GadgetsYou can modify fields, check boxes, and radio buttons on the SoftwaDistribution dialogs. To do so, you must retrieve, de-compile, modifre-compile, and install the DSL code for the selected dialog. Thefollowing examples provide scenarios and solutions for changing

select_fps Select File Packages dialog



calc_size Calculate AutoPack Sizedialog

dist_ap Distribute AutoPack dialog

props_ap Set AutoPack Propertiesdialog

remove_ap Remove AutoPackdialog



for

u

he

the

s:

disabling existing dialog gadgets. Use these steps as an examplecustomizing either theFilePackage or AutoPack resource’s dialogs.

Note: If you have a window displayed while you customize it, yowill not see your changes until you close the window for atleast a minute (to allow the daemon to time out).

Suppose you set the Software Distribution default policy such that tPerform compression on distribution option is enabled for allnewly-created file packages, and you set the Software Distributionvalidation policy so that a user cannot disable this option. BecausePerform compression on distributionoption can no longer be set bythe user, you can modify theFile Package Propertieswindow so thatthis option is not available. Also, suppose you want to change theVendor field on theEdit Optional Information dialog to theAuthorfield. To implement these desired changes, complete the followingsteps:

1. Using thewgetdialog command, retrieve theFile PackageProperties window’s and theEdit Optional Informationdialog’s dialog descriptor by entering the following command

wgetdialog -r FilePackage properties_filepack \> /tmp/properties.d

wgetdialog -r FilePackage optional_info \> /tmp/optional.d

where:

–r FilePackageSpecifies to retrieve the dialog descriptor for theFilePackage resource type.

properties_filepack and optional_infoSpecifies to retrieve the dialog descriptor file.

> /tmp/properties.d and> /tmp/optional.dRedirects the output of the command to thespecified file. If you do not redirect the output toanother process or file, the output is sent tostandard output.

5–4 Version 3.6


Custom

izationsng

rut.

2. To reverse compile the each dialog descriptor, enter the followirdsl commands:

rdsl /tmp/properties.d > /tmp/properties.dsl

rdsl /tmp/optional.d > /tmp/optional.dsl

where:

/tmp/properties.d and /tmp/optional.dSpecifies to reverse-compile the dialogdescriptor file.

> /tmp/properties.dslRedirects the output of the reverse compiler tothe /tmp/properties.dsl and/tmp/optional.dslfiles. If you do not redirect the output to anotheprocess or file, output is sent to standard outp

3. Edit the/tmp/properties.dsl file to disable thePerformcompression on distributionoption on theFile PackageProperties window.

a. Locate the following code in the /tmp/properties.dsl file:

Switch{ Changed = CB_DoCompress_switch&(), CB_PropsDirty&(); Name = DoCompressSwitch; Title = Msg(FpDsl,”Perform compression on distribution”,339); TitlePos = RIGHT; Value = $do_compress; ChildColumnAlignment = LEFT;}

b. To desensitize thePerform compression on distributionoption, insert the following line at the bottom of this sectionof code:

Sensitive = NO;



nd

Thus, the resulting code is:

Switch{ Changed = CB_DoCompress_switch&(), CB_PropsDirty&(); Name = DoCompressSwitch; Title = Msg(FpDsl,”Perform compression on distribution”,339); TitlePos = RIGHT; Value = $do_compress; ChildColumnAlignment = LEFT; Sensitive = NO;}

c. Save and exit the/tmp/properties.dsl file.

4. Edit the/tmp/optional.dsl file to change theVendor field on theEdit Optional Information dialog.

a. Locate the following code in the /tmp/optional.dsl file:

Message{ Name = vendor_title; Title = Msg(FpDsl,”Vendor:”,11); GridHorizontal = 0; GridVertical = 4; ChildColumnAlignment = LEFT; ChildRowAlignment = CENTER;}

b. Change the code so that the title of the field isAuthor , asfollows:

Message{ Name = vendor_title; Title = Msg(FpDsl,”Author:”,11); GridHorizontal = 0; GridVertical = 4; ChildColumnAlignment = LEFT; ChildRowAlignment = CENTER;}

Note: If you are using TME 10 in a language other thanEnglish, you must also change the catalog name amessage key in theMsg(FpDsl,“Author:”, 11)message directive or change the entry number11 in

5–6 Version 3.6


Custom

izations
all translated versions of theFpDsl message catalog.See the TME 10 Application Extension FacilityUser’s Guide for more information about messagecatalogs.
c. Save and exit the /tmp/optional.dsl file.

5. Compile the DSL code for each file by entering the followingdslcommands:

dsl /tmp/properties.dsl > /tmp/properties.d

dsl /tmp/optional.dsl > /tmp/optional.d

where:

/tmp/properties.dsl and /tmp/optional.dslSpecifies to compile the/tmp/properties.dsland/tmp/optional.dsl files.

> /tmp/properties.d and > /tmp/optional.dRedirects the compiled output to the/tmp/properties.d and /tmp/optional.d files,respectively. If you do not redirect the output toanother process or file, it is sent to standardoutput.

6. Install the changes to theFile Package Properties window andEdit Optional Information dialog by entering the followingwputdialog commands:

wputdialog -r FilePackage -T properties_filepack < /tmp/properties.d

wputdialog -r FilePackage -T optional_info < /tmp/optional.d

where:

–r FilePackageSpecifies theFilePackage resource type forwhich to install the dialog.

–T Installs the dialog in all connected TMRs.

properties_filepack and optional_infoSets theproperties_filepackandoptional_infodialog descriptors.



< /tmp/properties.d and < /tmp/optional.dRedirects the new code from the modified DSLfiles, /tmp/properties.d and/tmp/optional.d. Ifyou do not redirect a file to this command, thecommand reads from standard input.

The command line displays the following message to indicatethat the change is successful:

Adding resource-wide customization for dialogproperties_filepack and resource FilePackage.

7. View the changes to theFile Package Properties window bydouble-clicking of a file package icon

This radio button isnow desensitized

5–8 Version 3.6


Custom

izations

ren

the

ed

Alleds

To view theEdit Optional Information dialog, selectOptionalInformation... from theEdit menu on theFile PackageProperties window:

Exposing File Package Keywords and Excluded FilesTME 10 Software Distribution file packages support keywords that anot currently available from the desktop. Use the TME 10 ApplicatioExtension Facility to add new gadgets to any of the SoftwareDistribution dialogs so that you can set these keywords from thedesktop. The type of gadget you can add to a dialog depends on type of keyword you want to expose.

In addition to exposing keywords, you can expose the list of excludfiles. The file package definition is comprised of a header and foursections—keyword options, files and directories to be distributed,nested file packages, and files to be excluded from the file package.of these sections are available from the desktop except the excludfiles list. Use the Application Extension Facility to expose this list a

This field is nowtitled Author



e

s as

t

a List gadget (like theSource Directories and File andNested FilePackagesscrolling lists on theFile Package Propertieswindow).

The following tables list the keywords and their gadget types.Implement the boolean keywords as Switch or Choice gadgets; thUID, GID, time, and file mode keywords as Text gadgets; thereboot/restart keywords as Choice gadgets; and the string keywordText, Page, or Choice gadgets. See theTME 10 Application ExtensionFacility User’s Guide for descriptions and illustrations of the gadgetypes.

Boolean Keywords

create_dirs do_checksum

do_compress dos_after_input_from_src

dos_after_removal_input_from_src dos_after_removal_prog_from_src

dos_before_input_from_src dos_commit_input_from_src

dos_on_error_input_from_src dos_on_error_prog_from_src

dos_removal_input_from_src file_cksums

install_progs nested_first

no_overwrite nt_after_input_from_src

nt_after_removal_input_from_src nt_after_removal_prog_from_src

nt_before_input_from_src nt_commit_input_from_src

nt_on_error_input_from_src nt_on_error_prog_from_src

nt_removal_input_from_src nw_after_input_from_src

nw_after_removal_input_from_src nw_after_removal_prog_from_src

nw_before_input_from_src nw_commit_input_from_src

nw_on_error_input_from_src nw_on_error_prog_from_src

nw_removal_input_from_src os2_after_input_from_src

5–10 Version 3.6


Custom

izations

os2_after_removal_input_from_src os2_after_removal_prog_from_src

os2_before_input_from_src os2_commit_input_from_src

os2_on_error_input_from_src os2_on_error_prog_from_src

os2_removal_input_from_src rm_empty_dirs

rm_extraneous skip_older_src

src_before_skip_non_zero unix_after_input_from_src

unix_after_removal_input_from_src unix_after_removal_prog_from_src

unix_before_input_from_src unix_commit_input_from_src

unix_on_error_input_from_src unix_on_error_prog_from_src

unix_removal_input_from_src win95_after_input_from_src

win95_after_removal_input_from_src win95_after_removal_prog_from_src

win95_before_input_from_src win95_commit_input_from_src

win95_on_error_input_from_src win95_on_error_prog_from_src

win95_removal_input_from_src win_after_input_from_src

win_after_removal_input_from_src win_after_removal_prog_from_src

win_before_input_from_src win_commit_input_from_src

win_on_error_input_from_src win_on_error_prog_from_src

win_removal_input_from_src

Boolean Keywords

UID Keywords

log_file_uid src_after_as_uid

src_before_as_uid unix_after_as_uid

unix_after_removal_as_uid unix_before_as_uid



unix_commitas_uid unix_default_dir_uid

unix_on_error_as_uid unix_removal_as_uid

UID Keywords

GID Keywords

log_file_gid unix_default_dir_gid

Time Keywords

default_mtime

File Mode Keywords

default_dir_mode log_file_mode

Restart/Reboot Keywords

dos_after_removal_option dos_on_error_option

nt_after_removal_option nt_on_error_option

win95_after_removal_option win95_on_error_option

win_after_removal_option win_on_error_option

String Keywords

backup_fmt default_dest

5–12 Version 3.6


Custom

izations

eile

ouut).

The following examples provide steps that you can follow to createach type of gadget. Note that if you have the dialog displayed whyou perform this customization, you will not see the changes until yclose the dialog for at least a minute (to allow the daemon to time o

dos_after_removal_input_path dos_after_removal_prog_path

dos_on_error_input_path dos_on_error_prog_path

list_path nt_after_removal_input_path

nt_after_removal_prog_path nt_on_error_input_path

nt_on_error_prog_path nw_after_removal_input_path

nw_after_removal_prog_path nw_on_error_input_path

nw_on_error_prog_path os2_after_removal_input_path

os2_after_removal_prog_path os2_on_error_input_path

os2_on_error_prog_path postproc

preproc prog_env

src_after_input_path src_after_prog_path

src_before_input_path src_before_prog_path

src_relpath unix_after_removal_input_path

unix_after_removal_prog_path unix_on_error_input_path

unix_on_error_prog_path win95_after_removal_input_path

win95_after_removal_prog_path win95_on_error_input_path

win95_on_error_prog_path win_after_removal_input_path

win_after_removal_prog_path win_on_error_input_path

win_on_error_prog_path

String Keywords



Creating a Switch Gadget and the Excluded Files List

Suppose you want to make thenested_first keyword (a booleankeyword) and excluded files list available in theFile PackagePropertieswindow. Implement thenested_firstkeyword as a Switchgadget in theGeneral Optionssection of the window, and implementthe excluded files list as a List gadget.

1. Retrieve theFile Package Properties window’s dialogdescriptor using thewgetdialog command:

wgetdialog -r FilePackage properties_filepack \| rdsl > /tmp/filepack.dsl

where:

–r FilePackageSpecifies to retrieve the dialog descriptor for theFilePackage resource type.

properties_filepackSpecifies to retrieve theproperties_filepackdialog descriptor file.

| rdsl Redirects the output of thewgetdialogcommandto therdsl command, which reverse-compilesthe code.

> /tmp/filepack.dslRedirects the output of therdsl command to the/tmp/filepack.dsl file. If you do not redirect theoutput to another process or file, the output issent to standard output.

2. Edit the/tmp/filepack.dsl file to make thenested_firstkeywordavailable.

a. Add a Switch gadget for thenested_first keyword. Locatethe following code in the file:

Switch{ Changed = CB_DoCompress_switch&(), CB_PropsDirty&(); Name = DoCompressSwitch;

5–14 Version 3.6


Custom

izations

e

d.

Title = Msg(FpDsl,”Perform compression on distribution”,339); TitlePos = RIGHT; Value = $do_compress; ChildColumnAlignment = LEFT;}

To add aProcess nested file packages firstoption below thePerform compression on distribution option, insert thefollowing code below this section of code:

Switch{ Name = NestedFirstSwitch; Title = ”Process nested file packages first”; TitlePos = RIGHT; ChildColumnAlignment = LEFT;}

When defining the Switch gadget, you need only define thName, Title , TitlePos, andAlignment attributes.

b. Add the following variable definition in the variabledeclaration section (at the top) of thefilepack.dsl file:

CString IgnoredValue = register_fp_keyword%(“properties_filepack”,“nested_first”,”/.../NestedFirstSwitch”);

where:

IgnoredValueAssigns the value returned by theregister_fp_keyword method to theIgnoredValue variable, which is ignored.

properties_filepackSpecifies the dialog to be modified.

nested_first Specifies thenested_firstkeyword in the filepackage definition.

/.../NestedFirstSwitchSpecifies the path to the gadget to be create



das

,

etes

g

If you were to add another gadget to the dialog, you woulsimply add the keyword and the new gadget’s name, suchinstall_progs, to this declaration, as follows:

CString IgnoredValue = register_fp_keyword%(“properties_filepack”,“nested_first”,”/.../NestedFirstSwitch”, ”install_progs”,“/.../SecondKeywordSwitch”);

3. Add the exclude files list. Locate the following code in the/tmp/filepack.dsl file:

}

Group{ Attributes { Border = YES; Layout = VERTICAL; Name = fpOptionsGroup; ChildColumnAlignment = CENTER; ChildRowAlignment = STRETCH; }}

Insert the following code above this section of code:

Group ExcludeFilesDirsGroup = Load(“excludes”);

Note: You can add this line of code anywhere in the DSL filewhich will determine its position on the window. In thiscase, the exclude files list is added in the Group gadgthat defines the source files list and nested file packaglist.

4. Save the file and compile the DSL code by entering the followindsl command:

dsl /tmp/filepack.dsl > /tmp/filepack.d

where:

/tmp/filepack.dslSpecifies to compile the/tmp/filepack.dsl file.

5–16 Version 3.6


Custom

izations
> /tmp/filepack.d
Redirects the compiled output to the/tmp/filepack.d file. If you do not redirect theoutput to another process or file, it is sent tostandard output.

5. Install the dialog by entering the followingwputdialogcommand:

wputdialog -r FilePackage properties_filepack \< /tmp/filepack.d

where:


properties_filepackSets the properties_filepack dialog descriptor.

< /tmp/filepack.dRedirects the new code from the/tmp/filepack.dfile. If you do not redirect a file to this command,the command reads from standard input.



tedionou

6. View the changes to theFile Package Properties window bydouble-clicking of a file package icon:

Creating a Choice and Text Gadget

Currently, Software Distribution file packages do not support afterremoval and on error keywords from the desktop. Suppose you wanto expose the after removal keywords, creating another configuratbutton on each platform-specific file package dialog. For example, ywould create anAfter Removal button on theFile Package WindowsOptions dialog to expose thewin_after_removal_prog_from_src,

5–18 Version 3.6


Custom

izations

be

e

win_after_removal_prog_path,win_after_removal_input_from_src,win_after_removal_input_path, andwin_after_removal_optionskeywords.

Note: This procedure is complicated; Tivoli recommends that youvery familiar with the Application Extension Facility andDSLs before performing this procedure.

Complete the following steps to add after removal keywords to theplatform-specific dialogs:

1. Retrieve theFile Package Window Optionsdialog’s dialogdescriptor using thewgetdialog command:

wgetdialog -r FilePackage options_windows \| rdsl > /tmp/opts_win.dsl

where:

–r FilePackageSpecifies to retrieve the dialog descriptor for thFilePackage resource type.

options_windowsSpecifies to retrieve theoptions_windowsdialog descriptor file.

| rdsl Redirects the output of thewgetdialogcommandto therdsl command, which reverse-compilesthe code.

> /tmp/opts_win.dslRedirects the output of therdsl command to the/tmp/opts_win.dsl file.

2. Locate the following code in the /tmp/opts_win.dsl file.

Button{ Commands = set_visible&/GlobalGroup/ScriptGroup/ BeforeScriptGroup(NO), set_visible&/GlobalGroup/ ScriptGroup/AfterScriptGroup(NO), set_visible&/ GlobalGroup/ScriptGroup/RemoveScriptGroup(NO), set_visible&/GlobalGroup/ScriptGroup/ CommitScriptGroup(YES); Name = CommitButton;



ed.

at

rin

Title = Msg(FpDsl,”During Commit”,239); TitlePos = CENTER; GridHorizontal = 1; GridVertical = 3; ChildColumnAlignment = STRETCH; ChildRowAlignment = CENTER;}

3. Copy this text and insert it below itself. Modify the gadgetdefinition so that it is as follows:

Button{ Commands = set_visible&/GlobalGroup/ScriptGroup/ BeforeScriptGroup(NO), set_visible&/ GlobalGroup/ScriptGroup/AfterScriptGroup(NO), set_visible&/GlobalGroup/ScriptGroup/ RemoveScriptGroup(NO), set_visible&/ GlobalGroup/ScriptGroup/CommitScriptGroup(NO), set_visible&/GlobalGroup/ScriptGroup/ AfterRemovalScriptGroup(YES); Title = “After Removal”; TitlePos = CENTER; GridHorizontal = 1; GridVertical = 4; ChildColumnAlignment = STRETCH; ChildRowAlignment = CENTER;}

This step creates theAfter Removal button, which will displaythe partial dialog where the after removal keywords are expos

Because you are adding another button, you must indicate thyou’ll have five buttons on the dialog, not four. Locate thefollowing line:

GridHeight = 4;

Change4 to 5 in this line of code.

4. Add the following line at the end of the Commands attribute foeach configuration program Button gadget (similar to the codestep 3):

set_visible&/GlobalGroup/ScriptGroup/AfterRemovalScriptGroup(NO);

5–20 Version 3.6


Custom

izations
Thus, the code in step 3 will be:
Button{ Commands = set_visible&/GlobalGroup/ScriptGroup/ BeforeScriptGroup(NO), set_visible&/GlobalGroup/ ScriptGroup/AfterScriptGroup(NO), set_visible&/ GlobalGroup/ScriptGroup/RemoveScriptGroup(NO), set_visible&/GlobalGroup/ScriptGroup/ CommitScriptGroup(YES), set_visible&/GlobalGroup/ ScriptGroup/AfterRemovalScriptGroup(NO); Name = CommitButton; Title = Msg(FpDsl,”During Commit”,239); TitlePos = CENTER; GridHorizontal = 1; GridVertical = 3; ChildColumnAlignment = STRETCH; ChildRowAlignment = CENTER;}

5. Locate the following code:

Group{ Attributes { Border = YES; Layout = VERTICAL; Name = CommitScriptGroup; Title = Msg(FpDsl,”Commit Distribution BAT/EXE/COM File Options”,267); TitlePos = TOP; . .(omitted code) . Choice { Changed = CB_OptionsWindowsDirty&(); Choices = Msg(FpDsl,”Do nothing”,274){OPT_NONE},

Msg(FpDsl,”Reboot machine”,275){OPT_REBOOT},Msg(FpDsl,”Restart Windows”,276){OPT_RESTART};

Name = BootChoice; Show = ALL; Sort = NO; Title = Msg(FpDsl,”After Commit:”,273); TitlePos = TOP; Value = $win_commit_option; ChildColumnAlignment = LEFT; } } } }}



to

he

6. Copy this code and insert it below itself. Make the followingchanges to the code. This addition to the DSL file enable youspecify whether the input file resides on the source host orsubscriber (set thewin_after_removal_input_from_srckeyword). By default, this keyword is set to the same value as twin_after_removal_prog_from_src keyword. The final codeshould look like the following:

Group{ Attributes { Border = YES; Layout = VERTICAL; Name = AfterRemovalScriptGroup;

Title = “After Removal Distribution BAT/EXE/COM FileOptions”; TitlePos = TOP; Visible = NO; GridHorizoontal = 0; GridVertial = 1; ChildRowAlignment = STRETCH; }

Gadgets { Choice { Border = YES; Choices = Msg(FpDsl,”Source Host”,269){“y”}, Msg(FpDsl,Subscribers,270){“n”}; Layout = HORIZONTAL; Name = win_after_removal_prog_from_src; Show = ALL; Sort = NO; Title = Msg(FpDsl,“Get BAT/EXEC/COM filefrom:”,268); TitlePos = TOP; ChildColumnAlignment = STRETCH; }

Group { Attributes { Border = YES; Layout = HORIZONTAL; Name = prog_group; Title = Msg(FpDsl,”Enter BAT/EXE/COM filename”,271); TitlePos = TOP; }

5–22 Version 3.6


Custom

izations

Gadgets { Text { Name = win_after_removal_prog_path; ChildColumnAlignment = STRETCH; } } }

Choice { Border = YES; Choices = Msg(FpDsl,”Source Host”,269){“y”}, Msg(FpDsl,Subscribers,270){“n”}; Layout = HORIZONTAL; Name = win_after_removal_input_from_src; Show = ALL; Sort = NO; Title = Msg(FpDsl,“Get input file from:”,268); TitlePos = TOP; ChildColumnAlignment = STRETCH; }

Group { Attributes { Border = YES; Layout = HORIZONTAL; Name = input_group;

Title = Msg(FpDsl,”Enter input file name”,271); TitlePos = TOP; }

Gadgets { Text { Name = win_after_removal_input_path; ChildColumnAlignment = STRETCH; } } }

Choice win_after_removal_option = Load(“advanced_win_opt”,”title”,”After RemovalScript Runs:”); }

}



g

7. Add the following variable to the Variable block:

CString dummy =register_fp_keyword%(“options_windows”,“win_after_removal_prog_from_src”,“/.../win_after_removal_prog_from_src”,“win_after_removal_prog_path”,“/.../win_after_removal_prog_path”,“win_after_removal_input_from_src”,“/.../win_after_removal_input_from_src”,“win_after_removal_input_path”,“/.../win_after_removal_input_path”,“win_after_removal_option”,“/.../win_after_removal_option”);

8. Save the file and compile the DSL code by entering the followindsl command:

dsl /tmp/opts_win.dsl > /tmp/opts_win.d

where:

/tmp/opts_win.dslSpecifies to compile the/tmp/opts_win.dsl file.

> /tmp/opts_win.dRedirects the compiled output to the/tmp/opts_win.d file. If you do not redirect theoutput to another process or file, it is sent tostandard output.

9. Install the dialog by entering the followingwputdialogcommand:

wputdialog -r FilePackage -T options_windows \< /tmp/opts_win.d

where:


–T Installs the dialog in all connected TMRs.

options_windowsSets the options_windowsdialog descriptor.

5–24 Version 3.6


Custom

izations
< /tmp/opts_win.d
Redirects the new code from the/tmp/opts_win.d file. If you do not redirect a fileto this command, the command reads fromstandard input.

10. View the changes to theFile Package Windows Optionsdialogby selectingPlatform-Specific Options -> Windows Options...from theEdit menu of the File Package Properties window:



hes:

nTohisr

re

Bitmaps and IconsIn addition to customizing dialogs, TME 10 Application ExtensionFacility enables you to create and customize icons and bitmaps. Ticons and bitmaps available for Software Distribution are as follow

All other bitmaps and icons are inherited from the TME 10Framework.

These bitmaps are stored in the X pixmap (XPM) format, which cadisplay an image on monochrome, grey scale, and color monitors.edit an XPM file, you must have a bitmap editor that can support tformat. If you do not, you can use the public domain pixmap editoincluded in the Productivity Package. See theTME 10 ApplicationExtension Facility User’s Guide for a further discussion on bitmapeditors.

To customize a bitmap, you must perform the following actions:

■ Retrieve the bitmap

■ Edit the bitmap using a pixmap editor

■ Install the custom bitmap

The following example illustrates these steps. To customize SoftwaDistribution, you must use theFilePackage or AutoPack resourcetype.

1. Retrieve the bitmap from theAutoPack resource’s user interfaceusing thewgetbitmap command:

wgetbitmap -r AutoPack ap_icon > apicon.bit

where:

fp_icon ap_icon down left right up

5–26 Version 3.6

TME 10 Application Development Environment

Custom

izations

,

nd

–r AutoPack Specifies theAutoPack resource type for whichto retrieve the bitmap.

ap_icon Specifies to retrieve theap_icon bitmap.

> apicon.bit Redirects the bitmap to theapicon.bit file. If youdo not redirect output to another process or fileoutput is written to standard output.

2. Edit theapicon.bit file using your bitmap or pixmap editor.

3. Install the customized bitmap by entering the followingwputbitmap command:

wputbitmap -r AutoPack -T ap_icon < apicon.bit

where:

–r AutoPack Specifies theAutoPack resource type for whichto install the new bitmap.

–T Installs the new bitmap in the current TMR andall connected TMRs.

ap_icon Specifies to replace theap_icon bitmap.

< apicon.bit Redirects the bitmap definition fromapicon.bitfile. If you do not redirect output to anotherprocess or file, output is written to standardoutput.

See the chapter on bitmaps in theTME 10 Application ExtensionFacility User’s Guidefor detailed information on editing and installingbitmaps.

TME 10 Application Development EnvironmentTME 10 Application Development Environment enables you toprogrammatically customize Software Distribution by creating newdialogs and CLI commands. Use the Application DevelopmentEnvironment if you want to customize Software Distribution bydirectly invoking the methods or by accessing the IDL interfaces ainclude files.



at

Customizing the File Package ResourceThe following methods reside on the file package (fp) object:

The$INTERP/tivoli/FPO/FpoCore.h file is a header file that residesin the directory specified during the Extension API productinstallation. Be sure to include this header file with your source so thyou can use the following defined constants for the indicatedtype andoption input parameters discussed here:

FilePackage_FpoCore_DISTRIBUTEFilePackage_FpoCore_COMMITFilePackage_FpoCore_DISTRIBUTE |FilePackage_FpoCore_COMMITFilePackage_FpoCore_ALL_FILESFilePackage_FpoCore_SRC_CHANGE_ONLYFilePackage_FpoCore_ANY_DIFFERENCES

In addition to providing these defined constants, the$INTERP/tivoli/FPO/FpoCore.h file provides defined constants forthe following:

■ Software Distribution-specific exceptions

■ Function prototypes for Software Distribution method stubs

■ Software Distribution-specific data structures

■ Software Distribution-specific TypeCodes

See theTME 10 Programmer’s Reference Manualfor a discussion onexceptions and TypeCodes.

Method Purpose

fp_push Processes thefp object to produce a file package stream(fps), sends, unpacks, and installs thefps on thespecified target hosts

fp_to_fpblock Processes thefp to produce a file package block(fpblock), which is output to a file on a specified host

fp_to_size Processes thefp to return a sum of all file byte sizes

set_fp_name Sets thefp object name

5–28 Version 3.6


Custom

izations

elles),he

s,full

et

lern

The fp_push Method

void fp_push( in long type, in long option, in SysAdminTypes::ObjectLabelList target_list, out SysAdminTypes::ObjectLabelList fail_list);

The inputs of this method include the type of distribution (distributonly, distribute and commit, commit only), the distribution option (aentries, entries with changed source files, or entries with any changand a list of targets. This method outputs those targets for which tspecified operation failed.

The fp_to_fpblock Method

void fp_to_fpblock( in long option, in string target_path, in SysAdminTypes::ObjectLabelList target_list, out SysAdminTypes::ObjectLabelList fail_list);

The inputs to this method include the distribution option (all entrieentries with changed source files, or entries with any changes), thepath to where the fpblock will be stored, and a list of targets. Ifmultiple targets are specified, the fpblock will be written to the targpath on all of them. This method returns a list of those targets forwhich the specified operation failed.

The fp_to_size Method

void fp_to_size( in long platform, in long option, out string fp_size);

The inputs to this method include the platform type to which the fipackage will be distributed and the distribution option (all entries oentries with changed source files). This method outputs the size, ibytes, of the file package.



ean

n.

o

d

The set_fp_name Method

void set_fp_name( in string fp_name, in boolean log_notice);

The inputs to this method include the file package name and a boolvalue whereTRUE or 1 posts a notice to the Software Distributionnotice group after the name is changed, andFALSE or 0 does not posta notice. There are no outputs of this method.

Customizing the AutoPack ResourceThe following methods reside on the AutoPack (ap) object:

The$INTERP/tivoli/APO/APack.h file is a header file that resides inthe directory specified during the Extension API product installatioIt defines contents for the following:

■ AutoPack-specific exceptions

■ Function prototypes for AutoPack method stubs

■ AutoPack-specific data structures

■ AutoPack-specific TypeCodes

Method Purpose

calc_size Returns the size of the AutoPack file associated withtheap object

distributep Sends, unpacks, and installs the AutoPack on thetarget PC managed nodes

init_by_upload Copies an AutoPack file from a PC managed node ta managed node and associates the managednode-resident copy with theap object

init_from_existing Associates an existing AutoPack file on a managednode with theap object

removep Removes an AutoPack from the target PC managenodes

5–30 Version 3.6


Custom

izations

the

for

ied

ofhets

See theTME 10 Programmer’s Reference Manualfor a discussion onexceptions and TypeCodes.

The calc_size Method

long calc_size();

There are no inputs to this method. It returns the size, in bytes, ofAutoPack object’s associated AutoPack file.

The distributep Method

long distributep( in SysAdminTypes::ObjectLabelList targets_list, out SysAdminTypes::ObjectLabelList failed_list);

The input to thedistributep method is a list of targets from which theAutoPack should be removed. This method outputs those targets which the removal operation failed.

The init_by_upload Method

void init_by_upload( in path_desc_t source_file, in path_desc_t dest_file, in boolean overwrite);

The inputs to this method are the path to an AutoPack file on a PCmanaged node, the path to which the AutoPack file should be copon a managed node, and theoverwrite argument. If theoverwriteargument is set to TRUE, the method overwrites an existing copy the same AutoPack file on the managed node. If it’s set to FALSE, tmethod throws an ExCopyFailed exception if the AutoPack file exison the managed node.

The init_from_existing Method

typedef struct path_desc_struct { string hostname; string pathname;} path_desc_t;

void init_from_existing( in path_desc_t autopack_file);



st

for

The input to this method is the path to an AutoPack file, which mualready reside on a managed node. Thehostnamestring is the name ofa managed node and thepathnamestring is the path to the AutoPackfile on that managed node.

The removep Method

long removep( in SysAdminTypes::ObjectLabelList targets_list, out SysAdminTypes::ObjectLabelList failed_list);

The input to theremovep method is a list of targets from which theAutoPack should be removed. This method outputs those targets which the removal operation failed.

5–32 Version 3.6

Troubleshooting

n

e,e. Aw

d

o

e

the

e

6Troubleshooting

This chapterdiscusses trou-bleshooting forfile packageoperations only.

During a file package distribution, TME 10 Software Distribution cainvolve three types of machines—the Tivoli Management Region(TMR) server, the file package source host, and the target machinwhich can be a managed node, an endpoint, or a PC managed noddistribution operation can take different avenues depending on hoyou have set up repeaters on the network, how many targets areinvolved in the distribution, and the size of the file package.

File package distributions are enabled by three main methods:fp_push, fp_dist, andfps_install. This chapter examines how thesemethods and machine types interact depending on the number antypes of targets. It also provides some pointers about solvingdistribution problems.

How Software Distribution WorksSoftware Distribution relies on the following three main methods tperform file package operation

■ Thefp_pushmethod runs on the TMR server and coordinates thdistribution. In addition to its other tasks, it obtains the filepackage and the list of targets, and passes this information tofp_dist method on the source machine. Thefp_push methodalso concludes the distribution based on the completion of thfp_dist andfps_install methods.

■ The fp_dist method runs on the file package source host andcontacts the MDist service with the list of targets. The MDist

6


How Software Distribution Works

ver

ch

e

to

ervns

will

s,erk

for

service, in turn, contacts the repeater manager on the TMR serthat runs theobj_route method to determine routing of the filepackage data stream.

The MDist service receives the routing information from therepeater manager and contacts the distribution’s targets, whirun thefps_install method. It passes the routing information torepeaters and endpoint gateways.

■ The fps_install method runs on each target system and isresponsible for receiving and installing the file package.

During a file package distribution, Software Distribution distributesfile packages with communication services provided with TME 10Framework. Distributions rely on communication established by thfollowing two Framework services:

■ Interobject Message (IOM) service, which provides a means distribute large blocks of data without involving oservcommunications between source and target machines. The osis the main Framework service that coordinates communicatiobetween all managed resources and gateways. This chapterrefer to an IOM service connection as an IOM channel.

■ Multiplexed Distribution (MDist), which enables synchronousdistributions of large amounts of data to multiple targets in anenterprise. During a file package distribution to multiple targetMDist sets up a distribution tree of IOM channels from the sourchost to repeaters to targets. MDist limits its own use of netwobandwidth, as configured through thewrpt command, to helpprevent intense network activity that stresses the bandwidth extended periods of time (network storms).

See Chapter 3, “The Distribution Environment,” in theTME10Software Distribution User’s Guide for a detailed description and aconfiguration example of the MDist service. Additional informationabout MDist is available in theTME 10 Framework Planning andInstallation Guide. The BDT/IOM service is explained in a followingsection.

6–2 Version 3.6

Software Distribution Methods

Troubleshooting

ted. file

e

Software Distribution MethodsDuring a file package distribution, one of three push methods isinitiated on the TMR server. How you choose to distribute the filepackage actually determines which of these methods will be execuOne of the following methods serves as the master method of thepackage distribution and orchestrates all submethods:

Validation poli-cy for SoftwareDistributionruns at distribu-tion time. Also,policy is set bythe policy re-gion, not by in-dividual filepackages

fp_push Method called if the file package is distributed from theFile->Distribute... menu option on theFile PackageProperties window or using thewdistfp command.

default_pushMethod called if the file package is distributed from theProfile Manager->Distribute... menu option on theProfile Manager window or using the drag-and-drop.

push Method called if the file package is distributed using thwdist command from the command-line.

The following sections examine and illustrate how thefp_pushmethod works withfp_dist andfps_install to distribute a file package.Both thepush anddefault_push methods are implemented similarlyand call the same submethods asfp_push.



n

in

.

p,

The following diagram illustrate how methods are invoked betweemachines in a TME 10 environment:

The actual distribution of a file package to a client machine occursstages. When a file package is distributed, thefp_pushmethod on theTMR server executes the following steps:

■ Gathers a list of targets for the file package operation.

■ Retrieves the file package definition from the object database

■ Runs thefp_val_operation validation policy method, whichvalidates the targets of the distribution.

■ Calls thefp_dist method on the source host.

■ Completes the distribution and logs the results to a notice groue-mail address, or log file after thefp_dist method completes.

TMR server M1 w/ repeaterSH

T1 T2 T3

fp_push fp_dist

fps_install (on all targets)

MDist servicerpt

repeater manager

T3

1. fp_push passes target list to fp_dist on source host (SH)

2. fp_dist initiates the MDist service on SH

3. MDist retrieves routing information from repeater manager on the TMR server

4. While MDist invokes rpt on source to distribute to source’s target endpoints, thesource’s rpt invokes fps_install on T1 and T2 and starts distribution

5. MDist passes routing information and the distribution files to the rpt method on M1

6. M1’s rpt method invokes fps_install on T3 and T4 and starts distribution

rpt

6–4 Version 3.6


Troubleshooting

e

s to

pt

its

gets.

he

of

red

When thefp_pushmethod calls thefp_dist method on the source host,it passes the file package data definition and the list of targets. Thfp_dist method then:

■ Initiates the MDist service that calls theobj_route method on therepeater manager, which keeps track of repeater configurationdetermine how the file package will be routed to each target.

■ Bundles the contents of the file package into a data stream.

■ If the source host is a repeater, MDist calls therpt method todistribute the data stream to all targets within its range. The rmethod, in turn, calls thefps_install method on each target. Forall other targets of the distribution, the source host calls therptmethod on the repeater that has a target of the distribution inrange, and passes the data stream and list of targets to it.

■ If the source host is not a repeater, it calls therpt method on thesource host’s repeater, passing the data stream and list of tar

Each repeater then simultaneously:

■ Distributes the data stream to all targets in its range, calling tfps_install method on each target.

■ Calls therpt method on any subrepeater and passes the datastream and list of targets to it if this repeater includes a targetthe distribution in its repeater range.

The size of the file package data stream dictates how it is transferbetween thefp_dist andfps_install methods. File packages that are16KB or less are passed as a parameter to thefps_install method: Thefp_dist method sends the file package to thefp_dist method’s oserv,which forwards it to thefps_install method’s oserv (assuming that themethods are running on different managed nodes). Thefps_installmethod’s oserv then forwards the file package to thefps_installmethod.

For file package data streams that are larger than 16KB, thefp_distmethod, MDist service, and thefps_install method communicate overa separate channel. Communication between thefp_dist andrptmethods proceeds in the same manner as thefp_dist andfps_installmethods, as does communication between multiplerpt methods.


Network Communications

ets.

e

ves.

r ofRsns

o

94

When thefps_install method finishes receiving and installing the filepackage, it returns its completion status (failed or successfuloperation) to the method that initially called it. Thefp_dist methoddoes not complete until all of thefps_install andrpt methods that itinitiated have returned. Correspondingly, it returns its results to thfp_push method, which then completes after receiving these resul

To view a list of all thefps_install andrpt methods called by thefp_dist method, enter theodstat –c command on the source hostduring the distribution. Also, if you enter theodstat –c command oneach managed node while it is receiving the distribution, you will sea listing for thefps_install method that is running. Theodstat –ccommand listsfp_push method as running on the server and thefp_dist method as running on the source host. It lists therpt methodas running on the repeater. If you continually enter theodstat –ccommand, you will see eachfps_installmethod disappear from the listas each process completes, until finally thefp_dist method completes.

Note: If repeaters are involved, you may not see all of thefps_installmethods for all targets usingodstat from the source host.They are listed on their repeaters or on the targets themsel

Network CommunicationsTME 10 Framework provides a Interobject Message (IOM)communication service that enables the rapid and reliable transfelarge quantities of data between machines in a TMR or between TMin a network. During a distribution, the IOM service provides a meaof transferring large blocks of data without involving oservcommunications between source and target machines.

The oserv coordinates communications between all managedresources and gateways in a TMR. Managed nodes, PC managednodes, and endpoint gateways continuously keep port 94 “open” treceive information from other oservs or TME 10 processes.Distributions from a source machine to a target system can occurthrough oserv communications over port 94. However, using port for oserv communication during large distributions can lead tonetwork overload, resulting in a slow and inefficient distribution

6–6 Version 3.6

Distributing to Managed Nodes

Troubleshooting

n:

xtestthe

atert’s

.

rceeralrk

schema. To lessen some of this load, Framework establishes IOMchannels for file distributions larger than 16KB.

The following diagram summarizes the sequence of communicatioevents that occur when distributing a data packet larger than 16KB

For distributions that are larger than 16KB, the source and targetmachine communicate over the IOM channel to transfer data.

Distributing to Managed NodesAs you initiate a file package distribution to a managed node, thesource machine determines the size of the file package. If the filepackage is larger than 16KB, the source machine allocates the neavailable port number and opens it to listen for a file package requfrom the target machine. The source machine then passes a dkey totarget. The dkey contains the IP address of the source host or repefrom which the file package will be distributed, and the allocated pornumber. Using the dkey information, the target machine makes anIOM connection, called an IOM channel, with the source machine

The transfer of file package data can occur after this sequence ofcommunication events establishes a connection between the souand target machines. The remainder of this section illustrates sevdistribution scenarios to managed nodes involving different netwoconfigurations

1. The source machine opens a new port and passes a dkey to target system.

2. The target opens an IOM channel on the source via an IP address and portspecified in dkey.

3. The source begins transfer of data to target.

source managednode



theor

e

. Thed

over

utn.

eon

Distributing from Source Host/TMR Server to ManagedNodes

In the simplest distribution scenario, the server and source host aresame machine and the targets are MN1 and MN2, which are UNIXNT managed nodes.

If you distribute a file package to MN1 and MN2 in this diagram, thfp_push method starts thefp_dist method—both methods run on thesame machine because the TMR server serves as the source hostfp_dist method, through the oserv, contacts the oservs on MN1 anMN2 and starts thefps_install method on each machine. Thefp_distmethod passes the IP address of the source host and a port numberwhich thefps_install method can pull the file package. If the filepackage is larger than 16KB, thefps_install method opens an IOMchannel from the target, thereby enabling the methods to talk withothe oservs and without using port 94 for the file package distributioThe file package is then received by eachfps_install method on MN1and MN2.

If the distribution includes the server as a target, thefp_dist methodstarts thefps_install method on the server and pulls the file packagfrom its source directories and distributes it to its defined destinatidirectory (on the same machine).

TMR serverserves assource host

MN1 MN2

6–8 Version 3.6


Troubleshooting

R1

ffiletos:

’sithN3the

Distributing from Source Host/TMR Server through aRepeater

This illustration extends the previous scenario by adding repeateras a client of the TMR server/source host machine. The managednodes, MN3 and MN4, are both specified in R1’s repeater range.

If you distribute a file package to MN1 and MN2, the same order omethods occurs as described above. If, however, the targets of thepackage include MN3 and MN4, and you distribute the file packageall targets, including the source host and R1, the following happenThe fp_push method starts thefp_dist method. Again, both of thesemethods run on the same machine. Thefp_dist method starts thefps_install method on MN1, MN2, and itself, and therpt method onR1. Therpt method starts thefps_install method on each of its clients.The fps_install methods on MN3 and MN4 then receive the filepackage from R1; thefps_install methods on MN1, MN2, and R1receive from the source host.

When therpt method on R1 pulls the file package, it is placed in R1staging area, which is generally specified when R1is configured wthewrpt command. This staging area serves as a cache in case Mor MN4 cannot synchronously absorb the file package as it reaches


MN1 MN2

MN3 MN4

R1



age

nghto toes.r

ing.

s,

d. The

er’s

repeater. As R1 receives the file package, it distributes the file packto MN3, MN4, and itself.

Finally, if you distribute the file package to MN3 only, the oservs othe source host and MN3 communicate directly, without going throuthe repeater. This is true in general—if you distribute a file packageone target, Software Distribution always opens a direct connectionthat target, even if a repeater is configured between the two machinThe only time this does not hold true is when, while configuring yourepeaters, you set thealwaysargument with thewrpt command. Thisargument specifies that the repeater must always be used for routTivoli recommends setting this flag when it is appropriate for aparticular wide area network—setting this flag for local area networkhowever, isnot recommended. See theTME 10 Framework ReferenceManual for wrpt command usage and syntax.

Distributing from a Source Host to Multiple RepeatersThis scenario adds multiple repeaters (R1 and R2) to the TMR anassumes that the server and source host are not the same machinemachines illustrated under the repeaters are listed in each repeatrange.

TMR server

MN2 MN3

source

R2

PC MN MN1

R1

hostMN4

6–10 Version 3.6

Distributing to Endpoints

Troubleshootingeters

td;nds

,ially ander1

ge.

itheam

ineion.iated orr

ctedgehe

e to

If you distribute a file package from the source host (SH) to MN4, thsource host makes a direct connection to MN4, bypassing the repeaand server. MN4 receives the file package using port 94 or an IOMchannel depending on the size of the file package.

Distributing a file package from SH to itself and MN4, however,changes the communication design entirely. The source host is noresponsible for what is distributed if more than one target is involveinstead, it passes the responsibility to the repeater, R2. Thus, SH sethe file package to R2 and R2 sends it to MN4 and SH.

If you distribute the file package to all of the machines in this diagramincluding the repeaters, source host and server, the source host initsends the file package to all three repeaters: R1, the TMR server,R2. R2 distributes the file package to MN4, SH, and R2. The servthen distributes the file package to MN3, MN2 and itself. Finally, Rdistributes the file package to MN1, PCMN and itself.

Distributing to EndpointsAs you initiate a file package distribution to an endpoint via itsgateway, the source machine determines the size of the file packa

If the file package is less than 16KB, the source machine oservcommunicates directly with the gateway oserv that is associated wa target endpoint, and uses port 94 to send the file package data strto the gateway. The gateway then distributes the data to its targetendpoints.

However, if the file package is larger than 16KB, the source machallocates the next available port number and opens an IOM connectThe source machine passes the dkey to the gateway that is assocwith the target endpoint. The gateway then connects to the sourcerepeater IOM channel specified by the IP address and port numbefrom the dkey. Simultaneously, the gateway contacts the targetendpoint to initiate thefps_install method.

When the source host or repeater detects that the gateway is conneto the IOM channel, the host machine begins sending the file packadata stream to the gateway, where the data is stored in a cache. Tgateway then simultaneously begins data transferral from the cachthe endpoint. In conjunction with the lcfd daemon, thefps_install



inttion

, the

en the

.

odm itsod

ce

method reads and processes the data stream. When each endpofinishes processing the file package data stream, it returns complestatus to its gateway and closes the connection. After each targetendpoint has returned its individual status to its associated gatewaygateway sends collective distribution status to the source.

The remainder of this section describes distribution scenarios toendpoints via an endpoint gateway. During a distribution to anendpoint, thefp_push andfp_dist methods are executed between thsource host and the gateway in much the same manner as betweesource host and managed nodes. Thefps_install method, however,follows a very different communication strategy in this architecture

During a distribution, the gateway is responsible for tracking methrequests from the server and other managed nodes as well as froendpoints. The endpoint gateway also acts as a gateway for methinvocation.All operations to or from an endpoint pass through anendpoint gateway—the gateway receives a distribution request,determines the targets, downloads and executes thefps_installmethodon the endpoints to perform the requested Software Distributionoperation, and returns final endpoint distribution results to the sourhost or the parent repeater.

6–12 Version 3.6


Troubleshooting

ts, areG1.

e

essthe

the

ce

Distributing from Source Host/TMR Server to Endpointsvia a Gateway

In the simplest distribution scenario involving gateways and endpointhe server and source host are the same machine and the targetsEP1 and EP2, both of which are assigned to an endpoint gateway

If you distribute a file package to EP1 and EP2 in this diagram, thfp_push method starts thefp_dist method—both of which run on theTMR server because it is also the source host. If the file package is lthan 16KB, the source machine oserv transfers the file package togateway oserv over port 94. The gateway then initiates thefps_installmethod on the target endpoint and distributes the file package to endpoint, wherefps_install works with the lcfd daemon to receive andinstall the file package.

If the file package is larger than 16KB, thefp_dist method on thesource host oserv contacts therpt method on G1 and passes the IPaddress of the source host and a port number over which the filepackage data stream will be transferred. The gatewayrpt method thenperforms the following two actions:

■ Uses the dkey information to open an IOM channel on the sourhost

■ Invokes thefps_install method on the endpoint


endpointgateway, G1

EP1 EP2



m toingilen

int

a

2,1’sway

n

the

ut

The source machine begins transmitting the file package data streaG1, where the file package is placed in G1’s staging area. This stagarea serves as a temporary cache from which G1 distributes the fpackage to thefps_install method on each of the target endpoints. Othe endpoint,fps_install and the lcfd daemon unpack and install thefile package. After the distribution has successfully (orunsuccessfully) completed, thefps_install method on the endpointreturns distribution status to therpt method on the gateway. Thegatewayrpt method, in turn, returns final distribution status to thefp_dist method on the source machine only after each target endpohas returned its distribution status to the gateway.

Distributing from Source through Multiple Gatewaysand Repeaters

This scenario extends the distribution hierarchy by configuringrepeaters, managed nodes, endpoint gateways, and endpoints in multi-tiered TMR environment. In this illustration, the clients of thedistribution are managed nodes MN2 and MN4, endpoint gateway Gand endpoints EP4 and EP5. Both MN2 and G2 are specified in Rrepeater range. Endpoints EP4 and EP5 are associated with gateG2, and MN4 is configured in G2’s repeater range. Recall that thegateway has the Mdist repeater functionality built in and can functioas a repeater in the TMR environment. In this instance, thewrptcommand has been used to add MN4 to G2’s repeater range. SeeTME 10 Framework Planning and Installation Guidefor informationabout using and configuring endpoint gateways. For information abo

6–14 Version 3.6


Troubleshooting

ed

,

thewrpt command, refer to theTME 10 Framework ReferenceManual.

If you distribute a file package from the source host to the clients listearlier, the following sequence of events occur:

■ The fp_push method starts thefp_dist method on the sourcehost, R2.

■ The fp_dist method invokes the MDist service to contact therepeater managerobj_route method on the TMR server anddetermine the distribution path. Using this routing informationthe source host contacts therpt method on R1.

■ Therpt method on R1 invokes thefps_install method on each ofits clients, MN2 and G2. Thefps_install methods on these twoclients then receive and install the file package from R1.

TMR server

R2 andG1

MN3

EP2 EP3

EP1

R1

MN1

MN2

G2

EP5EP4MN4

sourcehost

MN5


Distributing to PC Managed Nodes

2,

the

xtileengeded3.edthee

■ Therpt method on R1 contact therpt method on G2 to distributeto MN4. G2 invokes thefps_install method on MN4, whichunpacks and installs the file package.

■ To distribute to the endpoints, thefp_dist method on the sourcecontacts the gatewayrpt method on G2.

■ The gateway invokes thefps_install method on each of itsendpoints.

■ The source machine begins transmitting the file package to Gwhere the file package is cached in G2’s staging area.

■ G2 distributes the file package to thefps_install method on EP4and EP5. On each endpoint,fps_install unpacks and installs thefile package.

■ After distributions have successfully (or unsuccessfully)completed, thefps_install methods on the MN2 and G2individually send back distribution status to thefp_dist methodson the source via their repeater. Likewise, thefps_install methodon MN4 sends back distribution status to thefp_dist method onthe source via its repeaters G2 and R1.

■ Endpoints EP4 and EP5 return their statuses to the parentrptmethod on G2. Only after G2 has received distribution statusfrom each of these target endpoints does it return finaldistribution status to thefp_dist method on the source via R1.

Distributing to PC Managed NodesAs you initiate a file package distribution to a PC managed node, source machine determines the size of the file package. If the filepackage is larger than 16KB, the source machine allocates the neavailable port number and opens an IOM connection to listen for a fpackage request from the target machine. The source machine thpasses a dkey to the PC managed node’s proxy, which is a mananode with which the PC managed node is associated. The managnode then passes the dkey to its PC managed node over port 654Specifically, the dkey is passed to the PC agent on the PC managnode. The IP address in the dkey is that of either the source host, ifdistribution is point-to-point, or of the PC managed node’s proxy. Th

6–16 Version 3.6

Distributing to PC Managed Nodes

Troubleshootingey,ion

y.ectedent.e hosts itshe

s3)

es

dkey also includes the allocated port’s number. After sending the dkthe PC managed node’s proxy waits for the agent to return completstatus.

Meanwhile, the agent on a PC managed node connects to the IOMchannel specified by the IP address and port number from the dkeOnce the source host or repeater detects that the PC agent is connto the IOM channel, it sends the file package data stream to the agThe agent reads and processes the data stream. When the sourcor repeater finishes sending the file package data stream, it closeIOM connection. Similarly, when the PC agent finishes processing tfile package data stream, it closes its connection and returnscompletion status to the PC managed node’s proxy.

During a distribution to a PC managed node, thefp_pushandfp_distmethods are executed in the same manner as in distributions tomanaged nodes. Thefps_install method on the PC managed node,however, follows a different communication strategy.

If the distribution occurs directly from the source host to the PCmanaged node. thefp_dist method contacts the PC managed node’proxy (on port 94), which then contacts the PC agent (on port 654and starts thefps_install method on the PC managed node. Thefps_install method contacts the source host (on port 94) and receivthe file package.


Troubleshooting Tips

lsoe

N.om

,en

d;

yngess

Consider, however, the following distribution diagram in which thedistribution occurs from the source host to the PC managed nodethrough the PC managed node’s proxy and a repeater site.

In this scenario, the source host contacts PCMN’s proxy, which is athe server. Specifically, thefp_dist method on the source host starts thfps_install method on PCMN’s proxy and passes a dkey. Thefps_install method then sends the dkey to the PC agent on the PCMThe agent on PCMN opens an IOM channel to receive the data frthe source host.

If, however, you distribute a file package to MN1, MN2, and PCMNSH would contact the server and R1. The server and R1 would throute the file package accordingly to MN2, MN1, and PCMN.Remember, though, that the PC’s managed node is always involveR1 contacts the PC managed node’s proxy, which contacts the PCmanaged node.

Troubleshooting TipsProblems encountered during file package distributions are usuallcaused by configuration, networking, or target problems. Dependion the situation, Software Distribution provides a number of sourcof information about errors. The following list describes a few stepthat can often resolve problems that may arise:

TMR serverandPCMN proxy

MN2MN1 PCMN

R1

sourcehost

6–18 Version 3.6


Troubleshootingble.y’s

an

lly

utrs

,

ers.

to

,cegte

e

a

■ If you can successfully distribute one file package, but are unato distribute a similar one, examine the file package definitionThe file package definition enables you to view every propertand option set for a file package. Also, check the file packageattributes; thewgetfpattr command enables you to list allattributes set for a file package.

■ If you can successfully distribute a file package that is less th16KB but you cannot distribute a larger one, check fornetworking problems regarding IOM channels. This is especiatrue in the case where network traffic must pass through afirewall.

■ If you can successfully distribute a file package to one target ba distribution to multiple targets fails, ensure that the repeateare optimized and configured correctly. Also, if you havenetwork storms, examine the MDist parameters. In particularcheck the value of themaxconnparameter. By default it is set to100, which may be too high for some repeater machines. Thwrpt command enables you to list and set repeater paramete

■ If you can successfully distribute a file package to a managednode but not to a PC managed node, list the PCs properties verify if your PC is configured incorrectly.

■ If you can no longer distribute to an endpoint to which youpreviously were able to send distributions, ensure that theendpoint is connected to its gateway.

In general, the first step in troubleshooting is to consult the log filewhich contains more information than a Software Distribution notigroup entry or an e-mail sent about the file package operation. Lofiles provide a detailed list of successful or failed attempts to distribufile packages for each target. Theappend_logkeyword is set in the filepackage definition file. Check this file to verify if theappend_logkeyword is set. If it is, the log file will contain information aboutmultiple file package operations. See Chapter 1, “File PackageDefinitions” for information about keyword settings in the file packagdefinition file.

For more in-depth information about the file package and forinformation that may help you determine why a distribution behaved



t,

onds,ns

s

and

es

et

g

n

ile

certain way, examine the file package definition’s keywords, file lisand exclude file list. The file package attributes and repeaterconfiguration may also provide a clue to why a file package operatibehaved as it did. In addition to the above-listed files and commanensure that the configuration programs are in the specified locatioand that they are properly written.

The following sections provide more information about tips and trickthat may help you debug an unsuccessful file package operation.

Examining the File Package DefinitionBecause the file package definition enables you to set all propertiesoptions, including those only available using export/import, youshould examine the keyword settings. In particular, check the valufor the following keywords.

UNIX Only postproc and preprocSpecify encryption and decryption filters through whichthe file package data stream is run before and after adistribution.

stop_on_errorSpecifies whether to stop (fail) a distribution to a targwhen any error (fatal and non-fatal) occurs.

backup_fmtSpecifies whether and where to backup any files beinoverwritten by the files distributed in the file package.

list_path Specifies where to write a list of files distributed to atarget.

prog_env Sets the environment for the configuration programs oa target. (This keyword on applies to UNIX and NTplatforms.)

log_file Specifies the file to which log information is written.

log_host Specifies the machine on which the log file resides.

Also, ensure that the correct files or directories are included in the flist and exclude file list sections of the file package definition.

6–20 Version 3.6


Troubleshooting

frk,

ys

n

Verifying Repeater Parameters and ConfigurationsSoftware Distribution relies heavily on the MDist service in the TME10 Framework. This MDist service, enabled through the use ofrepeaters, is configured with thewrpt command. Several arguments othis command may help you troubleshoot problems with your netwoincluding the following options to this command:

always Configures the repeater so that distributions must alwagot through the repeater.

–g Lists all repeaters.

–q Maps the route of a distribution. This command draws aASCII map of the file packages route. For example, ifyou distribute a file package to MN1 in the followingdiagram:

the output of thewrpt -q command will be similar to thefollowing:

pescado{root}: wrpt -q SH MN1

--[RPT:SH [3]] |--[RPT:R1 [1]] | |--MN1 [46] |

–t Displays and changes individual repeater siteparameters.

TMR serverandPCMN proxy

MN2

MN1 PCMN

R1

sourcehost(SH)



.

r.

ng. Bytiontlyoad.

ata.

ted.

hy

e

oeds on

–L Lists active distributions.

–R Lists routing information for a distribution in progress

–e Lists endpoints that are served by a gateway repeate

In addition to these arguments, you may want to consider configuria machine that is continually used as a source host as a repeaterconfiguring the source host as a repeater, you can tune communicaparameters of the machine so that the file package is routed direcfrom the source host to the targets. This saves time and network l

Checking lost-n-foundTivoli provides alost-n-found collection on the server to storedatabase objects that are “orphaned” due to broken links or lost dTivoli transfers file packages that have encountered one of thefollowing problems to thelost-n-found collection:

■ The file package source host no longer exists.

■ The log host no longer exists.

■ A nested file package has been deleted.

■ The parent file package of a nested file package has been dele

In any of these cases, thewchkdb method moves the file package tothe lost-n-found. Use thewls /lost-n-found command to list thecontents of this collection. Check the notice groups to determine wthe file package was moved—a notice is generated anytime a filepackage is moved to thelost-n-found collection. Use thewmvfpobjcommand to move the file package from thelost-n-found collection toa profile manager. Finally, correct the problem that initially moved thfile package before distributing it.

Checking the Default Directory on a Target SystemWhen specifying file package options to set platform-specificinformation, you must designate a valid destination directory pathwhere the distributed files will reside on the target machine. If you dnot specify a valid destination directory, the file package is distributto a default destination on the target system, and the distribution ilogged as successful. Tivoli determines the default location based

6–22 Version 3.6


Troubleshootingts

e

the platform type of the subscribing machine. The following table listhe default location for each subscriber and platform type:

For example, if you distribute a UNIX file package, for which you havspecified/data as the destination directory, to a Windows NTendpoint, TME 10 distributes this file to therun_dir directory setting.You can view this setting for any endpoint with thewadminepcommand, as follows:

pescado{root}: wadminep coral view_config_info

which lists the following information about the endpoint,coral:

TargetPlatform

Subscriber Type

Managed Node Endpointa PC Managed Nodeb

UNIX $DBDIR directoryLocation specified intherun_dir directory

Windows NT $DBDIR directoryLocation specified intherun_dir directory

The directory where thePC agent is installedc

Windows 95 Location specified intherun_dir directory

The directory where thePC agent is installed

Windows 3.1 Location specified intherun_dir directory


OS/2 Location specified intherun_dir directory


Netware Location specified intherun_dir directory

SYS:/ drive

Shaded regions indicate that the platform type is not applicable for this subscriber.a. To determine the location of therun_dir directory, enter the following command at the TMRcommand line: wadminepmachine_nameview_config_info, wheremachine_nameis the endpointmachine name.b. The PC agent, by default, is installed to \TIVOLI\TMEAGENT directory of the drive where theoperating system is installed.c. This directory is%windir%\SYSTEM32 for the service PC agent.



ileh a

red

te

t

n

s

Performing browse mode ‘view_config_info’ on endpoint‘coral’machineid = YK4G83F8WQJRYZ1RL1HG0000058Einterp = w32-ix86lcfd_port = 6221gateway_port = 6221log_threshold = 1lcfd_version = 4logfile = C:\Tivoli\lcf2\dat\4\lcfd.logconfig_path = C:\Tivoli\lcf2\dat\4\last.crun_dir = C:\Tivoli\lcf2\dat\4bin_dir = C:\Tivoli\lcf2\bin\w32-ix86\mrtstage_dir = C:\Tivoli\lcf2\bin\w32-ix86\mrt\upgradeupgrade_dir = C:\Tivoli\lcf2\bin\w32-ix86\mrt\upgradelib_dir = C:\Tivoli\lcf2\bin\w32-ix86\mrtcache_loc = C:\Tivoli\lcf2\dat\4\cachecache_index = C:\Tivoli\lcf2\dat\4\cache\Index.v5cache_limit = 20480000log_size = 1024000log_queue_size = 1024

Check in the appropriate default directory if you have distributed a fpackage without error and cannot locate the distributed data. In succase, you must copy the data from the default location to the desidestination directory.

Verifying Setup for EndpointsYou can verify the setup of endpoint systems when trying to distribufile packages. This can include:

■ Verifying the endpoint connection. Thewep command providesa list of all endpoints in a TMR and their assigned gateways,retrieves and sets endpoint information, migrates an endpoinfrom one gateway to another, or updates any endpoint datachanges within a TMR. This command lists information in theendpoint list that is maintained by the endpoint manager.

■ Verifying endpoint configuration settings. Thewadminepcommand set with theview_config_info option listsconfiguration settings for a particular endpoint.

■ Verifying the gateway log. After configuring a gateway, you caset theset_debug_level option to thewgateway command totrack information about the gateway. Thewgateway commandlists gateway object identification numbers, names, and statuwithin a TMR.

6–24 Version 3.6


Troubleshooting

e’s ather

C’srePC

n.

resr

T,

,

Verifying Setup for PC Managed NodesYou can verify configuration settings when trying to distribute filepackages to PC managed nodes. These can include:

■ Verifying the PC managed node’s proxy. The PC managed nodobject cannot be moved once it is created or associated withmanaged node. It is not beneficial to select a managed node othan the server unless you select a repeater. Ensure that the Pmanaged node is up and available to the network. Also, ensuthat you are able to ping the repeater or source host from themanaged node.

■ Verifying which stack is running on the PC. The PC agentssupport a limited list of stacks, available in your Frameworkrelease notes.

■ Verifying how much memory is available on the PC. SoftwareDistribution uses memory and disk space for buffering duringdistributions. See the chapter concerning the distributionenvironment and repeater parameters in theTME 10 SoftwareDistribution User’s Guidefor examples of checking memory anddisk space. Otherwise, see your stack and PC documentatio

■ Verifying how many sockets are available. The PC agent requiat least 10 sockets; see your stack and PC documentation foinformation about checking socket availability.

■ Verifying if the _DEFAULT.PIF file is configured to run in thebackground.

■ Verifying where the agent log files are written—TEMP, anenvironment variable, or to the console. Also, on Windows Nthe service agent uses the NT event log.

■ Verifying if a configuration program to run on the PC has acarriage return or Ctrl-M (̂M ) at the end of each line.

■ Verifying the PC agent configuration as it is set up in theTMEAGENT.CFG file (see below).

Aside from the PC managed node being available on the networkrunning an agent, and being a valid PC managed node during adistribution, theTMEAGENT.CFG file may be the most important



h

nt

yn

d

ntr.

kn.e

s

the

lts

factor on the PC side of a distribution. This file is installed in the\ETCdirectory and defines how Software Distribution communicates witthe PC, including the following sections.

[TCPIPAGENT]The entries under this section are used by the IP ageand identify the PC managed node’s proxy andinformation used by the UserLink (DHCP) service. Thealso identify the base directory of the agent, the locatiomessage catalog, information for IP synchronization,NetWare options, Windows icon and menu options, anstack information.

[IPXAGENT]The entries under this section are used by the IPX ageand include information used by the NetWare repeate

See theTME 10 Framework Planning and Installation Guidefor moreinformation about theTMEAGENT.CFG file.

Performing Miscellaneous Debugging TricksOther debugging tricks include:

■ Using theodstatcommand. This command enables you to checthe methods running on a particular oserv during a distributioThe fps_install method should be running for each target of thfile package. If you use this command on the source host orserver, not allfps_install methods are visible if the PC managednode is running under a repeater. In this case, use theodstat –ocommand to list methods on a specified managed node.

■ Creating similar file packages if a distribution is not behaving aexpected. You can clone a file package using the desktop,command line, and by editing the file package definition.Distribute each file package and compare the results.

■ Creating the file package in the same TMR as the targets of distribution if you are having problems distributing targets inanother TMR. Distribute the file package and compare the resuwith the failed distribution.

■ Configuring the PC managed node’s proxy as a repeater.

6–26 Version 3.6


Troubleshooting
■ Monitoring the network and packet movement.
■ Configuring repeaters by subnet.

These tricks enable you to pinpoint minute file package problems.Using these, you can track methods, compare file packages, andproperly configure your distribution environment.



6–28 Version 3.6

Object C

onsistency

ck

r

his

ject

7Object Consistency

TME 10 Software Distribution creates the FilePackage and AutoPaobjects, which have relationships with other objects such asManagedNode, PolicyRegion, and ProfileManager. Objectconsistency is vital to Software Distribution functionality, and in ordefor Software Distribution to function correctly, these relationshipsamong objects must be maintained. This chapter describes how tconsistency is automatically or manually enforced.

Object consistency is checked by the following operations:

In addition to these operations, an administrator can run thewchkdbcommand to check the database for FilePackage and AutoPack obconsistency. This command invokes thecheck_db andfix_dboperations, which check for and fix any inconsistencies detected.

7

OperationObject Type

CheckedInvoked When

fp_name_change FilePackage A file package is renamed

remove_fp FilePackage A file package is deleted

host_name_change AutoPack,FilePackage

A managed node is renamed

remove_host AutoPack,FilePackage

A managed node is deleted


The fp_name_change Operation

tos

filested

e to

ts

. Ifthe

en

n

When an object is found to be in an inconsistent state, it is movedthe lost-n-found collection. The last section of this chapter provideinstructions on moving objects from thelost-n-found collection sothat it can be repaired and used.

The fp_name_change OperationSoftware Distribution automatically invokes thefp_name_changeoperation for every file package when an administrator changes apackage name. If the file package whose name was changed is nein another file package, thefp_name_change operation changes thename of the nested file package to the new name and posts a noticthe Software Distribution notice group.

For example, suppose file packageB is nested in file packageA. If anadministrator changes the name of file packageB to C, thefp_name_changeoperation checks each file package. When it detecthat file packageB is nested in file packageA, it changes the nestedreference of file packageB to C and logs a notice to the SoftwareDistribution notice group.

The remove_fp OperationSoftware Distribution automatically invokes theremove_fpoperationfor every file package when an administrator deletes a file packagethe deleted file package was nested in another, this operation movesnestingfile package from the profile manager in which it resides to thlost-n-found collection and posts a notice to the Software Distributionotice group.

For example, suppose file packageB is nested in file packageA. If anadministrator deletes file packageB, theremove_fpoperation detectsthat file packageB is nested in file packageA. This operation thenmoves file packageA to thelost-n-found collection and logs a noticeto the Software Distribution notice group. It does not remove filepackageB as a nested file package ofA.

To distribute a file package that was moved to thelost-n-foundcollection, you must first move the file package back to the profilemanager in which it originally resided. See “Moving Objects Betwee

7–2 Version 3.6

The host_name_change Operation

Object C

onsistencyecksack.

eject

gesdk ishe

f

ode

.

agedckcteds

Collections” on page 7-5 for instructions on moving file packagesfrom thelost-n-found collection.

The host_name_change OperationThehost_name_change operation is invoked by the TME 10Framework when a managed node is renamed. This operation chthe log host of each file package and the source host of each AutoP

Note: Thehost_name_changeoperation does not check the sourchost of each file package because only the source host’s obID is stored. It also does not check the log host of eachAutoPack, which is encoded in the AutoPack’s archive file.

If the file package log host is what was changed, this operation chanthe log host name to the new managed node name. If the renamemanaged node is the host of an AutoPack, the path to the AutoPacupdated with the managed node’s new name. In both instances, thost_name_change operation posts a notice to the SoftwareDistribution group.

For example, suppose thefuji managed node is specified as the host otheMSOffice AutoPack. If an administrator changes the name ofmanaged nodefuji to denali, thehost_name_change operationchecks each AutoPack’s host. When it detects that the managed nfuji is specified as the host of theMSOffice AutoPack, it makes thechange and logs a notice to the Software Distribution notice group

The remove_host OperationThe Framework automatically invokes theremove_host operationwhen an administrator deletes a managed node. If the deleted mannode is the source host or log host for a file package, or if an AutoParesides on the deleted managed node, this operation moves the affefile package or AutoPack from the profile manager in which it resideto thelost-n-found collection. It also posts a notice to the SoftwareDistribution notice group describing the action.

For example, suppose the managed nodedenali is specified as the loghost for theDemoSWfile package. If an administrator deletesdenalifrom the TMR, theremove_host operation detects that the log host


The wchkdb Command

for

s in

e

10ge

ded

ilege

that

n

ms

n

specified for theDemoSWfile package is not valid. This operationthen moves theDemoSWfile package to thelost-n-found collectionand logs a notice to the Software Distribution notice group.

To distribute a file package or AutoPack that was moved to thelost-n-found collection, you must first move the file package orAutoPack back to a valid profile manager. See the following sectioninstructions on moving objects from thelost-n-found collection.

The wchkdb CommandThewchkdb command detects, reports, and corrects inconsistenciethe TME 10 environment. Refer to theTME 10 Framework ReferenceManualfor a complete description of this command. In particular, thwchkdb command performs the following checks on SoftwareDistribution objects:

■ The file package source host to ensure that it is a valid TME object reference; the source host is recorded in the file packaas aManagedNode object reference.

■ The managed node on which the Software Distribution log fileresides, as indicated by thelog_hostkeyword, to ensure that it isthe name of a valid managed node; this managed node is recorin the file package definition.

■ Nested file packages to ensure that they are names of valid fpackages; nested file packages are recorded in the file packadefinition as file package names.

■ The managed node on which the AutoPack resides to ensureit is valid.

If inconsistencies are present when an administrator issues thewchkdb –u command, notices are logged to the Software Distributioand Diagnostics notice groups. (Thewchkdb –ucommand updates theTME 10 resource database and fixes discrepancies.)

In addition, file packages and AutoPacks with any of these probleare moved from the profile manager in which they reside to thelost-n-found collection. If an object is moved to thelost-n-foundcollection, a notice to this effect is logged to the Software Distributioand Diagnostics notice groups. You can list the contents of the

7–4 Version 3.6

Moving Objects Between Collections

Object C

onsistency

file

lost-n-found collection using thewls /lost-n-found command. Thiscommand lists the contents of the collection for each TMR.

Moving Objects Between CollectionsThe remove_fp andremove_host operations automatically moveFilePackage and AutoPack objects from their original collection(profile manager) to thelost-n-found collection. The objects thatreside inlost-n-found reference a deleted file package or managednode. Because you cannot distribute or modify a file package orAutoPack from thelost-n-found collection, you must first move it toa valid profile manager. Thewmvfpobj andwmvapobj commandsenable you to do this. Use these commands to regain access to thepackage or AutoPack after you correct the problems.

See theTME 10 Software Distribution Reference Manual for acomplete description of thewmvfpobj andwmvapobj commands.


Moving Objects Between Collections

7–6 Version 3.6

e

Index

Aadding

block of statements into a file 2-46directories and files, using wildcard

characters 1-3entries to a path statement in a registry

hive 2-12icons to a Windows Program Manager

group 2-9lines to a file 2-48

advanced featuresappending notices to log files 1-12backup format 1-13creating intermediate directories at the

target 1-13default destination directory 1-14defaults

gid for directories distributed toUNIX targets 1-67

gid for files distributed to UNIXtargets 1-68

mode of distributed directories1-14

modification time of file packageentries 1-15

uid for directories distributed toUNIX targets 1-67

uid for files distributed to UNIXtargets 1-68

directory path to log file 1-21input files

for source after program 1-58for source before program 1-59residing on the source host for a

NetWare target 1-33,

1-35, 1-37, 1-40,1-41, 1-43

residing on the source host for a OS/2target 1-47, 1-52

residing on the source host for aUNIX target 1-61,1-63, 1-64, 1-66,1-68, 1-70

residing on the source host for aWindows 95 target 1-82,

1-84, 1-86, 1-87,1-89, 1-92

residing on the source host for aWindows NT target1-24, 1-25, 1-27,1-28, 1-30, 1-32

residing on the source host for aWindows target 1-71,1-73, 1-75, 1-76,1-78, 1-81

residing on the source host for anOS/2 target 1-45, 1-49,

1-50, 1-53overwriting

files at the target 1-23older files on a target 1-57

process filtersfor file package on source host

1-55for file package on target 1-56

processing nested file packages before thfile package contents 1-23

putenv string before running a UNIXconfiguration program 1-56

removingconfiguration programs from target

after they run 1-20extraneous files from a target1-57

skipping distribution if source beforeprogram exit with non-zero

TME 10 Software Distribution Reference Manual Index–1

1-60source after program 1-58source before program 1-60timeout period

optional distribution to Windows 95targets 1-91

optional distribution to Windowstargets 1-80

uidssource after program 1-57source before program 1-59UNIX after program 1-61UNIX after_removal program

1-63UNIX before program 1-64UNIX commit program 1-66UNIX on_error program 1-68UNIX removal program 1-70

using checksums to detect differencesbetween source and target files1-19

verifying distribution using a checksum1-15

ap_def_autopack_file method 3-33ap_def_autopack_host method 3-34ap_val_autopack_file method 3-35ap_val_name method 3-37append_log keyword 1-12, 2-76assigning policy to a policy region 3-27attributes

behavior_flags 2-67check_nested 2-69check_no_src_host 2-70default_push_mode 2-69default_push_type 2-70destination_flags 2-36, 2-68fp_info 2-69fp_size 2-70lenient_distribution 2-69push_time 2-70

src_host 2-69stage_area 2-39, 2-71

Bbackup_fmt keyword 1-13, 2-77behavior_flags attribute 2-67bitmaps 6-26

Ccheck_nested attribute 2-69check_no_src_host attribute 2-70commands

cpio 1-6object references 2-2odstat 7-6PC 2-5syntax 2-2UNIX 2-4waddclnt 2-7waddicon 2-9waddpath 2-12wchkdb 8-4wclrblk 2-13wclrline 2-15wcpfpblock 2-17wcpyfile 2-19wcrtfpblock 2-20wcrtnwms 2-7wdirnwc 2-7wdistfp 2-22wdistfpblock 2-26wdskspc 2-29weditini 2-31wexecnwc 2-7wexprtfp 2-33wgetfpattr 2-35wgetkey 2-40

Index–2 Version 3.6

wgetnwcfile 2-7wgetnwms 2-7wgetval 2-42wimprtfp 2-44winsblk 2-46winsline 2-48winstruct_file 2-50wlstclnt 2-7wmrgini 2-52wmvapobj 2-53wmvfpobj 2-54wpolclnt 2-7wputnwcfile 2-7wrestart 2-55wrmfp 2-56wrmfpblock 2-58wrmvclnt 2-7wrplblk 2-61wrplline 2-63wrunprog 2-65wseterr 2-66wsetfpattr 2-67wsetfpcontents 2-72wsetfpopts 2-74wsetfpprgs 2-86wsetnwms 2-7wsettrus 2-97wsetval 2-99wswdistrim 2-101

configuration programsinput files 4-3PC examples 4-11previewing 2-23return codes 4-3UNIX examples 4-6

configuration repositoryupdating with Software Distribution

operations 2-101copying fpblocks to a target 2-17create_dirs keyword 1-13, 2-77

creatingfpblocks from existing file package

definitions on a target 2-20PC configuration programs on UNIX

machines 4-11customizing TME 10 Software Distribution

6-1bitmap example using TME 10 AEF

6-26bitmaps and icons 6-26dialog example using TME 10 AEF6-4dialogs 6-2using TME 10 ADE 6-27

methods 6-28, 6-30

Ddata encryption and decryption 1-55data formats of file package definitions 1-2default_dest keyword 1-14, 2-77default_dir_mode keyword 1-14, 2-79default_file_mode keyword 1-14, 2-79default_mtime keyword 1-15, 2-78default_push_mode attributes 2-69default_push_type attribute 2-70descend_dirs keyword 1-15, 2-77destination_flags attribute 2-36, 2-68developing NLMs 4-4dialog descriptors 6-2dialogs, Execute a Query 7-8directories

descending into 1-4paths 1-6

disk space, verifying 2-29distributing

directories 1-4file packages to subscribers 2-22files in a fpblock to a target 2-26optional 1-80, 1-91


o

to nonsubscribers 2-69distribution

modes 2-69types 2-70

do_checksum keyword 1-15, 2-80do_compress keyword 1-15, 2-77

Eencrypting and decrypting data 1-55environment space 4-5environment variables, distributing 1-6example configuration programs

PCchecking disk space 4-11preparing for a distribution 4-13

UNIXchecking architecture type 4-9rebooting after distributing 4-6removing files from the destination

directory 4-7running an installation script after a

distribution 4-8Execute a Query dialog 7-8exporting file packages 2-33

Ffile exclusions 1-7file package attributes

retrieving 2-35setting 2-67

file package blocks (fpblocks)copying to a target 2-17creating from existing file package

definitions 2-20distributing files 2-26removing files from 2-58

file package definitionexclude files 1-7file list 1-3format 1-2keyword options 1-3keywordsSee keywordsnested file packages 1-7

file package properties, descending intdirectories 1-4

file_cksums keyword 1-19, 2-78firewalls, troubleshooting distributions7-19flist 1-3follow_links keyword 1-20, 2-78fp_def_excludes method 3-41fp_def_flist method 3-42fp_def_src_host method 3-45fp_dist method 7-1, 7-5fp_info attribute 2-69fp_push method 7-1

steps during distribution 7-4fp_size attribute 2-70fp_val_delete_src_host method 3-39,

3-46fp_val_excludes method 3-48fp_val_flist method 3-50fp_val_name method 3-52fp_val_nestedlist method 3-54fp_val_operation method 3-56fp_val_options method 3-58fp_val_src_host method 3-60fps_install method 7-1, 7-5

Iicons 6-26importing file packages 2-44increasing environment space on a PC 4-5


INI filemerging groups and variables from

several files 2-52modifying 2-31

install_progs keyword 1-20, 2-78interobject message (IOM) 7-6IOM channel 7-2IOM service 7-2

Kkeep_paths keyword 1-21, 2-78keywords 1-8

append_log 1-12, 2-76backup_fmt 1-13, 2-77create_dirs 1-13, 2-77default_dest 1-14, 2-77default_dir_mode 1-14, 2-79default_file_mode 1-14, 2-79default_mtime 1-15, 2-78descend_dirs 1-15, 2-77do_checksum 1-15, 2-80do_compress 1-15, 2-77file_cksums 1-19, 2-78follow_links 1-20, 2-78install_progs 1-20, 2-78keep_paths 1-21, 2-78list_path 1-21, 2-78log_file 1-22, 2-79log_file_gid 1-22log_file_mode 1-22log_file_uid 1-22log_host 1-23, 2-78mail_id 1-23, 2-77modifiers 1-23nested_first 1-23, 2-79no_overwrite 1-23, 2-79nt_after_input_from_src 1-24nt_after_input_path 1-24nt_after_option 1-24

nt_after_prog_from_src 1-25nt_after_prog_path 1-25nt_after_removal_input_from_src1-25nt_after_removal_input_path 1-26nt_after_removal_option 1-26nt_after_removal_prog_from_src 1-26nt_after_removal_prog_path 1-27nt_before_input_from_src 1-27nt_before_input_path 1-27nt_before_prog_from_src 1-28nt_before_prog_path 1-28nt_before_skip_non_zero 1-28nt_commit_input_from_src 1-28nt_commit_input_path 1-29nt_commit_option 1-29nt_commit_prog_from_src 1-29nt_commit_prog_path 1-30nt_on_error_input_from_src 1-30nt_on_error_input_path 1-30nt_on_error_option 1-31nt_on_error_prog_from_src 1-31nt_on_error_prog_path 1-31nt_platform_prefix 1-31, 2-83nt_removal_input_from_src 1-32nt_removal_input_path 1-32nt_removal_option 1-32nt_removal_prog_from_src 1-33nt_removal_prog_path 1-33nw_after_input_from_src 1-33nw_after_input_path 1-34nw_after_prog_from_src 1-34nw_after_prog_path 1-35nw_after_removal_input_from_src

1-35nw_after_removal_input_path 1-36nw_after_removal_prog_from_src

1-36nw_after_removal_prog_path 1-37nw_before_input_from_src 1-37nw_before_input_path 1-37nw_before_prog_from_src 1-38nw_before_prog_path 1-38


nw_before_skip_non_zero 1-38nw_bindery 1-39, 2-81nw_broadcast_message 1-39, 2-82nw_broadcast_mode 1-39, 2-82nw_commit_input_from_src 1-40nw_commit_input_path 1-40nw_commit_prog_from_src 1-40nw_commit_prog_path 1-41nw_context 1-41, 2-81nw_force_disconnect 1-41, 2-82nw_on_error_input_from_src 1-41nw_on_error_input_path 1-42nw_on_error_prog_from_src 1-42nw_on_error_prog_path 1-43nw_platform_prefix 1-43, 2-81nw_removal_input_from_src 1-43nw_removal_input_path 1-44nw_removal_prog_from_src 1-44nw_removal_prog_path 1-45nw_tree 1-45, 2-82os2_after_input_from_src 1-45os2_after_input_path 1-46os2_after_option 1-46os2_after_prog_from_src 1-46os2_after_prog_path 1-47os2_after_removal_input_from_src

1-47os2_after_removal_input_path 1-48os2_after_removal_option 1-48os2_after_removal_prog_from_src

1-48os2_after_removal_prog_path 1-49os2_before_input_from_src 1-49os2_before_input_path 1-49os2_before_prog_from_src 1-50os2_before_prog_path 1-50os2_before_skip_non_zero 1-50os2_commit_input_from_src 1-50os2_commit_input_path 1-51os2_commit_prog_from_src 1-51os2_commit_prog_path 1-51os2_on_error_input_from_src 1-52

os2_on_error_input_path 1-52os2_on_error_prog_from_src 1-52os2_on_error_prog_path 1-53os2_platform_prefix 1-53, 2-83os2_removal_input_from_src 1-53os2_removal_input_path 1-54os2_removal_prog_from_src 1-54os2_removal_prog_path 1-55post_notice 1-55, 2-79postproc 1-55, 2-79preproc 1-56, 2-79prog_env 1-56, 2-78progs_timeout 1-57rm_empty_dirs 1-57, 2-80rm_extraneous 1-57, 2-80skip_older_src 1-57, 2-79src_after_as_uid 1-57src_after_input_path 1-58src_after_prog_path 1-58src_before_as_uid 1-59src_before_input_path 1-59src_before_prog_path 1-60src_before_skip_non_zero 1-60src_relpath 1-6, 1-61, 2-80stop_on_error 1-61, 2-80unix_after_as_uid 1-61unix_after_input_from_src 1-61unix_after_input_path 1-62unix_after_prog_from_src 1-62unix_after_prog_path 1-62unix_after_removal_as_uid 1-63unix_after_removal_input_from_src

1-63unix_after_removal_input_path 1-63unix_after_removal_prog_from_src

1-63unix_after_removal_prog_path 1-64unix_before_as_uid 1-64unix_before_input_from_src 1-64unix_before_input_path 1-65unix_before_prog_from_src 1-65unix_before_prog_path 1-65


unix_before_skip_non_zero 1-66unix_commit_as_uid 1-66unix_commit_input_from_src 1-66unix_commit_input_path 1-66unix_commit_prog_from_src 1-67unix_commit_prog_path 1-67unix_default_dir_gid 1-67, 2-81unix_default_dir_uid 1-67, 2-81unix_default_file_gid 1-68, 2-80unix_default_file_uid 1-68, 2-81unix_on_error_as_uid 1-68unix_on_error_input_from_src 1-68unix_on_error_input_path 1-69unix_on_error_prog_from_src 1-69unix_on_error_prog_path 1-69unix_platform_prefix 1-70, 2-81unix_removal_as_uid 1-70unix_removal_input_from_src 1-70unix_removal_prog_from_src 1-71unix_removal_prog_path 1-71win_after_input_from_src 1-71win_after_input_path 1-72win_after_option 1-72win_after_prog_from_src 1-72win_after_prog_path 1-73win_after_removal_input_from_src

1-73win_after_removal_input_path 1-74win_after_removal_option 1-74win_after_removal_prog_from_src

1-74win_after_removal_prog_path 1-75win_before_input_from_src 1-75win_before_input_path 1-75win_before_prog_from_src 1-76win_before_prog_path 1-76win_before_skip_non_zero 1-76win_commit_input_from_src 1-76win_commit_input_path 1-77win_commit_option 1-77win_commit_prog_from_src 1-77win_commit_prog_path 1-78

win_on_error_input_from_src 1-78win_on_error_input_path 1-78win_on_error_option 1-79win_on_error_prog_from_src 1-79win_on_error_prog_path 1-79win_optional_dist 1-80, 2-82, 2-83win_optional_dist_timeout 1-80,

2-82, 2-83win_platform_prefix 1-81, 2-82,

2-83win_removal_input_from_src 1-81win_removal_input_path 1-81win_removal_option 1-82win_removal_prog_from_src 1-82win_removal_prog_path 1-82win95_after_input_from_src 1-82win95_after_input_path 1-83win95_after_option 1-83win95_after_prog_from_src 1-83win95_after_prog_path 1-84win95_after_removal_input_from_src

1-84win95_after_removal_input_path 1-85win95_after_removal_option 1-85win95_after_removal_prog_from_src

1-85win95_after_removal_prog_path 1-86win95_before_input_from_src 1-86win95_before_input_path 1-86win95_before_prog_from_src 1-87win95_before_prog_path 1-87win95_before_skip_non_zero 1-87win95_commit_input_from_src 1-87win95_commit_input_path 1-88win95_commit_option 1-88win95_commit_prog_from_src 1-88win95_commit_prog_path 1-89win95_on_error_input_from_src 1-89win95_on_error_input_path 1-89win95_on_error_option 1-90win95_on_error_prog_from_src 1-90win95_on_error_prog_path 1-90


a

win95_optional_dist 1-91win95_optional_dist_timeout 1-91win95_platform_prefix 1-92win95_removal_input_from_src 1-92win95_removal_input_path 1-92win95_removal_option 1-93win95_removal_prog_from_src 1-93win95_removal_prog_path 1-93

Llenient_distribution attribute 2-69limitations of NLMs 4-4list_path keyword 1-21, 2-78log_file keyword 1-22, 2-79log_file_gid keyword 1-22log_file_mode keyword 1-22log_file_uid keyword 1-22log_host keyword 1-23, 2-78lost-n-found collection

movingAutoPacks 8-5file packages 8-5

Mmail_id keyword 1-23, 2-77managed nodes

changing names 8-3removing 8-3

MDist 7-2merging groups and variables from INI files

2-52methods

fp_dist 7-1, 7-5fp_push 6-29, 7-1

steps during distribution 7-4fp_to_fpblock 6-29

fp_to_size 6-29fps_install 7-1, 7-5obj_route 7-2set_fp_name 6-30

modifiers keyword 1-23modifying groups, variables, and values in

INI file 2-31

Nnested_first keyword 1-23, 2-79NLMs, limitations of 4-4no_overwrite keyword 1-23, 2-79nt_after_input_from_src keyword 1-24nt_after_input_path keyword 1-24nt_after_option keyword 1-24nt_after_prog_from_src keyword 1-25nt_after_prog_path keyword 1-25nt_after_removal_input_from_src keyword

1-25nt_after_removal_input_path keyword1-26nt_after_removal_option keyword 1-26nt_after_removal_prog_from_src keyword

1-26nt_after_removal_prog_path keyword 1-27nt_before_input_from_src keyword 1-27nt_before_input_path keyword 1-27nt_before_prog_from_src keyword 1-28nt_before_prog_path keyword 1-28nt_before_skip_non_zero keyword 1-28nt_commit_input_from_src keyword 1-28nt_commit_input_path keyword 1-29nt_commit_option keyword 1-29nt_commit_prog_from_src keyword 1-29nt_commit_prog_path keyword 1-30nt_on_error_input_from_src keyword 1-30nt_on_error_input_path keyword 1-30nt_on_error_option keyword 1-31


nt_on_error_prog_from_src keyword 1-31nt_on_error_prog_path keyword 1-31nt_platform_prefix keyword 1-31, 2-83nt_removal_input_from_src keyword 1-32nt_removal_input_path keyword 1-32nt_removal_option keyword 1-32nt_removal_prog_from_src keyword 1-33nt_removal_prog_path keyword 1-33nw_after_input_from_src keyword 1-33nw_after_input_path keyword 1-34nw_after_prog_from_src keyword 1-34nw_after_prog_path keyword 1-35nw_after_removal_input_from_src keyword

1-35nw_after_removal_input_path keyword

1-36nw_after_removal_prog_from_src keyword

1-36nw_after_removal_prog_path keyword

1-37nw_before_input_from_src keyword 1-37nw_before_input_path keyword 1-37nw_before_prog_from_src keyword 1-38nw_before_prog_path keyword 1-38nw_before_skip_non_zero keyword 1-38nw_bindery keyword 1-39, 2-81nw_broadcast_message keyword 1-39,

2-82nw_broadcast_mode keyword 1-39, 2-82nw_commit_input_from_src keyword 1-40nw_commit_input_path keyword 1-40nw_commit_prog_from_src keyword 1-40nw_commit_prog_path keyword 1-41nw_context keyword 1-41, 2-81nw_force_disconnect keyword1-41, 2-82nw_on_error_input_from_src keyword

1-41nw_on_error_input_path keyword 1-42

nw_on_error_prog_from_src keyword1-42nw_on_error_prog_path keyword 1-43nw_platform_prefix keyword 1-43, 2-81nw_removal_input_from_src keyword1-43nw_removal_input_path keyword 1-44nw_removal_prog_from_src keyword 1-44nw_removal_prog_path keyword 1-45nw_tree keyword 1-45, 2-82

Oobj_route method 7-2object consistency

changing namesfile packages 8-2managed nodes 8-3

operations 8-1removing

AutoPacks 8-2file packages 8-2managed nodes 8-3

object paths 2-3object references

object paths 2-2registered names 2-2

odstat command 7-6operations

fp_name_change 8-2host_name_change 8-3remove_fp 8-2remove_host 8-3

optional distribution 1-80, 1-91os2_after_input_from_src keyword 1-45os2_after_input_path keyword 1-46os2_after_option keyword 1-46os2_after_prog_from_src keyword 1-46os2_after_prog_path keyword 1-47os2_after_removal_input_from_src

keyword 1-47


os2_after_removal_input_path keyword1-48

os2_after_removal_option keyword 1-48os2_after_removal_prog_from_src keyword

1-48os2_after_removal_prog_path keyword

1-49os2_before_input_from_src keyword 1-49os2_before_input_path keyword 1-49os2_before_prog_from_src keyword 1-50os2_before_prog_path keyword 1-50os2_before_skip_non_zero keyword 1-50os2_commit_input_from_src keyword1-50os2_commit_input_path keyword 1-51os2_commit_prog_from_src keyword 1-51os2_commit_prog_path keyword 1-51os2_on_error_input_from_src keyword

1-52os2_on_error_input_path keyword 1-52os2_on_error_prog_from_src keyword

1-52os2_on_error_prog_path keyword 1-53os2_platform_prefix keyword 1-53, 2-83os2_removal_input_from_src keyword

1-53os2_removal_input_path keyword 1-54os2_removal_prog_from_src keyword1-54os2_removal_prog_path keyword 1-55oserv communication 7-6

Ppolicy 3-1policy methods

default 3-2ap_def_autopack_file 3-33ap_def_autopack_host 3-34examples 3-4, 3-6, 3-28

fp_def_excludes 3-41fp_def_flist 3-42fp_def_nestedlist 3-43fp_def_options 3-44fp_def_src_host 3-45

replacing 3-25validation 3-8

ap_val_autopack_file 3-35ap_val_name 3-37fp_val_delete_src_host 3-39,

3-46fp_val_excludes 3-48fp_val_flist 3-50fp_val_name 3-52fp_val_nestedlist 3-54fp_val_operation 3-56fp_val_options 3-58fp_val_src_host 3-60setting with Tivoli commands 3-21

policy objects 3-22post_notice keyword 1-55, 2-79postproc keyword 1-55, 2-79preproc keyword 1-56, 2-79previewing, configuration programs 2-23prog_env keyword 1-56, 2-78progs_timeout keyword 1-57push_time attribute 2-70

Rrebooting a system 2-55registered names 2-3registry hives

adding an entry 2-12retrieving key values 2-40setting key values 2-99

removingblock statements from a file 2-13


file packages from targets 2-56files from an fpblock on a target 2-58lines from a file 2-15

replacingblock of statements in a file 2-61lines in a file 2-63

restarting a system 2-55retrieving

attributes of file packages 2-35registry hive key values 2-40

return codes of configuration programs 4-3rm_empty_dirs keyword 1-57, 2-80rm_extraneous keyword 1-57, 2-80running a Windows program from a DOS

batch file 2-65

Ssetting

configuration program information2-86

excluded files 2-72file lists 2-72nested file packages 2-72NetWare trustee rights 2-97registry hive key values 2-99return codes from a batch file for a

configuration program 2-66source hosts 2-72

shell commands in an flist 1-3skip_older_src keyword 1-57, 2-79src_after_as_uid keyword 1-57src_after_input_path keyword 1-58src_after_prog_path keyword 1-58src_before_as_uid keyword 1-59src_before_input_path keyword 1-59src_before_prog_path keyword 1-60src_before_skip_non_zero keyword 1-60src_host attribute 2-69

src_relpath keyword 1-6, 1-61, 2-80stage_area attribute 2-39, 2-71stop_on_error keyword 1-61, 2-80

Ttroubleshooting distributions through a

firewall 7-19trustee rights 2-97

Uunix_after_as_uid keyword 1-61unix_after_input_from_src keyword 1-61unix_after_input_path keyword 1-62unix_after_prog_from_src keyword 1-62unix_after_prog_path keyword 1-62unix_after_removal_as_uid keyword 1-63unix_after_removal_input_from_src

keyword 1-63unix_after_removal_input_path keyword

1-63unix_after_removal_prog_from_src

keyword 1-63unix_after_removal_prog_path keyword

1-64unix_before_as_uid keyword 1-64unix_before_input_from_src keyword 1-64unix_before_input_path keyword 1-65unix_before_prog_from_src keyword 1-65unix_before_prog_path keyword 1-65unix_before_skip_non_zero keyword 1-66unix_commit_as_uid keyword 1-66unix_commit_input_from_src keyword

1-66unix_commit_input_path keyword 1-66unix_commit_prog_from_src keyword


1-67unix_commit_prog_path keyword 1-67unix_default_dir_gid keyword 1-67, 2-81unix_default_dir_uid keyword 1-67, 2-81unix_default_file_gid keyword 1-68, 2-80unix_default_file_uid keyword 1-68, 2-81unix_on_error_as_uid keyword 1-68unix_on_error_input_from_src keyword

1-68unix_on_error_input_path keyword 1-69unix_on_error_prog_from_src keyword

1-69unix_on_error_prog_path keyword 1-69unix_platform_prefix keyword 1-70, 2-81unix_removal_as_uid keyword 1-70unix_removal_input_from_src keyword

1-70unix_removal_prog_from_src keyword

1-71unix_removal_prog_path keyword 1-71updating, configuration repository 2-101

Vverifying available disk space 2-29

Wwaddclnt command 2-7waddpath command 2-12wchkdb command 8-4wclrblk command 2-13wclrline command 2-15wcpfpblock command 2-17wcpyfile command 2-19wcrtfpblock command 2-20wcrtnwms command 2-7

wdirnwc command 2-7wdistfp command 2-22wdistfpblock command 2-26wdskspc command 2-29weditini command 2-31wexecnwc command 2-7wexprtfp command 2-33wgetfpattr command 2-35wgetkey command 2-40wgetnwcfile command 2-7wgetnwms command 2-7wgetval command 2-42wildcard characters

specifying files 1-3wimprtfp command 2-44win_after_input_from_src keyword 1-71win_after_input_path keyword 1-72win_after_option keyword 1-72win_after_prog_from_src keyword 1-72win_after_prog_path keyword 1-73win_after_removal_input_from_src

keyword 1-73win_after_removal_input_path keyword

1-74win_after_removal_option keyword 1-74win_after_removal_prog_from_src keyword

1-74win_after_removal_prog_path keyword

1-75win_before_input_from_src keyword 1-75win_before_input_path keyword 1-75win_before_prog_from_src keyword 1-76win_before_prog_path keyword 1-76win_before_skip_non_zero keyword 1-76win_commit_input_from_src keyword1-76win_commit_input_path keyword 1-77win_commit_option keyword 1-77win_commit_prog_from_src keyword 1-77win_commit_prog_path keyword 1-78


win_on_error_input_from_src keyword1-78

win_on_error_input_path keyword 1-78win_on_error_option keyword 1-79win_on_error_prog_from_src keyword

1-79win_on_error_prog_path keyword 1-79win_optional_dist keyword 1-80, 2-82,

2-83win_optional_dist_timeout keyword 1-80,

2-82, 2-83win_platform_prefix keyword 1-81,

2-82, 2-83win_removal_input_from_src keyword

1-81win_removal_input_path keyword 1-81win_removal_option keyword 1-82win_removal_prog_from_src keyword1-82win_removal_prog_path keyword 1-82win95_after_input_from_src keyword 1-82win95_after_input_path keyword 1-83win95_after_option keyword 1-83win95_after_prog_from_src keyword 1-83win95_after_prog_path keyword 1-84win95_after_removal_input_from_src

keyword 1-84win95_after_removal_input_path keyword

1-85win95_after_removal_option keyword1-85win95_after_removal_prog_from_src

keyword 1-85win95_after_removal_prog_path keyword

1-86win95_before_input_from_src keyword

1-86win95_before_input_path keyword 1-86win95_before_prog_from_src keyword

1-87win95_before_prog_path keyword 1-87

win95_before_skip_non_zero keyword1-87

win95_commit_input_from_src keyword1-87

win95_commit_input_path keyword 1-88win95_commit_option keyword 1-88win95_commit_prog_from_src keyword

1-88win95_commit_prog_path keyword 1-89win95_on_error_input_from_src keyword

1-89win95_on_error_input_path keyword 1-89win95_on_error_option keyword 1-90win95_on_error_prog_from_src keyword

1-90win95_on_error_prog_path keyword 1-90win95_optional_dist keyword 1-91win95_optional_dist_timeout keyword

1-91win95_platform_prefix keyword 1-92win95_removal_input_from_src keyword

1-92win95_removal_input_path keyword 1-92win95_removal_option keyword 1-93win95_removal_prog_from_src keyword

1-93win95_removal_prog_path keyword 1-93winsblk command 2-46winsline command 2-48winstruct_file command 2-50wlstclnt command 2-7wmrgini command 2-52wmvapobj command 2-53wmvfpobj command 2-54wpolclnt command 2-7wputnwcfile command 2-7wrestart command 2-55wrmfp command 2-56


wrmfpblock command 2-58wrmvclnt command 2-7wrplblk command 2-61wrplline command 2-63wrunprog command 2-65wseterr command 2-66wsetfpattr command 2-67wsetfpcontents command 2-72wsetfpopts command 2-74wsetfpprgs command 2-86wsetnwms command 2-7wsettrus command 2-97wsetval command 2-99wswdistrim command 2-101
