omledit [Update=]library [options]*
(+|-)Clear (-) (+|-)error_Stop (+) (+|-)Verbose (-) Append=file,file,... Delete=symbol,symbol,... Extract=symbol[>file],symbol[>file],... Include=file,file,... indeX=file,file,... Replace=file,file,...
extract=sym1,sym2>xyzthe OM associated with "sym1" will be written into a file called "sym1" and the OM associated with "sym2" will be written into "xyz". Files are created if they do not already exist.
Include=file Append=file Delete=symbol Extract=symbol>file Replace=fileThe OMLEDIT instructions given in an index file are executed in the order they appear in the file. A line in an index file may also have the form
!commandin which case "command" is executed as a TSS command.
OMLEDIT lets you change the contents of an OM object library, by replacing or deleting individual OMs within the library.
The OMs are always referred to by one of their primary SYMDEFs. OMs are deleted as required to insure the uniqueness of this naming method.
If Update= is used to specify the name of the library, the Include= keyword may be omitted for modules, as in
omledit u=lib modIf Update= is not used to introduce the name of the library, the Include= keyword must be used, as in
omledit lib i=mod
A command line may have any number of Include, Delete, Extract, or indeX directives. Directives appearing on the command line are handled first, in the following order:
-- all Extracts, in the order they appear on line -- all Deletes, in the order they appear on line -- all Includes, in the order they appear on lineAfter this, directives from index files are executed, line by line. With each line in an index file, the directives are executed in the same order as the command line: Extracts, then Deletes, then Includes. Index files are processed in the order they appear on the command line.
The following example shows how to use OMLEDIT.
omledit mylib i=fc*o*edits the modules in the file "fc*o*" into the library "mylib". If "mylib" is of bad format, OMLEDIT will not overwrite it.
You can run OMLEDIT in batch using the following JCL:
$ program omledi $ limits ,45k $ prmfl **,r/c,r,cmdlib/etc/qstar $ data cz $ ascii command line $ enxThe command line following the $DATA statement is exactly the same as the OMLEDIT command line you'd use in TSS.
Copyright © 2000, Thinkage Ltd.