How to troubleshoot the remote loader hanging combined with a broken-pipe message on a MainFrame RACF Computer
(Last modified: 30Jan2006)
This document (10100345) is provided subject to the disclaimer at the end of this document.
fact
Novell Identity Manager 3.0
Novell Identity Manager - RACF Driver
goal
How to troubleshoot the remote loader hanging combined with a broken-pipe message on a MainFrame RACF Computer
fix
Sometimes the remote loader hanging up on shutdown and a broken-pipe message are related. It may be a deadlock of sorts, where each end is waiting on the other. IBM describes situations where this can cause the broken-pipe message. --- Instructions For A TCP/IP Packet Trace ---
In order to troubleshoot these problems, information needs to be gathered and then Novell support should be contacted with the following information:
.. A packet trace. Instructions at the end of this message
.. A copy of the TCPIP.PROFILE
.. All messages from the driver address space (TSO messages, Java exceptions, etc)
Below are instructions for taking a trace from the RACF mainframe.
The tcp/ip address space writes packet trace information to an internal data space, the size of which is specified SYS1.PARMLIB(CTIEZB00):
TRACEOPTS
ON
BUFSIZE(8M)
This is discussed in manual "MVS Initialization and Tuning Reference".
You can get to the trace information in two ways, dump the address space or use a component trace external writer to write the trace to a dataset. Once you have the information you can use IPCS to format it.
To use a component trace external writer you must have a JCL procedure in SYS1.PROCLIB (must be here). For example:
//CTWTR PROC
//*
//* JCL for CTRACE writer.
//*
//IEFPROC EXEC PGM=ITTTRCWR,REGION=32M
//TRCOUT01 DD DSNAME=SYS1.CTRACE1,VOL=SER=Z6SYS1,UNIT=SYSDA,
// SPACE=(CYL,25),DISP=(NEW,CATLG),DSORG=PS
(Substitute a valid DSN and disk volser as needed on the TRCOUT01 DD card.)
This is discussed in manual "MVS Diagnosis: Tools and Service Aids".
To collect the packet trace information, do the following:
1. Start the external writer by entering the following operator command:
trace ct,wtrstart=ctwtr,wrap
2. Tell the component trace facility to capture packet trace info from the tcp/ip address space:
trace ct,on,comp=systcpda,sub=(tcpip)
r nn,wtr=ctwtr,end
3. Tell tcp/ip to start generating packet trace information:
v tcpip,,pkt,on,full,ip=<ip address> <--full packets to/from <ip address> only
Substitute the driver's remote IP address for <ip address>. In the case of the shim running on z/OS, this address may be "localhost" (127.0.0.l) or some other form of local address.
4. To verify that packet information is being generated, enter the following from TSO:
netstat dev
...
DevName: LCS1 DevType: LCS DevNum: 0E20,
DevStatus: Ready,
LnkName: ETH1 LnkType: ETH LnkStatus: Ready,
...
BSD Routing Parameters:,
...
Packet Trace Setting:,
Protocol: * TrRecCnt: 00000111 PckLength: FULL,
SrcPort: * DestPort: *,
IpAddr: <ip address> SubNet: *,
Multicast Specific:,
Multicast Capability: No,
Link Statistics:,
...
The "trace ct" command is discussed in manual "MVS System Commands".
The "v tcpip" and "netstat" commands are discussed in manual "Communications Server IP System Administrator's Commands".
When you're finished:
1. Tell tcp/ip to stop generating packet trace information:
v tcpip,,pkt,off
2. Stop the component trace writer:
trace ct,on,comp=systcpda,sub=(tcpip)
r nn,wtr=disconnect,end
trace ct,off,comp=systcpda,sub=(tcpip)
trace ct,wtrstop=ctwtr,flush
To actually display the records, you must use IPCS. Sample command to display full information:
CTRACE COMP(SYSTCPDA) FULL DSNAME('SYS1.CTRACE1')
document
| Document Title: | How to troubleshoot the remote loader hanging combined with a broken-pipe message on a MainFrame RACF Computer |
| Document ID: | 10100345 |
| Solution ID: | NOVL105021 |
| Creation Date: | 30Jan2006 |
| Modified Date: | 30Jan2006 |
| Novell Product Class: | DirXML |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.