Specifications

Chapter 8. Problem handling 97
provider, or simply kept on your Linux system for potential use later. The senderrdata
command can manage the FTP operation to IBM. These files (on the receiving system at
IBM) are automatically deleted after a few days unless a formal problem (PMR or equivalent)
event is opened; this can be done by your zPDT service provider.
Figure 8-1 provides an overview of problem data handling. If snapdump data is sent to IBM
(as outlined in the figure) then the senderrdata option to create a configuration file should also
be used and the results sent to IBM.
4
Figure 8-1 Problem data capture and reporting
4
Later 1090 versions may automatically combine the configuration data with the snapdump data.
Option 3 FTP/dump snapdata
snapdump ID
PMR number (if known)
branch office, country code
(leave blank)
warning about lsvpd
*File to transfer/dump: 999999.99...tar.gz
1 to FTP
Enter1
yes to save
Attempts to FTP to IBM
hangs if cannot connect.
Cntl-C to escape.
Clean option erases all
existing logs and traces
awsstart xxxxx clean
/home/ibmsys1/z1090/logs
User detects problem
during 1090 operation
$ snapdump
Logs/traces
1090 detects problem and
performs internal equivalent
of a snapdump
A severe problem may also
create Linux core files in
your home directory. These
are not managed by the
senderrdata command or by
any other 1090 function.
$ rassummary -s
Any snapdumps?
Note the ID.
Working on a
1090 problem?
Consider the --clean
option the next time
you use awsstart
No Yes
Date and time in a snapdump
matches your problem?
Want to open a problem with
the zPDT provider or add data
for existing open problem?
$ senderrdata
Saves file in /tmp
Must work through your
zPDT service provider to
open a problem with IBM
Option 5: configuration file
PMR number (if known)
warning about lsvpd
*File to transfer/dump: 999...tar.gz
1 to FTP
Enter1
yes to save
Saves file in home directory
END
Attempts to FTP to IBM
hangs if cannot connect.
Cntl-C to escape.
Look through
snapdump titles