Description
The amblist utility
provides a UNIX interface to the AMBLIST program. With
AMBLIST, you can obtain information about object modules and executable
modules, and diagnose problems with them. Output is written to stdout
and errors to stderr.
amblist reads
control statements from standard input (stdin). One or more control
statements that identify the processing to be performed must be specified.
Each control statement line must begin with one or more blanks. Keywords
are case-sensitive and must be uppercase. Each control statement line
can be up to 80 bytes long, but only the first 70 bytes can contain
control information. Control statement lines longer than 70 bytes
might be ignored or might cause an error to be reported.
Options
- file
- The file argument can be either a path name or a data set name.
You cannot specify both a path name and a data set name at the same
time. If you do, amblist ends with an error
message and a nonzero return code.
- If a path name is specified, it can be either a UNIX file
or a UNIX directory. You can use only one path name
at a time. If a UNIX directory is used for the path
name, MEMBER must be specified on the amblist control
statement to specify the file name.
- If a data set name is specified, or more data sets can be listed
to indicate a concatenation of data sets to be searched. If a member
name cannot be specified on the data set name (such as for LISTLOAD),
it can either be specified on a control statement or omitted completely.
If the member name is omitted, then all members are processed.
Examples
- Control statement from a pipe, output redirected to a file:
echo “ LISTLOAD” | amblist a.out > a.amblist
- Control statement read interactively, output sent to terminal:
amblist hello.o
The
user must then type " LISTOBJ" (leading blank, no
quotation marks), then press CTRL-D to end the amblist processing.
- Control statement from a file, with output sent to terminal:
amblist hello.o < hello.ambctl
where
the file hello.ambctl contains a single line " LISTOBJ" (leading
blank, no quotation marks).
- Control statement from pipe, process an object data set, output
redirected to a file: contains the single line " LISTOBJ"
(leading blank, no quotation marks).
echo “ LISTOBJ” | amblist “//binder.obj(hello)” > hello.amblist
For examples of
output created when running amblist, see z/OS MVS Diagnosis: Tools and Service Aids.
Localization
amblist uses
the following localization environment variables:
- LANG
- LC_ALL
- LC_CTYPE
- LC_MESSAGES
- NLSPATH
See Localization for more
information.
Exit values
- 0
- Successful completion.
- 1
- No operands were specified, or -? was used as an option
- 2
- An incorrect option was specified.
- 3
- The AMBLIST program ended with a nonzero return code. The return
code is in message AMBU2003. Some output might have been written to
stdout.
- 4
- UNIX path names and MVS™ data
set names cannot be mixed.
- 9
- A file could not be opened. The error number is in message AMBU2010.
- 10
- Dynamic allocation failure. Message AMBU2010 indicates the return
code, error code, and the information code from dynamic allocation
(SVC 99). Additional messages that describe the error might have
been written to stderr.
Usage notes
- You cannot use the DNN= control statement keyword except when
specifying the default value of SYSLIB because amblist does
not provide a facility for the use of any other data definition name.
- You must specify at least one library when invoking amblist.
Do not use LISTLPA because it is obsolete.