|
|
|
The following table describes common errors or conditions you can encounter, their probable cause, and the recommended action to take to resolve them:
|
Error Type or Symptom |
Probable Cause |
What to do... |
|---|---|---|
|
NETSTAT or Connections List Errors: |
||
|
General Note: |
Incorrect or incomplete configuration causes most of errors from NETSTAT or List Connection requests. |
Ensure that all steps in the tasks for your environment have been successfully completed. Note: For more information, see the Installation Guide. |
|
IPNS0807 UNIX SHELL OPEN REQUEST HAS FAILED, CALL=0 RC=0 RSN=0000-0000 |
SOLVE SSI software is out of date. |
Ensure that the SOLVE SSI run-time libraries contain the latest release of security and system services. |
|
IPNS0806 UNIX SHELL REQUEST OPEN HAS FAILED DUE TO UNIX interface not available |
SOLVE SSI is not configured to act as the USS interface. |
Update your SOLVE SSI configuration to include the start parameter UNIX=YES. |
|
|
The user ID associated with the SOLVE SSI started task does not have an OMVS segment. |
Set up an OMVS segment in the CA ACF2 for z/OS, CA Top Secret for z/OS, or RACF profile of the user ID associated with the SOLVE SSI started task. Note: For more information, see the Installation Guide. |
|
IPNS0809 UNIX SHELL INITIALIZATION FAILED, CALL=760 RC=129 RSN=053B-006C |
The user ID associated with the SOLVE SSI started task has in its OMVS segment the name of a shell program that could not be invoked. |
Ensure that this user ID has a valid shell program specified in the PROGRAM section of its OMVS segment. Note: For more information, see the Installation Guide. |
|
Cannot change to the HOME directory. |
The user ID associated with the SOLVE SSI started task does not have at least read access to the home directory defined in its OMVS segment. |
Ensure that this user ID has at least read access to the specified home directory. Note: For more information, see the Installation Guide. |
|
User ID not displayed in list connections, or IP address not being displayed in EASINET. |
The default application for Telnet is not performing user ID registration. The following causes are possible: |
|
|
|
|
Set IPCHECK to REGISTER or VERIFY. |
|
Errors Starting Sockets Interface |
||
|
N3B290 WARNING - UNABLE TO OBTAIN TCP/IP HOST NAME, USING 'LOCALHOST' N3B291 WARNING - UNABLE TO OBTAIN TCP/IP HOST ADDRESS USING 127.0.0.1 (LOOPBACK) |
The DNRALCxx and DNRHSTxx members have not been configured as specified. For example, DNRALCxx does not contain an entry for the CA TCPaccess CS for z/OS subsystem name. |
Follow the instructions for setting up DNR in the Installation Guide. |
|
TVG101 TCPAXS INTERFACE INITIALIZATION FAILURE 31 - BAD RET HOSTNAME LEN: 0 N3B220 TCPIP START (TYPE=TCPAXS) FAILED, 7 - TCPAXS MODULE NM053030 INITIALIZATION FAILURE, RC: 8 |
The DNRALCxx member contains an entry for the CA TCPaccess CS for z/OS subsystem name, which translates the name directly to an IP address, not to a host name. |
Follow the instructions for setting up DNR in the Installation Guide. |
|
Name lookup is not working. |
The host that is defined as the Domain Name Server (DNS) is down or incorrectly defined. |
Ping the name server host to verify that it is accessible from the system. IBM TCP/IP: Review the NSINTERADDR parameter specified (up to three occurrences allowable) in the TCPIP.DATA data set. This parameter contains the IP address of a DNS system. CA TCPaccess CS for z/OS: Review the contents of the DNRNSCxx member in the CA TCPaccess CS for z/OS PARM data set. |
|
|
The host’s files are incorrect or out of date. |
IBM TCP/IP: Review the contents of the prefix.HOSTS.LOCAL data set. If the prefix.HOSTS.LOCAL data set has been updated since your product was started and you want to refresh it, go to the SOCKETS parameter group. |
|
Name lookup, ping, or traceroute is slow. |
The Name Server is unreachable, inoperative, or slow. |
CA TCPaccess CS for z/OS: Update the SOCKETS parameter group to specify DNR mode ‘Local’. |
|
IPSNPK09 No resp from &P1 – SNMP may be unauth/unavailable |
The device does not support SNMP, or you are not authorized. |
Define SNMP security. |
|
Mails not being sent for the Email trouble ticket. |
The job name or destination on the trouble ticket interface definition is not running. |
Check the trouble ticket job name. |
|
UNIX SHELL SSI Interface Self-Test Errors: |
||
|
General Note: |
Incorrect or incomplete configuration causes most of errors from the UNIX shell SSI Interface section of the self-test. |
Ensure that all steps in all tasks in this section have been successfully completed. Note: For more information, see the Installation Guide. |
|
IPDI5227 Warning: Unexpected response from NETSTAT, see the log for details. |
Netstat errors indicate various conditions, which can affect your system. |
Look in the activity log for additional error messages (such as messages with a prefix of IPNS or EZA). |
Sometimes problems occur that require more in-depth diagnosis. A running CA NetMaster region may contain information that helps Technical Support determine the cause of a problem; therefore, Technical Support may ask you to provide a dump of a running region.
The latest Activity Log provides a history of events. Keep all logs since the system was started, and send to Technical Support. Also, send the JES system log and the results of $$SYSPRO.
Use IBM Utility TERSE to reduce the sizes of the dumps, activity logs, and other information gathered.
To dump a CA NetMaster region
The SVCDUMP can be found on SYS1.DUMP, or equivalent. The NetMaster JCL parameters can be found in the RUNJCLIN member.
(CSA,LPA,LSQA,PSA,RGN,SQA,SUM,TRT)
DUMP COMM=(Dump of NetMaster) R nn,JOBNAME=jobname, SDATA=(CSA,PSA,RGN,TRT,LPA,SQA,LSQA,SUM),END
Note: The preferred dump DSN should be blocked at LRECL 4160, BLKSIZE 24960.
| Copyright © 2012 CA. All rights reserved. |
|