|
|
|
Reason:
Some data is not displayed because it is obtained from a NetSpy region but the interface to the region is not enabled, or the NetSpy address space is not active.
System Action:
None
User Action:
Use the NETSPYLINKS Customizer Parameter Group to enable your interface to NetSpy.
Reason:
You entered an invalid FILTER command.
System Action:
The command is rejected.
User Action:
Reissue the FILTER command with a valid address space mask as the operand.
The mask can specify ? to match a single character, or * to match one or more characters. For example, FILTER CICS* displays all address spaces whose name starts with CICS.
Reason:
A request to display recent traffic statistics could not be satisfied because the Packet Analyzer has seen no packets to or from address space p1 over stack p2 in the last hour.
System Action:
The action is rejected.
User Action:
If traffic is expected, check the status of the application.
Reason:
No data was found for p1, and the TCP Connection Duration Times display could not be presented. This condition can happen if the SSI has been recently started and no connection information has been gathered for p1. It could also indicate that p1 has not had any connection activity since the SSI started.
System Action:
The command is rejected.
User Action:
Try later when there is data to display.
Reason:
The Packet Analyzer has not yet seen any TCP connections end for the selected object. Currently active connections are not represented in the graph.
System Action:
None.
User Action:
Try later when some TCP connections have ended.
Reason:
A request for TCP application activity has been sent to the Packet Analyzer. The request failed because the Packet Analyzer has seen no TCP connections for the stack using the indicated filter criteria, p1.
System Action:
The request fails.
User Action:
If the Packet Analyzer has been restarted recently, wait a while and reissue this command. If the Packet Analyzer has not been restarted recently, check the status of the indicated stack or address spaces.
If p1 is a stack, check that the stack is correctly configured to generate SMF records for TCP connection start and end. The SMF records are used by the Packet Analyzer to associate packets with an application address space.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are available only when PALEVEL is FULL.
System Action:
The TCP Application Activity list shows no packet statistics.
User Action:
Check why the SSI is not running with PALEVEL=FULL.
You can change the PALEVEL setting using the SSI's PACTL command.
To change the setting, enter the following command from the region:
SSISEND PACTL PALEVEL=FULL
Reason:
Address space port monitoring failed because the resource does not specify port numbers and/or associated stack name.
System Action:
No port monitoring is performed.
User Action:
Update the resource definition, adding port number(s) and stack details.
Reason:
An attempt to perform address space monitoring of P1 failed. P2 shows the error message.
System Action:
No sample is taken for P1.
User Action:
See message P2 for more information.
Reason:
An attempt to display traffic statistics for resource P1 failed. No ports could be identified on stack P1 for this resource.
System Action:
None.
User Action:
Check the status of the resource. If stack P2 is not the correct stack for resource P1, update the resource definition for P1.
Reason:
An attempt to retrieve storage utilization details for attributes ECSAStorage or PrivStorage has failed. IBM's EZBNMIFR API has returned an error condition. P2 is the return code (errno) and P3 is the reason code (errnojr) from EZBNMIFR.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt to retrieve storage utilization details for attributes ECSAStorage or PrivStorage has failed. P2 is the return code and P3 is the feedback from NMIFR.
For return code 12, following are some possible feedback values:
2 Prepare MDO failure
3 Assign MDO failure
4 Connect map failure
5 Subtask abend processing this request
6 Region not authorized
7 API module EZBNMIFR load failed during initialization
8 Interface disabled due to excessive number of abends
System Action:
The request is rejected.
User Action:
This is an internal failure. Contact Technical Support.
Reason:
Address space monitoring has attempted to process attributes ECSAStorage or PrivStorage for TCPaccess stack P1 . These attributes are not supported for TCPaccess stacks.
System Action:
None.
User Action:
Remove these attributes from your stack definition.
Reason:
An attempt to retrieve storage utilization details for attributes ECSAStorage or PrivStorage has failed. The D TCPIP,,STOR command returned an unexpected response or timed out.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt to monitor port traffic failed. Statistics cannot be retrieved from the Packet Analyzer for one of the following reasons:
System Action:
None of the port attributes sourced from the Packet Analyzer are available.
User Action:
Check the status of the SSI region.
If the SSI is active, check why it is not running with the SSI parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
Address space monitoring queried the Packet Analyzer in the SSI and found that it is currently not collecting statistics. Packet statistics are collected only when the SSI is running with PALEVEL=FULL.
System Action:
None of the port attributes sourced from the Packet Analyzer are available.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
An attempt to retrieve listener backlog details for attribute monitoring has failed. IBM's EZBNMIFR API has returned an error condition. P2 is the return code (errno) and P3 is the reason code (errnojr) from EZBNMIFR.
System Action:
The backlog attributes are not monitored.
User Action:
Contact Technical Support.
Reason:
An attempt to retrieve listener port backlog details has failed. P2 is the return code and P3 is the feedback value from NMIFR.
For return code 12, there are the following possible feedback values:
2 indicates that failure occurred while preparing an MDO.
3 indicates that failure occurred while assigning an MDO.
4 indicates that failure occurred while connecting to a map.
5 indicates that a subtask abended while processing this request.
6 indicates that the region is not authorized.
7 indicates that the EZBNMIFR API module failed to load during initialization.
8 indicates that the interface was disabled because of too many abends.
System Action:
The backlog attributes are not monitored.
User Action:
Contact Technical Support.
Reason:
The NSM agent failed during start up processing. A retry is in progress to start the agent.
System Action:
NSM Agent initialization is retried.
User Action:
Check that the Agent Technology framework is active using the Unix System Services 'awservices status' command. Ensure that the 'nmIpAgt' MIB is loaded using the USS command 'agentctrl -m' command. If necessary notify your system administrator.
The $RM UNICENTER customization parameter group can be accessed to control the agent and review startup messages.
Reason:
An attempt was made to start the TCP/IP TNG interface but it was already running.
System Action:
The existing TCP/IP TNG interface continues.
User Action:
None.
Reason:
The TNG agent failed during start up processing.
System Action:
TNG Agent initialization terminates.
User Action:
Check that the TNG Agent Technology framework is active using the Unix System Services 'awservices status' command. Ensure that the 'nmIpAgt' MIB is loaded using the USS command 'agentctrl -m' command. If necessary notify your system administrator.
Reason:
The Netmaster for TCP/IP TNG agent failed during start up processing.
P2 is the agent technologies function that failed with return code P3
System Action:
TNG Agent initialization terminates.
User Action:
Refer to the log for associated failure messages. If necessary report the failure to your system administrator.
Reason:
The NetMaster for TCP/IP TNG Agent has been invoked as instance P23.
System Action:
TNG Agent initialization begins. Message IPAWPK07 is issued when the agent becomes active.
User Action:
None.
Reason:
The CA NetMaster NM for TCP/IP NSM Agent is now running as instance P2.
System Action:
None.
User Action:
The CA NSM Nodeview and Worldview functions may be used to monitor resources supported by the NSM agent.
Reason:
The Netmaster for TCP/IP TNG Agent has terminated.
System Action:
None.
User Action:
None
Reason:
The Netmaster for TCP/IP TNG Agent has been requested to terminate.
System Action:
Agent termination is requested.
User Action:
None.
Reason:
The TNG agent failed to initialize the regular work load check task.
System Action:
TNG Agent initialization terminates.
User Action:
Check that the TNG Agent Technology framework is active using the Unix System Services 'awservices status' command. If necessary notify your product support representative.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed non-keyword parameters. Non-keyword parameters are only supported by the NETSTAT command.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP external interface procedure failed during request processing because a required keyword parameter was not found. The keyword is identified by P2 and the command is identified by P1 .
System Action:
The request is rejected and the procedure terminates. Control is returned to the calling procedure. If the procedure was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because an invalid IP Adress was passed to the procedure.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the IP Address and retry
Reason:
An APPC request to the remote system identified by P1 failed with return code P2 and feedback code P3 .
System Action:
An additional error message may be written to the activity log if RC=16.
User Action:
Contact your System Administrator.
Reason:
The link, stack, or device identified by P1 is not defined to this system. This message may also appear during region startup when the internal work tables are not available or partially initialized.
System Action:
None.
User Action:
Check that P1 is defined to the system or ensure that the name is correct, and retry the operation. If the message was issued during startup, retry the request after the region has completely initialized.
Reason:
You invoked the API procedure with invalid command parameters, which caused a syntax error.
System Action:
The command fails.
User Action:
Correct the parameters and retry the operation.
All parameters except the first must be in the format keyword=value, for example, PING myhost COUNT=5 WAIT=10.
For more information about the format of a specific command, position the cursor over the command and press F1 (Help).
Reason:
The file identified by P1 could not be opened for input as the file is either a partitioned dataset (PDS) with no member name specified or is a VSAM dataset.
System Action:
None
User Action:
Contact your system administrator.
Reason:
No help is available for the unsupported command identified by P1 .
System Action:
None
User Action:
None
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter was omitted from the call to $IPCALL. One of either ADDRESS, HOSTNAME or HOST must be specified.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed because the IP address passed is not a valid IP address. Valid IP address consist of 4 numbers seperated by decimal points each having a range of 0..255.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the IP address and retry.
Reason:
The TCP/IP external interface procedure $IPCALL failed because the Dataset Name identified by P1 is not a valid Dataset Name.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the Dataset Name and retry.
Reason:
An &ASSIGN operation failed because the ASN1 map identified by P1 could not be found.
System Action:
None
User Action:
Contact your System Administrator
Reason:
The user exited the Partitioned Dataset Member List using PF3 and did not select a member from the list. The current function is aborted.
System Action:
None.
User Action:
None.
Reason:
The user exited from viewing the Obeyfile Dataset or Member by using PF12.
System Action:
None.
User Action:
None.
Reason:
An MDO error occurred. The MDO is identified by P1 the map name by P2 the MDO return code by P3 and the feedback code is P4 .
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
The IP Address identified by P1 is not a valid IP Address. A valid IP Address consists of 4 numbers seperated by decimal points ("."), each number being between 0 and 255.
System Action:
None
User Action:
Correct the IP Address and retry the operation.
Reason:
The $IPCALL parameter identified by P1 is not numeric.
System Action:
None
User Action:
Correct the parameter and retry the operation.
Reason:
The $IPCALL parameter identified by P1 is out of the range defined by
P2 and P3 .
System Action:
None
User Action:
Correct the identified parameter and retry the operation.
Reason:
The user identified by P1 is not authorized to use TCP/IP services.
System Action:
None.
User Action:
Contact your security administrator. TCP/IP services authorization is a part of the Network Management authorization.
Reason:
The user identified by P1 is not authorized to use the TCP/IP function identified by P2 .
System Action:
None.
User Action:
Contact your security administrator.
Reason:
The VERBOSE keyword was supplied with an invalid value indicated by P1 The value must be either YES or NO.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
The Link Name identified by P1 is not currently active.
System Action:
None
User Action:
Investigate the cause of the link failure and retry the operation.
Reason:
The Link Name identified by P1 has been removed.
System Action:
None
User Action:
Contact your System Administrator.
Reason:
The dataset type for the dataset identified by P1 is not valid for the function being performed. The dataset must be either a Partitioned dataset with a member name or a sequential dataset.
System Action:
The request is rejected.
User Action:
Correct the Dataset Name and retry.
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter was omitted from the call to $IPCALL. One of either ADDRESS, HOSTNAME or HOST must be specified.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed because an &VARTABLE verb gave an unexpected return code. In the message:
P1 is the VARTABLE name
P2 is the &VARTABLE request type
P3 is the key for the entry
P4 is the return code
System Action:
The request is rejected and the procedure terminates. Control is returned to the procedure which executed $IPFT33L.
User Action:
Contact your system administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because the TCP/IP interface type ( P2 ) for the requested system ( P1 ) is not recognized. The internal processing routine is identified by P3.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
This is an internal error: contact Technical Support.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because the TCP/IP Interface Type (IBM or TCPaccess) cannot be determined. This situation can occur if TCP/IP services have not been initialized.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
TCP/IP services should be initialized using the TCP/IP Administration menu.
Reason:
Wildcard characters were found in P1 . Wildcard characters are not supported by the current function.
System Action:
SYSMSG is set and control returns to the calling procedure.
User Action:
Remove the wildcard characters and retry.
Reason:
The Hostname identified by P1 could not be resolved.
System Action:
None
User Action:
Correct the IP Address and retry the operation.
Reason:
Your SOLVE product does not support the SOLVE TCP/IP function identified by the action ( P1 ) and class ( P2 ).
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because a required keyword parameter was not found. The keyword is identified by P1 and the action is identified by P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing for the NETSTAT command because an illegal NETSTAT parameter was found. The illegal parameter is identified by P1 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
A response from VTAM was not received within 20 seconds when issuing a the VTAM command P1 .
System Action:
Could not complete requested function.
User Action:
Determine why VTAM is not responding to a P1 command and correct problem. Check for the message IPCALL36 in the log which will contain the last message received from VTAM. If no messages were received, this message will not be in the log.
Reason:
This message is written to the log as a result of a VTAM command not completing within 20 seconds. P1 is the text of the last message that was received before the command timed-out.
System Action:
Could not complete requested function.
User Action:
Determine why VTAM is not responding within 20 seconds. Also look_for the message IPCALL35 in the log which identifies the command that_was issued.
Reason:
A VTAM buffer trace for a Logical Unit has been started/stopped.
P1 - The Logical Unit Name
P2 - Trace status, ON or OFF
System Action:
None.
User Action:
None.
Reason:
This message is written to the log as a result of a STRACE START command not completing within 20 seconds. P1 is the text of the last message that was received before the command timed-out.
System Action:
Could not complete requested function.
User Action:
Determine why the SOLVE system is not responding to a STRACE START command and correct problem.
Reason:
A response from the SOLVE system was not received within 20 seconds when issuing an STRACE START command.
System Action:
Could not complete requested function.
User Action:
Determine why the SOLVE system is not responding to an STRACE START command and correct problem. Check message IPCALL38 in the log which will contain the last message received. If no messages were received, this message will not be in the log.
Reason:
An invalid value P1 was specified as a member name/mask.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the member name and retry. Valid member mask characters are:
'*' - match any character
'?' - match one character
Reason:
You attempted to perform a TCPaccess related function on a system that is not configured for managing that TCP/IP stack type.
System Action:
The request is rejected.
User Action:
Make sure you have specified the correct link name, as you may be pointing to a system that is managing a different TCP/IP stack.
Reason:
The requested function is not currently supported by TCPaccess.
System Action:
Proccessing of the function is terminated.
User Action:
None.
Reason:
The CTRACE parameter defaults have been saved in a database. These defaults will be displayed on the Start CTRACE Confirmation panel the next time it is displayed.
System Action:
None.
User Action:
None.
Reason:
The requested function is not supported by the remote region, P1. The remote region is used because it is the managing region for the resource, or has been selected by you specifying a link name.
System Action:
Processing of the function terminates.
User Action:
The remote region is currently linked to this region in Migration Mode. This type of linkage is used during migration to a new release level. Full functionality is provided when the remote region is upgraded to the same level as the current region and linked using normal region synchronization.
Reason:
TCP/IP services has not completed the implementation phase. Commands are not accepted before implementation has completed.
System Action:
Proccessing of the command is terminated.
User Action:
Access the TCP/IP primary menu (Option N.IP). The implementation process will start and you will be prompted for system details.
Reason:
An invalid value P1 was specified as a member name.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the member name and retry.
Reason:
An APPC request failed with return code P1 and feedback code P2 .
System Action:
The transaction is terminated.
User Action:
Contact your System Administrator.
Reason:
A request was received to obtain data from a Cisco channel card, but the channel card definition specifies a remote link name which does not represent an INMC link to another SOLVE system.
System Action:
The request fails.
User Action:
Update the channel card definition to specify a link name which represents an INMC link to another SOLVE system.
Reason:
The IPLOG extract process has been started as a background task running with the authority of the user who requested the extract. Progress messages are written to the log with the prefix IPLO82
System Action:
Extract process submitted to user's background region.
User Action:
Check the log for the progress reports.
Reason:
The option requested is not a valid action when applied to a channel card or a 2216 router.
System Action:
The option is not processed.
User Action:
Either select an option valid for that object or change the object to something other than a Channel Card or 2216 Router.
Reason:
The Network Tracking System (NTS) component of NetMaster for SNA provides session awareness support used for session monitoring. The function requested is only available if the region is configured with NetMaster for SNA.
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
Workload Monitor functions are available only if you are using IBM's eNetwork CS 2.5 or above.
System Action:
Processing of the function is terminated.
User Action:
None.
Reason:
The start of CTRACE failed because the job name P1 has a status of starting. The reason for this status could be that a dataset is in use, causing a dataset wait.
System Action:
None.
User Action:
Determine why the job P1 has a status of starting and rectify problem.
Reason:
A specified connection has terminated.
System Action:
None.
User Action:
Refresh the connection list to view current connections.
Reason:
An action has been attempted against stack P1 but the stack is not active.
System Action:
The action fails.
User Action:
Investigate why the stack is inactive.
Reason:
The requested function is not supported by the remote SOLVE system.
System Action:
Proccessing of the function is terminated.
User Action:
Upgrade the remote system so that it is running at the same level as your local system for maximum functionality or do not specify a value for the User ID, LU name, or Application fields.
Reason:
The option requested is not a valid action when applied to object P2
System Action:
The option is not processed.
User Action:
Either select an option valid for that object or apply the option to a different object.
Reason:
The stack, P1 , is not defined. The system reporting the error is P2 . This message may also appear during region startup when the internal work tables are not available or partially initialized.
System Action:
The request is rejected.
User Action:
Ensure that the stack is defined to the system or that the name is correct. Where available, use prompt lists to obtain the list of currently available stack names. If the message was issued during startup, retry the request after the region has completely initialized.
Reason:
A connection with id P1 was successfully dropped.
System Action:
None.
User Action:
Refresh the connection list to view current connections.
Reason:
An NSLOOKUP issued to extract host details about stack P1 has failed.
System Action:
None
User Action:
Check the status of the stack.
Reason:
This message contains information about a TRENDEX command. The TRENDEX command will submit a background procedure to roll up and extract trend data from IPFILE into a CSV file.
System Action:
None
User Action:
Check the Activity Log to see the progress of the trend data extract and CSV file creation. If there is a lot of data, this process may take a while. In order to create a trend file, you must enable trend data collection via the $IPFILES Customizer parameter group.
Reason:
It was determined that the dataset P2 has been migrated (for example, by DFHSM).
System Action:
Request is rejected.
User Action:
Manually recall dataset before invoking the 'Save Trace Data' option.
Reason:
A request was made to display the performance history data collected for resource P1, but the request has failed because no data is available.
System Action:
None
User Action:
Investigate the following possibilities:
- Monitoring is not active for the resource. To activate monitoring issue 'AM' against the resource or update the resource definition.
- No attributes have been selected for monitoring for this resource.
- Monitoring is active but no data was available at the time of collection.
- The attempts to collect samples from the resource have failed. If this is the case, issue 'L' against the resource to view the resource transient log where any error messages will be seen.
Reason:
A request was made to display data collected for a resource, but the request has failed because no data is available.
P1 is the type of data.
P2 identifies the resource.
System Action:
None.
User Action:
Investigate the following possibilities:
To activate monitoring, enter AM next to the resource from the IP Resource Monitor or update the resource definition.
To view the resource transient log, enter L next to the resource from the IP Resource Monitor.
Reason:
A request to display P1 data for resource P2 was selected, but this data is not currently being collected for this resource.
System Action:
None.
User Action:
Update resource monitoring by entering 'UM' against a resource definition.
Reason:
A command to start or stop a VTAM Buffer trace for LU P1 failed. P1 is unknown to VTAM or is not valid for buffer tracing.
System Action:
None.
User Action:
Buffer tracing cannot be used for this connection.
Reason:
An action routed to a remote region failed. User ID P1 is not known to the remote region P2.
System Action:
The request fails.
User Action:
Contact your systems administrator.
Reason:
The P1 command has failed because it requires an existing SmartTrace definition as a parameter but none was provided.
System Action:
The request is rejected.
User Action:
List the available SmartTrace definitions using the shortcut /TRACES, and reissue the command.
Reason:
You supplied the ADDRTYPE keyword with an invalid value indicated by P1. The ADDRTYPE value represents the IP version, and must be 4, 6, or ANY.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
The protocol parameter is invalid. Valid values are UDP or ICMP.
System Action:
The command fails.
User Action:
Correct the value and reissue the commands.
Reason:
You requested a list of IPv6 connections from a stack or device that does not support IPv6.
System Action:
The request is rejected.
User Action:
Change the criteria, and reissue the request.
Reason:
You requested a list of FTP connections, but this type of list is only available since z/OS V1R10.0.
System Action:
The request is rejected.
User Action:
Select a stack running on a later z/OS version, or select another type of list.
Reason:
The TCP/IP external interface procedure $IPCALL detected an invalid interface name.
System Action:
The request is rejected, and procedure $IPCALL terminates. Control is returned to the NCL procedure that executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
The interface name must be a maximum of 16 characters. Correct the name, and retry the operation.
Reason:
This message indicates the end of returned messages.
System Action:
None
User Action:
None
Reason:
A request encountered an error while trying to satisfy a translator query. An associated error message is also written to the activity log.
p1 identifies the data source.
p2 identifies the package.
p3 identifies the table.
p4 contains a reference for the specific error.
System Action:
The columns for the table that could not be filled in because of the error have null values. An error is written to the activity log, and processing continues.
User Action:
Review the related error message to determine the exact cause of the error, and retry the request.
Reason:
The value of the specified parameter passed is invalid.
System Action:
None.
User Action:
Correct the parameter and retry.
Reason:
A response from the command P1 was not received within an adequate amount of time.
System Action:
Could not complete requested function.
User Action:
Determine why there is no response to the P1 command and correct problem. Check for the message IPCK7603 in the log which will contain the last message received. If no messages were received, this message will not be in the log.
Reason:
This message is written to the log as a result of a command not completing within an adequate amount of time. P1 is the text of the last message that was received before the command timed-out.
System Action:
Could not complete requested function.
User Action:
Determine why the command is timing out. Also look for the message IPCK7602 in the log which identifies the command that was issued.
Reason:
While processing your request, the request and response queues used were congested with unprocessed messages that exceeded the NMIQLIM value (default is 32767).
System Action:
Cannot complete requested function.
User Action:
Investigate the reason for excessive messages being issued.
Reason:
During the processing of your request the VTAM status of the LU P1 was not available. This is most likely due to an internal error. The command that was issued to get the status of the LU was P3 . The INTREAD verb set a feedback code of P2 .
System Action:
Could not complete requested function.
User Action:
Contact your Systems Administrator. Look for the message IPCK7606 in the log.
Reason:
This message contains the last message processed before it encountered the error described in message IPCK7605.
System Action:
None.
User Action:
Contact your Systems Administrator and give them this message.
Reason:
The action P1 failed for LU name P2 . P1 is ACTIVATE or INACTIVATE. Possible reasons for the failure are that the LU may not exist or it may already be in the desired state.
System Action:
A message is logged to the activity log.
User Action:
Check the status of the LU before trying the command again.
Reason:
The Check Telnet LUs commands require at least z/OS V1.4.
System Action:
The command is rejected.
User Action:
None.
Reason:
The LISTMAX value has been reached. The number of records returned is identified by P1 .
System Action:
None.
User Action:
None.
Reason:
The selected STACK resource is not registered internally.
System Action:
The request is rejected.
User Action:
This message may occur transiently following a system image load or when remote stack resources are accessed. Try the command again later.
If the situation persists, there may be a mismatch in the information provided about the stack. Check the stack name and type are correct in the following places:
- The stack resource definition (A.R.R)
- Connection awareness stack definition (A.IP.CS)
- SOCKETS parameter group (/PARMS)
Reason:
The stack or address space selected for the command is inactive.
P1 is the resource class.
P2 is the resource name.
System Action:
The command is rejected.
User Action:
None.
Reason:
The Check Telnet LUs command found no LUs. This probably means the stack or address space is not configured as a Telnet server.
System Action:
The command is rejected.
User Action:
If the command was issued against a stack, the Telnet server may be running in its own address space. Issue the command against the ASMON resource for the Telnet server. (Your site can define ASMON resources of type TNSERVER for such servers.)
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
The TCP/IP procedure $IPCK77L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
An error occurred performing an ASSIGN of an MDO. The MDO is identified by P1 , the Map is identified by P2 , the MDO return code is identified by P3 and the MDO Feedback value is identified by P4 .
System Action:
The procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
A search for problem TELNET LUs but did not find any problems.
System Action:
None.
User Action:
None.
Reason:
You have specified a refresh interval that was not numeric or was not a minimum of 30 minutes or greater than 1440 minutes.
System Action:
Refresh Interval field placed in error.
User Action:
Correct the entry in the Refresh Interval field and retry.
Reason:
The received SMF record is of an unexpected record type, P1 , or structure. Supported SMF record types are 119 and 130.
System Action:
The record is ignored.
User Action:
If the situation persists, contact Technical Support.
Reason:
A telnet connection has started:
P1 is the IP Address (and port number) of the remote host
P2 is the LU name used by the connection
P3 is the SNA Application the connection is in session with
P4 is the logical device number assigned by the TCP/IP stack.
System Action:
None
User Action:
None
Reason:
A Telnet connection has stopped:
P1 is the IP address of the remote host.
P2 is the LU name used by the connection.
P3 is the SNA application that the connection was in session with.
P4 is the number of bytes received on the connection.
P5 is the number of bytes sent on the connection.
P6 is the number of days the connection has been active.
P7 is the time, in the form hh:mm:ss, that the connection was active.
P8 is the user ID associated with the connection, if known.
P9 is the reason for the connection termination, as given in message EZZ6034I, if known.
System Action:
None
User Action:
None
Reason:
A Telnet Client Logon event was received:
P1 is the local IP address and port number.
P2 is the remote IP address and port number.
P3 is the started task qualifier name and P4 is the node name.
System Action:
None
User Action:
None
Reason:
A Telnet Client Logoff event was received:
P1 is the local IP address and port number.
P2 is the remote IP address and port number.
P3 is the started task qualifier name and P4 is the node name.
System Action:
None
User Action:
None
Reason:
The received SMF record is of an unexpected record type, P1 , or structure. Supported SMF record types are 119 and 130.
System Action:
The record is ignored.
User Action:
If the situation persists, contact Technical Support.
Reason:
An FTP client action completed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended
P2 is the user performing the action
P3 is the IP address of the connection
P4 is the name of the dataset affected
P5 is the number of bytes transmitted
P6 is the number of seconds taken by the transaction
P7 is the number of bytes per second transmitted in the transaction.
System Action:
None.
User Action:
None.
Reason:
An FTP client action has completed but the action failed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended
P2 is the user performing the action
P3 is the IP address of the connection
P4 is the last reply code. Refer to the note below.
P5 is the name of the dataset affected
P6 is the number of bytes transmitted
P7 is the number of seconds taken by the transaction.
The last reply code ( P4 ) is the value set in bytes 28-31 of the FTP Client SMF record, as described in the appendices to the OS/390 Communications Server IP Configuration manual. A value of 0 or 2nn represents a successful transmission (and will cause message IPCM2303 to be issued rather than this message). Other values are as set by the TCP/IP stack.
System Action:
None.
User Action:
None.
Reason:
A TCP/IP connection was started:
P1 is the local IP address and port number
P2 is the remote IP address and port number
P3 is the job name.
System Action:
None.
User Action:
None.
Reason:
A TCP/IP connection was terminated:
P1 is the local IP address and port number
P2 is the remote IP address and port number
P3 is the job name
P4 is the number of bytes in and P5 is the number of bytes out
P6 is the user associated with the connection, if known.
System Action:
None.
User Action:
None.
Reason:
A Telnet Client Logon event was received:
P1 is the local IP address and port number
P2 is the remote IP address and port number
P3 is the started task qualifier name and P4 is the node name
System Action:
None.
User Action:
None.
Reason:
A Telnet Client Logoff event was received:
P1 is the local IP address and port number
P2 is the remote IP address and port number
P3 is the started task qualifier name and P4 is the node name
System Action:
None.
User Action:
None.
Reason:
An event receiver for the ( P2 ) event type has been initialized.
System Action:
The event receiver is started in the BSYS region. Additional RMEV25* messages are written to the activity log indicating the ongoing status of the event receiver.
User Action:
None.
Reason:
This message displays an IP Connections trace record. It includes the following information:
P1 -Procedure Name
P2 -Processing Phase
P3 -Time
P4 -Date
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring during IP connections display processing.
Reason:
This message displays an IP Connections trace record. It includes the following information:
P1 - Procedure Name
P2 - Processing Phase
P3 - Function
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring in IP Connections display processing.
Reason:
This message displays an IP Connections trace record. It includes the following information:
P1 - Procedure Name
P2 - Processing Phase
P3 - Parameter Name
P4 - Parameter Value
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occurring in IP Connections display processing, parameter values are invalid, or are not being adhered to.
Reason:
A list of connections has been obtained using the Packet Analyzer; however, packet analysis for the TCP/IP stack (P1) is disabled. Current statistical data, such as byte counts and packet counts, is incomplete.
System Action:
None.
User Action:
Use the SSI's SHOW STACKS command to display the stacks that the Packet Analyzer is aware of, and which have packet analysis enabled.
Use the SSI's STATUS command to display the status of the Packet Analyzer.
You can enter SSI commands from a CA NetMaster region using the SSISEND command, for example:
SSISEND SHOW STACKS
SSISEND STATUS
If the disabled state is unexpected, check the SSI's JES job log for error messages.
Reason:
An attempt to list connections using the Data Space has exceeded the control limit indicated.
System Action:
The list is truncated at the limit. Further records are ignored.
User Action:
Use more restrictive criteria to reduce the size of the list.
Reason:
An attempt to list connections has specified a non-numeric port value of p1 . The equivalent port number is not known.
System Action:
The list is not performed.
User Action:
Specify the numeric port number.
Reason:
An attempt to list connections using the Packet Analyzer has failed as the Packet Analyzer is unavailable.
System Action:
None.
User Action:
Contact your Systems Administrator to determine why the Packet Analyzer is unavailable.
List this region's configuration details (/IPTEST) and investigate any errors.
Retry the operation selecting a Netstat-based option from the TCP/IP : Connections menu /IPCON.
Reason:
An attempt to list connections using the Packet Analyzer has failed. The Packet Analyzer is running in an SSI region that is not at the latest product release level and does not support the P1 criteria option.
System Action:
No connections are returned for this stack.
User Action:
Determine why the Packet Analyzer is not running in an SSI region at the latest product release level. You cannot use criteria P1 until the SSI region is upgraded.
Reason:
You attempted a connection list action for stack P1 but the stack is not active.
System Action:
The action fails.
User Action:
Investigate why the stack is inactive.
Reason:
An attempt to list connections using the Packet Analyzer has failed. This has prevented accessing connections by User ID, LU name, or application name.
System Action:
No connections are returned for this stack.
User Action:
Contact your systems administrator to determine why the Packet Analyzer is unavailable.
List this region's configuration details (/IPTEST) and investigate any errors.
Reason:
An attempt to list connections using the data space has failed. This has prevented access to connection history data.
System Action:
None.
User Action:
Refer to the activity log for the reason that data space access has failed.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
A request to list saved criteria definitions has failed. There are no criteria definitions on file for the specified Connection List type ( P1 ).
System Action:
None.
User Action:
None.
Reason:
The RECALL command was used to recall a criteria definition using a prompt list but no definition was selected.
System Action:
None.
User Action:
None.
Reason:
A request to save the criteria definition ( P1 ) would overwrite an existing definition, but Replace=No was specified.
System Action:
The definition was not overwritten.
User Action:
Do one of the following:
- Specify Replace=Yes and use the File command to replace the record.
- Use the Cancel command.
Reason:
A request to recall the specified criteria definition ( P1 ) has failed because it was not found.
System Action:
None.
User Action:
None.
Reason:
The RECALL command was used to recall a criteria definition but there are no stored criteria.
System Action:
None.
User Action:
Use Store (F11) to define the stored criteria.
Reason:
A request to build a selection list of stacks and servers could not be completed because the TCP/IP sockets interface was terminated or not started.
System Action:
Request is rejected.
User Action:
To start the TCP/IP sockets interface, perform the following steps:
1. Review the SOCKETS Parameter group (/PARM). Verify that all the details are correct and then press PF6 to action the group.
2. If actioning the group fails, verify that the associated stack address space is available and completely initialized. Retry and action the parameter group.
Reason:
The list criteria for this selection had its P2 field cleared because it is no longer valid for the current system environment. This is caused by system changes that occurred since the last time the criteria was used. For example, a TCP/IP address space may have been renamed or
System Action:
User Action:
If required, enter ? in the P2 field to display a selection list of valid stacks and servers or press Enter to use the default stack or
Reason:
You entered an invalid value for IP version. Valid values for this field are 4 and 6.
System Action:
The field is highlighted in error.
User Action:
Correct the IP version value.
Reason:
The IP version specified does not match the version of the local or foreign host address.
System Action:
The fields are highlighted in error.
User Action:
Correct or remove the IP version or the highlighted host address.
Reason:
A prompt list of external Telnet servers was requested, but no matching resources were found. External Telnet servers should be defined as ASMON resources of type TNSERVER.
System Action:
The field is highlighted in error.
User Action:
To ensure prompting is available, check that your resource definitions are correct. Alternatively, clear the ? and enter the name of a Telnet server in the field.
Reason:
A prompt list of valid values for field P1 was displayed; however, you did not select a valid value from the list.
System Action:
Field P1 is highlighted in error.
User Action:
Retry the operation and select a value, or clear field P1.
Reason:
You entered an invalid value in the FTP Connection Type field. The valid values are DATA and CNTL.
System Action:
The field in error is highlighted.
User Action:
Correct the value in the Connection Type field.
Reason:
No entries were returned for display.
System Action:
None.
User Action:
Change the criteria and retry.
Reason:
The attempted action is valid only for IBM and TCPaccess Telnet connections. It is not valid for Telnet connections from channel cards or routers, or for non-Telnet connections.
System Action:
None.
User Action:
None.
Reason:
The attempted action is only valid for display lines that are active connections.
System Action:
None.
User Action:
None.
Reason:
The attempted action is only valid for display lines that are TCPaccess connections.
System Action:
None.
User Action:
None.
Reason:
The drop action is only valid for active TCP connections. The selected entry is either not a connection (for example, a listener port) or has already terminated.
System Action:
None.
User Action:
None.
Reason:
This action is only valid for TN3270 connections where a VTAM LU name is available and TN3270 services are provided by VTAM.
The action is not available for virtual TN3270 sessions, that is, where a TCP/IP application is providing the service instead of VTAM.
System Action:
None.
User Action:
None.
Reason:
This action is only valid for Telnet connections from a channel card.
System Action:
None.
User Action:
None.
Reason:
The attempted action is valid only for IBM stacks. The action may be invalid for IBM Telnet connections for which the local port is not available.
System Action:
None
User Action:
None
Reason:
The List Connections for a Task diagnostic option is not valid if the selected link represents a Cisco Channel Card or IBM 2216 Router. This option is available for links to NetMaster systems only.
System Action:
None.
User Action:
Correct the entry in the Link/Channel Card Name field and retry.
Reason:
An attempt to list connections using the Data Space has exceeded the control limit indicated.
System Action:
The list is truncated at the limit. Further records are ignored.
User Action:
Use more restrictive criteria to reduce the size of the list.
Reason:
You have specified a refresh interval that was not numeric or was not a minimum of 30 seconds.
System Action:
None.
User Action:
Correct the entry in the Refresh Interval field and retry.
Reason:
You attempted to execute a command against a connection on a remote system. This option is available only when viewing connections on a local system.
System Action:
None.
User Action:
None.
Reason:
You attempted to locate a connection on the connections list when the list was not sorted. You must sort the list using the SORT command before you can locate a connection.
System Action:
None.
User Action:
Sort the list using the SORT command and then retry the LOCATE command.
Reason:
The user has attempted to execute a command against a connection that has been dropped.
System Action:
None.
User Action:
Press the refresh key to rebuild the list of connected sessions.
Reason:
User P3 has issued a command to drop the connection to local port P2 from the P1 IP connection.
System Action:
None.
User Action:
None.
Reason:
Userid P3 has issued a command to drop the Telnet connection for LU P2 from the P1 IP connection.
System Action:
None.
User Action:
None.
Reason:
The connection was not found using either the Packet Analyzer or NetStat. The most likely cause is because the connection has ended.
System Action:
The action fails.
User Action:
Refresh your connection list to remove ended connections.
Reason:
The attempted action is valid for IBM and TCPaccess stack connections only. It is not valid for Telnet connections from channel cards or routers.
System Action:
None.
User Action:
None.
Reason:
The requested action is not available for closed connections (history).
System Action:
None.
User Action:
None.
Reason:
The requested action is not available for a Local Port of 0 or a Status of GROUND.
System Action:
None.
User Action:
None.
Reason:
You issued the LOCATE command with invalid operand P1. The connection list is sorted by Foreign Host, so P1 must be an IP address or part thereof.
System Action:
None.
User Action:
Change the locate command to specify a valid or partial IP address, or use the SORT ? command to sort the connection list by a different field.
Reason:
You have specified an invalid operand on the DELTA command. Valid operands are ON and OFF.
System Action:
The command is rejected.
User Action:
Enter the correct command.
Reason:
You specified P1 as the sort field for the list on the SORT command but
P1 is not a valid sort field for the type of connection list.
System Action:
SORT command rejected.
User Action:
Correct the sort field name (which is an operand on the SORT command) and retry.
Reason:
The SORT ? command was used to present a prompt list of connection list sort fields but no sort field was selected.
System Action:
None.
User Action:
Specify a sort field or select a field from the prompt list.
Reason:
The selected stack is not known to the system. It may have been deleted by another user.
System Action:
The request is rejected.
User Action:
Respecify the selection criteria.
Reason:
A request to build a list of connections could not complete because the TCP/IP sockets interface was terminated or never started.
System Action:
Request is rejected.
User Action:
To start the TCP/IP sockets interface, perform the following steps:
1) Review the SOCKETS Parameter group /PARM . Verify that all the details are correct and then press PF6 to action the group.
2) If actioning the group fails, verify that the associated stack address space is available and completely initialized. Retry and action the parameter group.
Reason:
A request to build a list of connections using value P1 for P2 field is no longer valid because the current system environment has changed since the list criteria was specified. For example, a TCP/IP address
System Action:
User Action:
Enter ? in the P2 field to display a selection list of valid stacks and
Reason:
An unexpected error has occurred. This message is written to the acivity log along with message GP1011 that provides additional details.
System Action:
The previous display is ended.
User Action:
Retry the operation. If the problem persists, contact Technical Support.
Reason:
The '?' action was used to display a prompt list of Connection List actions but no action was selected.
System Action:
None.
User Action:
None.
Reason:
A request for connection detail has failed. There is no ( P1 ) detail available for this connection in the MIB.
System Action:
None.
User Action:
None.
Reason:
The connection was not found using either the Packet Analyzer or NetStat. The most likely cause is because the connection has closed and has been purged from connection history.
System Action:
None.
User Action:
None.
Reason:
Packet Analyzer details were not found for this connection. This may be a transient condition. It also occurs if the Packet Analyzer is running with PALEVEL=NOPACKETS.
System Action:
None.
User Action:
Confirm that the SSI is running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are available only when PALEVEL is FULL.
System Action:
No packet statistics are displayed.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
This connection has been active since before the Packet Analyzer was last restarted. The data displayed on this panel represents only the activity since the Packet Analyzer was restarted.
System Action:
None.
User Action:
None.
Reason:
A request to list UDP connections has failed. There are no UDP connections to list for ( P1 ).
System Action:
None.
User Action:
None.
Reason:
The connection was not found using either the Packet Analyzer or NetStat. The most likely cause is the connection has closed and has been purged from connection history.
System Action:
None.
User Action:
None.
Reason:
No connections matched the specified criteria for the stack specified in
P1 .
System Action:
None.
User Action:
None.
Reason:
The IP version specified does not match the version of the local or foreign host address.
System Action:
The execution terminates.
User Action:
Correct or remove the IP version or the host address.
Reason:
The connection is not known to the EZBNMIFR interface. The most likely cause is that the connection has closed.
System Action:
None.
User Action:
None.
Reason:
The web search server process failed to start or terminated abnormally.
System Action:
Web search is terminated.
User Action:
Check the activity log for additional error messages.
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The web search server process encountered an error accessing the NDB.
P1 is the action.
P2 is the NDB ID.
P3 is the return code.
P4 is the error indicator.
P5 is a related message (which may not always be present).
System Action:
Web search is terminated.
User Action:
Check the activity log for additional error messages.
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The web search server could not find any records that match the search criteria specified in the criteria section.
System Action:
None.
User Action:
Change the search criteria or wait a few moments for more records to be added to the database, and then retry the search.
Reason:
The web search server process could not be contacted.
System Action:
Web search is terminated.
User Action:
Check the activity log for additional error messages.
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The web search could not be completed because the handle passed from the web page was not valid.
p1 was the handle passed.
System Action:
Web search is terminated.
User Action:
Check the activity log for additional error messages.
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The search is still processing but the process that waits for the search to complete has timed out. If you still want to wait for the search then click the "Re-Check" button. Some searches that target a large number of records will take longer than others.
System Action:
Web search continues in the background.
User Action:
Click the "Re-Check" button if you still want to wait for the results. Change the search criteria and click "Search" if you want to cancel the pending search and try a new one.
Reason:
An attempt to use the EZBNMIFR API for the indicated stack (P1) has failed. The API requires the procedure (job) step name (P2). The request failed due to one of the following reasons:
System Action:
The request is rejected.
User Action:
Check that the stack is correctly defined to ResourceView. To do this, follow these steps:
This field is the procname.
If this is incorrect, update the resource and retry.
If the resource definition is correct, check if the stack is active. To do this, follow these steps:
The Status Monitor : IP Resources dialog appears.
Reason:
An attempt to retrieve connection details from IBM's EZBNMIFR API has failed. The type of request is shown in P1. P3 is the return code (errno) and P4 is the reason code (errnojr)
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt to retrieve connection details has failed. The type of operation is shown in P1. P2 is the return code and P3 is the feedback code.
Some possible return codes and feedback values are:
|
RC |
FDBK |
Explanation |
|---|---|---|
|
12 |
1 |
NEXT request rejected, no outstanding GET request |
|
12 |
2 |
Prepare MDO failure |
|
12 |
3 |
Assign MDO failure |
|
12 |
4 |
Connect map failure |
|
12 |
5 |
Subtask abend processing this request |
|
12 |
6 |
NetMaster region not authorized |
|
12 |
7 |
API module EZBNMIFR load failed during initialization |
|
12 |
8 |
Interface disabled due to excessive number of abends |
|
12 |
10 |
Region shutdown in progress |
System Action:
The request is rejected.
User Action:
This is an internal failure. Contact CA Technical Support.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack field to display a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
A request was received to perform an action on a Cisco channel card, but during processing it was determined that the specified device is not a valid Cisco channel card device.
System Action:
The action terminates.
User Action:
Correct the IP Address in the channel card definition and retry.
Reason:
The TCP/IP Services Cisco Channel Card TN3270 Server Information utility procedure has determined that the TN3270 Server is not active on the specified device.
System Action:
The action terminates.
User Action:
Determine why TN3270 Server is not active.
Reason:
The requested maximum number of connections ( P1 ) has been reached but more connections satisfy the criteria. The remaining connections are ignored.
System Action:
None.
User Action:
If more connections are required, increase the Max Connections option and retry.
Reason:
An action has been attempted for a TN3270 client connection through a channel card. The action required details about the connection to be passed in an MDO called $IPCONN. This MDO has not been passed or it is not mapped correctly.
System Action:
The action terminates.
User Action:
Contact your System Administrator.
Reason:
An action was attempted for a TN3270 client connection through a channel card. The action required details about the connection to be passed in an MDO called $IPCONN; however, some of the data that should be present in the MDO is not present.
System Action:
The action terminates.
User Action:
Contact your System Administrator.
Reason:
A request was received to action a TN3270 client connection, but the request failed because the specified connection has ended.
System Action:
The action terminates.
User Action:
Refresh the connection list display and check if this is the case.
Reason:
A request was received to perform an action on a Cisco channel card, but during processing it was determined that no channel card is installed in the specified slot number.
System Action:
The action terminates.
User Action:
Correct the slot number in the channel card definition and retry.
Reason:
A request was received to action a specific PU defined to a Cisco channel card, but the PU specified is not known to the TN3270 Server running on the channel card.
System Action:
The action terminates.
User Action:
Refresh the current display and retry.
Reason:
A request was received to display a list of LUs defined for a specific PU defined to TN3270 Server running on a Cisco channel card. During processing, it was determined that no LUs are defined for the PU.
System Action:
The action terminates.
User Action:
None
Reason:
A request was received to retrieve the channel card definition called
P1 , but no such channel card definition exists.
System Action:
None.
User Action:
Check the name of the channel card definition requested. If it is correct, investigate why the definition has been deleted.
Reason:
A request was received to add or update multiple channel card definitions in a single request. This is not allowed.
System Action:
The request is rejected.
User Action:
Request only one update at a time.
Reason:
A request was received to add a channel card definition called P1 , but a channel card definition with that name already exists.
System Action:
The request is rejected.
User Action:
Choose a different channel card name or update the definition that already exists.
Reason:
When a channel card definition is updated, save processing issues a request to change the current monitoring status of the channel card to reflect the current settings. A request to start monitoring activity for channel card P1 failed.
System Action:
None.
User Action:
The message preceding this message indicates the cause of the failure.
Reason:
A request was received to perform an action on a Cisco channel card, but during processing it was determined that the specified device is not a valid Cisco channel card device.
System Action:
The action terminates.
User Action:
Correct the IP Address in the channel card definition and retry.
Reason:
A request was received to perform an action on a Cisco channel card, but during processing it was determined that no channel card is installed in the specified slot number.
System Action:
The action terminates.
User Action:
Correct the slot number in the channel card definition and retry.
Reason:
A request was received to obtain monitor data for channel card P1 , but monitoring is not active for this channel card.
System Action:
The action terminates.
User Action:
None.
Reason:
A request was received to obtain monitor data for channel card P1 , but all attributes requested have a monitoring status of inactive.
System Action:
The action terminates.
User Action:
None.
Reason:
The TN3270 server has started.
System Action:
None.
User Action:
None.
Reason:
A PU has changed state.
P1 is the PUIndex (not displayed)
P2 is the PU Name
P3 is the new state: ACTIVE, INACTIVE, WAITING or STOPPING
P4 is the IP Address of the tn3270 server supported by the PU
P5 is the TCP Port number of the tn3270 server supported by the PU
System Action:
None.
User Action:
None.
Reason:
A PU received an unsupported SNA message.
P1 is the index number of the PU.
P2 contains a fragment of the message which caused the problem.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A BIND was received by an LU for a TN3270 client.
P1 is the name of the PU which contains the LU
P2 is the local address (locaddr) of the LU (not displayed)
P3 is the client's IP Address
P4 is the client's TCP port number
P5 is the name of the LU
P6 is the outbound RU Size specified in the bind
P7 is the inbound RU Size specified in the bind
P8 is the lutype in the bind
System Action:
None.
User Action:
None.
Reason:
An UNBIND was done for an LU used by a TN3270 client.
P1 is the index of the PU. (not displayed)
P2 is the locaddr of the LU. (not displayed)
P3 is the client IP Address.
P4 is the client TCP port number
P5 is the tn3270 server IP Address (not displayed)
P6 is the tn3270 server TCP port number (not displayed)
P7 is the PU Name
P8 is the LU Name
P9 is the unbind type
P10 is the SNA Sense code
System Action:
None.
User Action:
None.
Reason:
An SNA/TN3270E correlator in a client response was not found.
P1 is the index of the PU. (not displayed)
P2 is the locaddr of the LU. (not displayed)
P3 is the client IP Address.
P4 is the client TCP port number.
P5 is the PU Name (not displayed).
P6 is the LU Name (not displayed).
P7 is the next TN3270E sequence number for the server (not displayed).
P8 is the TN3270E sequence number in the client response.
System Action:
None.
User Action:
None.
Reason:
An SNA/TN3270E sequence number on a client request was incorrect.
P1 is the client IP Address.
P2 is the expected TN3270E sequence number.
P3 is the TN3270E sequence number in the client request.
System Action:
None.
User Action:
None.
Reason:
DDDLU is not supported by the host.
P1 is the tn3270 server IP Address (not displayed)
P2 is the tn3270 server TCP port number (not displayed)
System Action:
None.
User Action:
None.
Reason:
An APPN BIND rejection was received.
P1 is the local CPName
P2 is the remote CPName
P3 is the SNA Sense code
System Action:
None.
User Action:
None.
Reason:
The host did not respond within 30 seconds.
P1 is the PU name
P2 is the LOCADDR of the LU (not displayed)
System Action:
None.
User Action:
Check the configuration and the status of the PU on the host.
Reason:
TCPIP write had a transient failure.
P1 is the Telnet CB index
P2 is the TCPIP error number.
System Action:
None.
User Action:
None.
Reason:
An illegal Telnet suboption was provided by a client.
P1 is the client IP Address.
P2 is the client TCP port number.
P3 is the illegal Telnet suboption.
System Action:
None.
User Action:
Check the client software.
Reason:
A pacing error has occurred.
P1 is the index of the PU. (not displayed)
P2 is the locaddr of the LU. (not displayed)
P3 is the client IP Address.
P4 is the client TCP port number.
P5 is the PU Name (not displayed).
P6 is the LU Name (not displayed).
P7 is the next TN3270E sequence number for the server (not displayed).
P8 is the TN3270E sequence number in the client response.
System Action:
None.
User Action:
None.
Reason:
A Telnet client has failed to respond within the negotiation time limit.
P1 is the client IP Address.
P2 is the client TCP port number.
System Action:
None.
User Action:
None.
Reason:
Invalid data was received from a TN3270 client.
P1 is the PU index (not displayed)
P2 is the locaddr of the lu (not displayed)
P3 is the client IP Address.
P4 is the client TCP port number
P5 is the LU Name
System Action:
None.
User Action:
1. Check client. 2. Report problem to Service Engineer with full details.
Reason:
A loop was detected during TN3270E function negotiation.
P1 is the client IP Address.
P2 is the client TCP port number.
P3 is the OR'd TN3270E function
System Action:
None.
User Action:
None.
Reason:
A TCPIP Listen failed.
P1 is the server IP address.
P1 is the server port number.
P3 is the TCPIP error number.
System Action:
None.
User Action:
None.
Reason:
The listen state of the server PU has changed.
P1 is the PU name.
P2 is the previous state.
P3 is the event that caused the state change.
P4 is the new state.
System Action:
None.
User Action:
None.
Reason:
A timer error has occurred.
P1 is the timer opcode.
P2 is the timer interval in seconds.
P3 is the function pointer in code.
P4 is the return address in code.
P5 is the old function pointer in code.
System Action:
None.
User Action:
None.
Reason:
An LU state error has occurred.
P1 is the new LU SNA state.
P2 is the LU SNA state flags.
P3 is the old LU SNA state.
P4 is the LU CB pointer.
System Action:
None.
User Action:
None.
Reason:
Timer stats max.
P1 is the timer expiries.
P2 is the timer non-expiries.
P3 is the timer relocations.
P4 is the timer processing in milliseconds.
System Action:
None.
User Action:
None.
Reason:
A loop was detected in Telnet termtype processing.
P1 is the client IP Address.
P2 is the client TCP port number.
P3 is the number of devtype requests.
System Action:
None.
User Action:
None.
Reason:
A bad bind was received from the host.
P1 is the PU index (not displayed)
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the client TCP port number
P5 is the LU Name
System Action:
None.
User Action:
1. Check VTAM configuration for this LU. 2. Report problem to Service Engineer with full details.
Reason:
A connection from a tn3270e client was rejected.
P1 is the client IP Address
P2 is the client TCP port number
P3 is the connection rejected reason code which can be:
CONN-PARTNER DEVICE-IN- USE - Requested LU already in use
INV-ASSOCIATE - Associate is not supported
INV- DEVICE-NAME - Requested LU name is not supported
INV-DEVICE-TYPE - Requested Terminal model is not supported
TYPE-NAME-ERROR UNKNOWN-ERROR NO PU DEFINED NO PU ACTIVE NO LU AVAILABLE
P4 is is the requested device type
P5 is the requested LU name
P6 is the sub error ID
System Action:
None.
User Action:
Check client and VTAM configuration.
Reason:
The Tn3270 server has no LUs left in generic pool for assignment to incoming client DDDLU requets.
P1 is the tn3270 server IP address
P2 is the tn3270 server TCP port number
P3 is the current number of active PUs
System Action:
None.
User Action:
1. Check DDDLU have been configured in VTAM. 2. Check channel card configuration.
Reason:
Connection accepted from a tn3270 client.
P1 is the PU index (not displayed)
P2 is the LU LOCADDR (not displayed)
P3 is the client IP address
P4 is the client TCP Port number
P5 is the server IP address
P6 is the server TCP Port number
P7 is the 'specific LU flag'
P8 is the telnet server index (not displayed)
P9 is the PU Name (not displayed)
P10 is the LU Name
P11 is tn3270 device type
System Action:
None.
User Action:
None.
Reason:
ACTLU was received from host for a specific LU. This LU will not form part of DDDLU generic pool.
P1 is the PU index (not displayed)
P2 is the LOCADDR of the LU (not displayed)
P3 is the LU Name
P4 is the PU Name
System Action:
None.
User Action:
None.
Reason:
A negative response was sent to the host from an LU.
P1 is the PU index (not displayed)
P2 is the LOCADDR (not displayed)
P3 is the PU name (not displayed)
P4 is the client IP Address
P5 is the client TCP port number
P6 is the LU name
P7 is a fragment of the SNA message The message fragment is a 2 byte length 'l' followed by 'l' bytes of the SNA Message.
System Action:
None.
User Action:
This may not be a problem and is only a debugging message, but if you notice any other problem on this session, please pass this and other relevant information to Service Engineer.
Reason:
A negative response was received from the host by an LU.
P1 is the PU Index (not displayed)
P2 is the LOCADDR of the LU (not displayed)
P3 is the PU Name
P4 is the client IP Address
P5 is the client TCP port
P6 is the LU name
P7 is a fragment of the SNA message
System Action:
None.
User Action:
This may not be a problem and is only a debugging message, but if you notice any other problem on this session, please pass this and other relevant information to Service Engineer.
Reason:
A tn3270 server listen point has changed status.
P1 is the tn3270 server IP address
P2 is the tn3270 server TCP port
P3 is the state of the listener: SCRAP listen point has been destroyed DEAF created, but not yet listening LISTENING listen point is active and listening
System Action:
None.
User Action:
None.
Reason:
Memory shortage on channel card for TN3270 server.
System Action:
None.
User Action:
1. Add more channel card memory. 2. Report to Service Engineer with full details.
Reason:
TN3270 server has stopped.
System Action:
None.
User Action:
None.
Reason:
There was a DLUR/DLUS protocol error.
P1 is the (local) DLUR CPName
P2 is the (remote) DLUS CPName
P3 is the SNA Sence code
System Action:
None.
User Action:
Check configuration of DLUR/DLUS
Reason:
Remote CP is not a DLUS, or is not willing to be DLUS for the local CP of the TN3270 server.
P1 is (local) DLUR CPName of tn3270 server
P2 is (remote) CPName
System Action:
None.
User Action:
1. DLUS name configured in tn3270 server might be incorrect. 2. DLUS might be configured incorrectly in VTAM. 3. Report problem to Service Engineer with full details.
Reason:
Remote DLUS is in a different subnet from the DLUR of the TN3270 server.
P1 is the local DLUR CP NAme
P2 is the remote DLUS CP Name
System Action:
None.
User Action:
1. DLUS name configured in tn3270 server might be incorrect.
2. Try a DLUS in the same subnet as DLUR.
3. Report problem to Service Engineer with full details.
Reason:
A received bind on a CP-CP session is being rejected.
P1 is the local DLUR CPName
P2 is the remote DLUS CPName
P3 is the SNA Sense code.
System Action:
None.
User Action:
1. DLUR configuration in tn3270 server might be incorrect. 2. VTAM DLUS configuration might be incorrect. 3. Report problem to Service Engineer with full details.
Reason:
An XID was rejected on a CP-CP session.
P1 is the local DLUR CPName.
P2 is the remote DLUS CPName.
P3 is the SNA Sense code.
P4 is the adapter name.
System Action:
None.
User Action:
1. XID specified in TN3270 server could be incorrect.
2. VTAM configuration could be incorrect.
3. Report full details of the problem to your technical support representative.
Reason:
A bad frame was received on a CP-CP session.
P1 is the local DLUR CPName
P2 is the remote DLUS CPName
P3 is SNA Sense code
P4 is the TGN (Transmission group Number) which recieved the frame.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
There is a shortage of IPC event buffers.
System Action:
None.
User Action:
Report the problem to the Service Engineer with full details.
Reason:
An XID was rejected.
P1 is the IDBLK/IDNUM value
P2 is the SNA sense code
P3 is the adapter name
System Action:
None.
User Action:
1. XID specified in tn3270 server might be incorrect. 2. VTAM configuration might be incorrect. 3. Report problem to Service Engineer with full details.
Reason:
The host did not respond to a NMVT PSID sent to it by the tn3270 server.
P1 is the puname
P2 is the LOCADDR (not displayed)
P3 is the client IP Address
P4 is the client TCP Port Number.
P5 is the LU Name
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The host did not respond to a Notify Available sent to it by the server.
P1 is the PU Name
P2 is the LOCADDR of the LU
P3 is the Client IP Address
P4 is the Client TCP Port number
P5 is the LU Name
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The host did not send a bind request to the named dependent LU.
p1 is the PU Name
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the client TCP Port Number
P5 is the LU Name
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The host did not send a Start Data Traffic (SDT) request to this dependent LU.
p1 is the PU Name
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the client TCP port number
P5 is the LU Name
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The TN3270 Client did not respond to the Telnet Timing mark that was sent to it by the server to mark a Start Data Traffic (SDT) request from host.
P1 is the PU name
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the Client TCP Port Number
P5 is the LU Name.
System Action:
None.
User Action:
1. Please investigate the TN3270/E client.
2. Please pass the TN3270/E client name and version along with other relevant information to Service Engineer.
Reason:
The TN3270 Client did not respond to the Telnet Timing mark that was sent to it by the server to mark an UNBIND request from the host.
P1 is the PU name
P2 is the LOCADDR of the LU (not displayed)
P3 is the client IP Address
P4 is the Client TCP Port Number
P5 is the LU Name.
System Action:
None.
User Action:
1. Please investigate the TN3270/E client.
2. Please pass the TN3270/E client name and version along with other relevant information to Service Engineer.
Reason:
The host did not respond to a Notify Unavailable sent to it by the server.
P1 is the PU name
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the Client TCP Port Number
P5 is the LU Name.
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The host did not send an ACTLU for this DDDLU request sent to the host.
P1 is the PU name
P2 is the LOCADDR of the LU
P3 is the client IP Address
P4 is the Client TCP Port Number
P5 is the LU Name.
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
The host did not respond to an UNBIND sent to it by tn3270 server.
P1 is the PU name
P2 is the LOCADDR of the LU (not displayed)
P3 is the client IP Address
P4 is the Client TCP Port Number
P5 is the LU Name.
System Action:
None.
User Action:
Please pass this and other relevant information to Service Engineer. Also gather as much information about this PU and LU from VTAM and pass it on.
Reason:
A link has been disconnected by remote.
P1 is the link name.
System Action:
None.
User Action:
None.
Reason:
Link objected to a field in XID control vector 22.
P1 is the link name
P2 is the SNA Sense code
P3 is the offset within the control vector 22 of the unacceptable field
System Action:
None.
User Action:
1. The related PU may not be active at host.
2. VTAM config is not correct. 3. Report problem to Service Engineer with full details.
Reason:
TN3270 server couldn't activate a link after several retries.
P1 is the link name
P2 is the number of unsuccessful retries.
System Action:
None.
User Action:
1. Eventually link should come up. If not, check that PU is activated on host
2. Check the config on the channel card for the PU 3. Check VTAM config.
Reason:
TN3270 server dropped a frame going to host due to buffer shortage.
System Action:
None.
User Action:
1. Check for sufficient memory on the channel card.
2. Report problem to Service Engineer with full details.
Reason:
TN3270 server could not open a local SAP after several retries.
P1 is the local SAP number
P2 is the adapter type
P3 is the adapter number
P4 is the number of unsuccessful retries.
System Action:
None.
User Action:
Check the config on the channel card for the PU.
Reason:
TN3270 server could not open an adapter after several retries.
p1 is the type of the adapter
P2 is the adapter number
P3 is the number of retries.
System Action:
None.
User Action:
Check the config on the channel card for the PU.
Reason:
A link received an XID of invalid length.
P1 is the link name
P2 is the length of the XID received.
System Action:
None.
User Action:
1. Check the config on the channel card for the PU
2. Check VTAM config.
Reason:
A receved LU 6.2 frame was rejected.
P1 is the SNA sense code.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A bad frame was rejected.
P1 is the link name
P2 is the SNA sense code
P3 is the length of the rejected frame
P4 contains a fragment of the rejected message.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A CP bind from the TN3270 server was rejected.
P1 is the SNA Sense code
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
CP-CP Contention winner session was unbound by NN Server for EN represented by DLUR for TN3270 server.
P1 is the UNBIND type
P2 is the SNA sense code
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
CP-CP Contention loser session was unbound by NN Server for EN represented by DLUR for TN3270 server.
P1 is the UNBIND type
P2 is the SNA sense code
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
DLUR is not able to find a route to configured DLUS. It is trying NN server link.
System Action:
None.
User Action:
1. DLUS name configured in Tn3270 server might be incorrect.
2. APPN network may not be fully operational/ not configured correctly.
3. Report problem to Service Engineer with full details.
Reason:
EN used by TN3270 server DLUR lost link to NN Server.
System Action:
The system will attempt to re-establish the link.
User Action:
1. NN might have gone down or connection between EN-NN may have broken.
2. If possible to reach the NN through another link it should be confgd.
3. If another NN is accessible, CP-CP sessions should come up on that.
4. APPN network may not be fully operational/ not configured correctly.
Reason:
A Link has been permanently lost.
System Action:
None.
User Action:
1. NN might have gone down or connection between EN-NN may have broken.
2. If possible to reach the NN through another link it should be confgd.
3. If another NN is accessible, CP-CP sessions should come up on that.
4. APPN network may not be fully operational/ not configured correctly.
Reason:
The DLUR-DLUS session has been lost.
System Action:
None.
User Action:
1. NN might have gone down or connection between EN-NN may have broken.
2. If possible to reach the NN through another link it should be confgd.
3. If another NN is accessible, CP-CP sessions should come up on that.
4. APPN network may not be fully operational/ not configured correctly.
Reason:
The DLUS rejected a bind from the tn3270 server DLUR.
P1 is the SNA sense code.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A contention winner DLUR-DLUS Session was unbound.
P1 is the UNBIND type
P2 is the SNA sense code
System Action:
None.
User Action:
None.
Reason:
A contention loser DLUR-DLUS Session was unbound.
P1 is the UNBIND type
P2 is the SNA sense code
System Action:
None.
User Action:
None.
Reason:
A frame from DLUS for unknown PU was received.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A DLUS protocol error has occurred.
P1 is the SNA sense code.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A bind was rejected from the DLUS.
P1 is the SNA sense code.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
Special Buffer pool in DLUR exhausted.
System Action:
None.
User Action:
Report problem to Service Engineer with full details.
Reason:
A tn3270 client was disconnected.
P1 is the PU index (not displayed)
P2 is the LU LOCADDR (not displayed)
P3 is the telnet server index (not displayed)
P4 is the disconnect reason: Unexpected data Header length too short Unknown header data Function not supported Requested LU unavailable Requested LU not configured TN3270 session timed out Unknown reason TN3270/TN3270E couln't be negotiated SYSREQ followed by data is taken as Logoff PU has been shutdown TCP client shutdown Other disconnect reason
P5 is the client IP Address
P6 is the client TCP port number
P7 is the PU Name (not displayed)
P8 is the LU Name
System Action:
None.
User Action:
None.
Reason:
LU Contention was discovered on the LU-LU session.
P1 is the PU index (not displayed)
P2 is the LOCADDR of the LU.
P3 is the client IP Address
P4 is the client TCP port number
P5 is the PU Name
P6 is the LU Name
P7 is the message fragment
System Action:
None.
User Action:
This is probably not a problem, but if you notice any other problem, please pass this and other relevant information to the Service Engineer. Also, gather as much information about this PU and LU from VTAM and pass it on.
Reason:
An unexpected response was detected on the LU-LU session.
P1 is the PU index (not displayed)
P2 is the LOCADDR of the LU (not displayed)
P3 is the client IP Address
P4 is the client TCP port number
P5 is the PU Name
P6 is the LU Name
P7 is the message fragment
System Action:
None.
User Action:
This is probably not a problem, but if you notice any other problem, please pass this and other relevant information to the Service Engineer. Also, gather as much information about this PU and LU from VTAM and pass it on.
Reason:
An LU-LU session was started for a TN3270/E client.
P1 is the PU index (not displayed)
P2 is the LOCADDR of the LU (not displayed)
P3 is the client IP Address
P4 is the client TCP port number
P5 is the server IP Address
P6 is the server TCP Port Number
P7 is the telnet server index (not displayed)
System Action:
None.
User Action:
None.
Reason:
On channel card P1 SOCKET P2 on IPaddr P3 failed.
System Action:
The operation will be retried every 30 seconds until successful.
User Action:
Check that the IP address for the channel card is correct.
Reason:
Retrieval of log records has been terminated due to P4.
System Action:
LOG record retrieval is terminated.
User Action:
None.
Reason:
A connection to the channel card has been established.
System Action:
None
User Action:
None
Reason:
An attempted add to the vartable for channel card P1 for the transient log failed. The return code ( P2 ) and table name ( P3 ) are shown.
System Action:
LOG record retrieval is terminated.
User Action:
None.
Reason:
A message was retrieved which is unknown to the logger for channel card
P1 .
System Action:
None.
User Action:
None.
Reason:
Field number P2 in message number P3 has not been defined.
System Action:
The original message is issued without substitution being performed. For the first occurrence of each msg/field number combination, the entire CIP log message data is written to the activity log, in dump format, marked 'Message Error'.
User Action:
Contact Technical Support. Include the message detail and CIP log message data.
Reason:
A connection to the channel card has been opened or closed ( P2 ). The socket ID is P3 and the IP address used is P4 .
System Action:
None.
User Action:
None.
Reason:
An attempt by the Log Browse utility to access the log for P1 failed.
System Action:
Log Browse terminates.
User Action:
Ensure the logging is active for the specified channel card.
Reason:
A command entered on the Log Browse panel is not recognized.
System Action:
None.
User Action:
Check the spelling of the command. If necessary use the Help command, or press F1, to view the application help.
Reason:
A / command was entered without any operands.
System Action:
None.
User Action:
Re-enter the / command with a product command as the operand.
Reason:
A command has been processed.
System Action:
None.
User Action:
None.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
A label command has specified an invalid label name. A label must be 1 to 8 characters.
System Action:
None.
User Action:
Enter a label name of 1 to 8 characters.
Reason:
A SCANMAX command has specified an invalid value. The limit must be a number in the range 1 to 9999.
System Action:
None.
User Action:
Correct the limit entered to be a number in the range 1 to 9999.
Reason:
A SCANMAX command has been accepted. P1 is now the limit on the number of log records that will be searched for a Find request.
System Action:
None.
User Action:
None.
Reason:
An ATTR command has been used to activate message level coloring and highlighting.
System Action:
Log messages with color and highlighting will be displayed with those attributes.
User Action:
Use the ATTR command again to reset message level attributes.
Reason:
An ATTR command has been used to deactivate message level coloring and highlighting.
System Action:
Log messages are displayed without color and highlighting.
User Action:
Use the ATTR command again to set message level attributes.
Reason:
A scroll value entered is not supported.
System Action:
None.
User Action:
Correct the scroll amount entered.
Reason:
A request to access a specific time failed because the format of the data does not match one of the following: HH HH.MM HH.MM.SS
System Action:
None.
User Action:
Correct the time entered to match one of the supported formats.
Reason:
A LABEL command has not specified a label name.
System Action:
None.
User Action:
Correct the label command to specify a label name. For example .HERE or LABEL HERE.
Reason:
A FORMAT command has specified an unknown format name.
System Action:
The format is unchanged.
User Action:
Correct the Format command to specify one of NORMAL, SHORT, LONG, or SOURCE.
Reason:
A FIND command has not specified a search argument.
System Action:
None.
User Action:
Correct the Find command to specify a search argument.
Reason:
A LOCATE command has not specified a label name.
System Action:
None.
User Action:
Correct the LOCATE command to specify a label name. For example, LOCATE THERE.
Reason:
A Locate command has specified a label name that is not defined.
System Action:
None.
User Action:
Check that the label name is spelt correctly and matches a defined label.
Reason:
A Label has been defined for the line indicated by the cursor or the line displayed at the top of the screen.
System Action:
None.
User Action:
Use the Locate P1 command to reposition to this line.
Reason:
A Label has been defined for the line indicated by the cursor or the line displayed at the top of the screen. This definition replaces an earlier position for the label.
System Action:
None.
User Action:
Use the Locate P1 command to reposition to this line.
Reason:
An attempt to add to the VARTABLE for the transient log failed.
System Action:
LOG record retrieval is terminated.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter was omitted from the call to $IPCALL. You must specify ADDRESS, HOSTNAME, or HOST.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure that executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
No log data was found for the date specified.
System Action:
None.
User Action:
Specify a date that has log data. For a list of dates that contain log data, enter the DATE command without specifying a date.
Reason:
A delete request for the named log file P3 failed with an unexpected return code of P1 . P2 is the VSAM feedback.
System Action:
If available, the system message from the FILE Verb is logged.
User Action:
See the VSAM Programming guide for an explanation of error codes.
Reason:
A delete request for the named log file P3 was rejected. No records for the request date P1 were found on the file P2 .
System Action:
None.
User Action:
None.
Reason:
This message shows the data and time when the channel card was initialized.
System Action:
None.
User Action:
None.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
A request to delete log data has specified the current day. This is not supported.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the named log file failed.
System Action:
None.
User Action:
Determine why the channel card log is unavailable. Possible reasons include:
1. The channel card definition does not specify that TN3270 logging is active.
Review the channel card definition details (issue UM command from the IP resource monitor). Check the value for the following field: TN3270 logging active This will have a value of Yes (active) or No (not active).
2. If TN3270 logging is (defined as) active, check the Activity Log for error messages. Locate the following initialization message: IPICAL07 STARTING TO INITIALIZE Miscellaneous Parameters Any errors will be reported after that message, and most likely before: IPICAL08 COMPLETED INITIALIZE OF Miscellaneous Parameters
Correct and retry.
Reason:
A request to process log resources requires the System Support authority, which the current user region does not have.
System Action:
The request is rejected.
User Action:
Contact your System Administrator. System Support authority may be granted through the update user function of UAMS maintenance.
Reason:
A request to access Log functions has failed because a required operand is not specified.
System Action:
Request is terminated.
User Action:
Correct the request to specify the required operand.
Reason:
The value P1 is not a valid value for the field identified by the field label P2 .
System Action:
The user cannot proceed until a valid value is entered.
User Action:
Enter a valid value before proceeding.
Reason:
The value P1 has been located in the Log file. The log record number for the day is P2 . The data was found in the field at offset P3 .
System Action:
None.
User Action:
None.
Reason:
A Log search has failed to locate the requested search argument. P1 lines were read in the time range indicated by P2 to P3 .
System Action:
None.
User Action:
If necessary retry the Find operation.
Reason:
A Log search has failed to locate the requested search argument. The top of data was reached for the current day.
System Action:
None.
User Action:
If necessary, retry the Find operation.
Reason:
A Log search has failed to locate the requested search argument. The bottom of data was reached for the current day.
System Action:
None.
User Action:
If necessary, retry the Find operation.
Reason:
A parsing error occurred processing the parameters in the procedure P1 .
System Action:
The SETVARS system message is logged.
User Action:
See the log and report the error to your product support representative.
Reason:
The keyword parameter P1 was omitted or specified incorrectly.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The userid P1 is not authorized to enter EXEC or CMD in the COMMAND and SELECT OPTION input fields on panels; therefore, the execution of commands is not allowed.
System Action:
The command is rejected.
User Action:
Contact your system administrator if the function is required.
Reason:
The connection to the channel card P1 is not currently active.
System Action:
None.
User Action:
This is informational and does not affect the ability to browse the log.
Reason:
Log records are not being retrieved because the channel card definition has logging turned off.
System Action:
None.
User Action:
Update the channel card definition if desired.
Reason:
No log data was found for the CIP specified.
System Action:
None
User Action:
Ensure that logging is enabled for the CIP and that it can be contacted.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP20L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP20L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places: * On the selected LU or, * On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP21L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP21L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to perform a minitrace on the selected LU but the LU has never been used and therefore has no data pertaining to a minitrace.
System Action:
Option not processed.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP22L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP22L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
A selection was made against a Channel Card application for which no further information is available.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP23L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP23L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP24L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP24L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP25L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP25L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP26L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP26L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP27L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCP27L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
You specified P1 as the sort field for the list on the SORT command but
P1 is not a valid sort field.
System Action:
SORT command rejected.
User Action:
Correct the sort field name (which is an operand on the SORT command) and retry. Use the SORT ? command to display a list of valid SORT field names.
Reason:
A 'D NET,CSM' or 'D NET,CSM,OWNERID=ALL' command was issued, but the response received was not as expected. P1 is the expected VTAM message ID and P2 is the message received.
System Action:
The CSM data sample is not taken.
User Action:
Contact your system administrator.
Reason:
A P1 command was issued, but the expected response was not received within two minutes.
System Action:
The CSM data sample is not taken.
User Action:
Contact your system administrator.
Reason:
A request to display Usage details for Communications Storage Manager failed because no information was available at the time.
System Action:
None.
User Action:
Retry the operation.
Reason:
The keyword parameter P1 was either not specified or an invalid value was specified. P2 is the invalid value.
System Action:
Request is rejected.
User Action:
Correct the call parameters and retry.
Reason:
No data was found for display in the diagram.
System Action:
The Diagram Display call is terminated.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the Diagram Handler.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The selected option is invalid.
System Action:
The cursor is placed in the field in error which is highlighted.
User Action:
Select the correct option and retry. To display a list of valid actions, put a '?' on the selected entry.
Reason:
The service procedure P1 passed an invalid value for a variable required for generating a diagram. The service procedure's name is P1 and the variable incorrectly set is P2 . P3 is the invalid value that was set.
System Action:
Processing is terminated.
User Action:
Correct the variable assignments in the service procedure P1 and retry the request.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected actions are correct before they are carried out.
System Action:
None.
User Action:
Press the ENTER key to execute the highlighted selections, or press the CANCEL function key to cancel the requested actions.
Reason:
This is an informational message indicating that a print request has successfully been sent to the requested printer. The print request number is P1 and the printer is P2 .
System Action:
None.
User Action:
None.
Reason:
The search string P1 was not found.
System Action:
None.
User Action:
None.
Reason:
A find command was issued and no character string was specified as the find argument and no previous find has been issued. The find command can be specified without a character string, but only if a previous find has been specified with a character string.
System Action:
The command is rejected.
User Action:
Re-enter the command specifying a valid character string.
Reason:
The hierarchical depth of the diagram to be constructed exceeds the maximum allowed. The maximum is 245.
System Action:
Processing terminates.
User Action:
None.
Reason:
Configuration details for the P1 region are being collected.
P2 P3 is the type of TCP/IP stack this region is using.
System Action:
None.
User Action:
None.
Reason:
The indicated service(s) are provided by the SOLVE SSI interface. The service(s) ( P1 ) include:
These services can be provided by:
In the message, P2 indicates whether a local or remote SSI is providing the indicated service.
System Action:
None.
User Action:
None.
Reason:
This message provides the error text or other additional details for the previous message.
System Action:
None.
User Action:
Refer to the description for the message that preceeded this message.
Reason:
Self Test attempted to issue a modify command against the active job, but was unable to do so. Target job can be TCPaccess, DataSpace, or other application. Additional reason information is written to the Activity Log.
System Action:
None
User Action:
Investigate any additional messages on the Activity Log.
If the application is TCPaccess: Ensure that the TCPaccess job is running, and that the TCPaccess jobname and SSID are correctly specified in the TCP/IP administration panels. Issue SYSCMD F <jobname>,D IFS from OCS and report the results.
If the application is DataSpace: Ensure that the Data Space Manager is running. Issue SYSCMD F <jobname>,DISPLAY from OCS and report the results.
Reason:
An attempt to issue a MODIFY command against job P1 resulted in system message 'IEE341I <jobname> NOT ACTIVE'.
P2 - stepname is provided for TCPaccess only.
System Action:
None
User Action:
Start the required application. Do a SYSCMD D A,L command to verify that it was started.
For TCPaccess: Issue a SYSCMD F <jobname>,D IFS and check the results. Ensure that you have correctly specified the TCPaccess jobname and SSID in the TCP/IP administration panels. If the TCPaccess job was started with a stepname specified that is different from the jobname of TCPaccess, then that stepname should be specified in the TCPaccess Job Name field.
For DataSpace: Issue a SYSCMD F <jobname>,DISPLAY and check the results.
Reason:
A command issued internally by the Self Test procedure has failed. The exact command is displayed in the message, and specific reason text as follows should appear on the Activity Log.
Command timed out
A response to the command was not received within a specified time.
SYSCMD interface unavailable
MVS system commands cannot be issued; this may indicate command interface congestion.
Unexpected command response
NetMaster received an unexpected response to the command.
Results unavailable
NetMaster could not correctly interpret the command results.
System Action:
Further testing in this class is abandoned. Results from testing in this class may be incomplete or inconclusive.
User Action:
Command timed out
Ensure that your region is responding to commands and that response times generally are not excessive. If so, re-run the Self Test.
SYSCMD interface unavailable
Enter an OCS command such as: SYSCMD D A,L and ensure you receive message N86510 Command passed to operating system followed by the command results. If not, contact your product administrator to investigate any error messages received. Once SYSCMD commands can be successfully processed, re-run Self Test.
The System Command Interface must be enabled using CONSOLES and OPSIDS in Customizer.
Your user ID definition must also include the System Command authority.
System Command authority requires the following:
1. UAMS : Access Authorities
Operations Management ........ Y (Y/N)
2. UAMS : AOM MVS Details
Console Authority ............ C (I, C, M, P - SYSCMD console )
If Console Authority = 'C'
MVS System Commands .......... Y (Y/N)
Unexpected command response
Results unavailable
Issue the failing command yourself, from OCS.
Investigate any incorrect or unexpected responses.
If the responses are normal for that command, report the problem to your product administrator.
Reason:
The TCP/IP socket interface configuration is being checked, including:
System Action:
None.
User Action:
Errors in the socket interface will result in major loss of function.
Review the region setup information in the product Installation Guide.
Many region socket-related parameters are set in the $NM SOCKETS Customizer parameter group (/PARMS).
Reason:
The current status of the TCP/IP interface between this region and the host system is P1.
It must be ACTIVE before NetMaster NM for TCP/IP can function correctly.
System Action:
None.
User Action:
If the status is STARTING, rerun the command in a few moments, after the interface has started.
If the status is INACTIVE or STOPPING, go to the $NM SOCKETS Customizer parameter group (/PARMS).
Look in the initialization log for this group for any error messages.
Action the SOCKETS group, and see if any errors recur.
Reason:
This message contains general information about the configuration and setup of this region.
System Action:
None.
User Action:
None.
Reason:
No port number has been specified for this region.
A region uses its port number to listen for connection requests. If a port number is not specified, this region cannot accept connections from other regions, and INMC over TCP/IP cannot be used.
System Action:
None.
User Action:
If this region needs to participate in IP connection activity, specify a port number, using the $NM SOCKETS Customizer parameter group (/PARMS).
Action this group, then check its initialization log for messages.
If a port number has been specified, it may already be in use by another task. Check the activity log for error messages relating to the port number (for example, N3AE01 37 - EADDRINUSE - ADDRESS ALREADY IN USE).
Use connection lists (/IPCON) to see who is currently using the port.
Reason:
A SHOW TCPIP command was issued, which either timed out or returned errors. This may not indicate problems with the socket interface, but should be investigated as a precaution.
System Action:
None.
User Action:
Issue the SHOW TCPIP command from OCS, and investigate any error responses (place cursor on a message, then press F1).
Look for errors in the Customizer initialization log for the $NM SOCKETS Customizer parameter group (/PARMS).
Ensure the Communications Server stack address space is active.
Look for TCP/IP or socket related errors in the activity log, including at the time of region startup.
Reason:
Unexpected response was received on GET of SNMP System Description.
System Action:
None.
User Action:
Errors in the SNMP interface will result in loss of data to certain functions.
Review the SNMP response, which was written to the activity log. Review the region setup information in the product Installation Guide.
Reason:
The Netspy interface is being checked.
System Action:
None.
User Action:
None.
Reason:
This message contains general information on the Netspy Interface. Information shown: CONN-NAME APPL STATUS PEND-STATUS ACT-DATE ACT-TIME
System Action:
None.
User Action:
None.
Reason:
This is an informational message specifying the dataset name that was derived for the P1 dataset. The actual dataset name is P2. The dataset is correctly defined and is accessible.
System Action:
None.
User Action:
None.
Reason:
Self Test failed to retrieve information about the dataset. Information written to the Activity Log includes the full DSN and any error codes returned. The dataset involved may be migrated.
System Action:
None.
User Action:
Check that the dataset name shown on the Activity Log is the correct one. If is is not, correct it. If it is, check the explanation of any additional messages. One possible cause of this message is a migrated dataset. For performance reasons, Self Test does not recall migrated datasets.
Reason:
The data set P1 does not have the attributes required by TCP/IP Services. The actual data set name, and the attribute in error, and its required and actual values, are written to the Activity Log.
System Action:
None.
User Action:
Ensure that the IPFILES parameter group in Customizer specifies the correct data set names. Check the attributes and reallocate the files if necessary.
Reason:
This message describes a data set attribute in error. Both the required and actual values are displayed.
System Action:
None.
User Action:
Ensure that the IPFILES parameter group in Customizer specifies the correct data set names. Check the attributes and reallocate the files if necessary.
Reason:
This message indicates the status of the CA TCPaccess Communications Server NETSTAT subsystem named $IPNETAX. If the status is not ACTIVE, possible reasons may be as follows:
System Action:
None.
User Action:
For more information, enter these commands from OCS:
SH SUBSYS=$IPNETAX
NETSTAT HELP
Reason:
The TCPaccess Sockets Interface panel specifies P3 as the SSID value. However, the currently active TCPaccess job P1 is using SSID P2.
System Action:
None.
User Action:
Change either the TCPaccess jobname or subsystem ID in the TCP/IP Administration panels so that both refer to the same TCPaccess system.
Reason:
The configuration for TCP/IP stack IP connection events is being checked, including:
System Action:
None.
User Action:
None.
Reason:
NetMaster NM for TCP/IP requires a connection to a SOLVE Subsystem Interface (SSI) started task to function correctly.
The SSID parameter is specified in the $NM SSI Customizer parameter group ( /PARMS ).
The SSID is not correctly defined, or the SSI cannot be connected for one of the following reasons ( P1 ):
System Action:
None.
Selftest UNIX System Services SSI Interface tests are omitted because these will always fail with no connected SSI.
User Action:
no SSID specified
The SSID is a one- to four-character value that matches the SSID parameter of the SOLVESSI started task. To connect to the started task, you must specify the same SSID in this region.
To specify the SSID:
1. Add the following JCL initialization statement to the RUNSYSIN member for this region:
PPREF='SSID=xxxx' (xxxx = the SSID value)
2. Update the SSI parameter group in Customizer to specify the SSID value and action the group.
SSID ssid matches AOM SSID
Ensure that the SOLVE SSI SSID and the AOM SSID are different. The two SSIDs are specified in the following Customizer parameter groups:
Update the appropriate parameter group to specify the correct value and action the group.
SSID ssid is not connected
Ensure that the SOLVESSI started task is active. The SSID specified in this region is shown (ssid).
Check that the value matches the SSID= parameter for the SOLVESSI started task. To change the SSID value in this region, update the SSI parameter group in Customizer and action the group.
Reason:
Many functions require a connection to a SOLVE Subsystem Interface (SSI) started task in order to receive external events. Furthermore, the SSI must be configured with the EndPoint Services (EPS) Simple Event Service.
This error usually occurs when you have specified the wrong SSID value. This region is connected to a SOLVE SSI. However, neither that SSI started task nor any interconnected SSI task is configured with the EPS Simple Event Service.
System Action:
None.
User Action:
Ensure that one of the SSI started tasks in the LPAR provides the Simple Event Service. To provide the service, an SSI started task must include the following parameter:
XEVNT=YES
The following parameters can also be included, but must not be set to any other value than as shown:
XMS=YES XAPI=YES
Note: If you need to change the SSI started task parameters, you must restart that started task. You can have multiple SSI started tasks but only one of these can provide this service.
To determine the facilities provided by the SSI that this region is connected to, issue the following command in OCS or Command Entry:
SSI STATUS
To determine the facilities provided by any SSI started task, you must use the SYSCMD facility to send a message to that started task, for example:
F taskname,SSI STATUS (taskname is the SSI started task name)
If the SSI provides the Simple Event Service, the output from the SSI STATUS command includes the following message:
NY8001 SIMPLE EVENT SERVICE ACTIVE, NAME=$SYS.SIMPLE.EVENT.sysn (sysn is the system name for the z/OS LPAR)
If you have connected the region to the wrong SSI started task, you need to change the SSID that is specified in the region.
To change the SSID for the region do one (or both) of the following:
To change the SSID value in this region you must first stop the SSI.
To stop the SSI, issue the following command:
SYSPARM SSID=NO
You can then specify the new value using the following command:
SYSPARM SSID=xxxx (xxxx = the SSID value)
Reason:
This message lists which stack workload events, if any, are written to the Activity Log and saved in the IP Event History dataset.
System Action:
None.
User Action:
IP Events are written to the Activity Log by specifying YES against the following fields on the IPEVENT Customizer parameter group:
- Log FTP Events?
- Log Telnet Events?
- Log Connection Events?
It is not a requirement by any other part of the NetMaster product to have these events written to the activity log and if you anticipate large volumes of events, you may prefer not to do so.
IP Events are stored in the IP Event History dataset IPLOG by specifying YES against the following fields on the IPEVENT Customizer parameter group:
- Save FTP Events?
- Save Telnet Events?
- Save Connection Events?
If you want to list, search or examine the details of individual IP events using the /IPHIST option, you must save the corresponding events. Events are only retained for a limited time period. You control this with the IPFILES Customizer parameter group.
With some mainframe IP stacks, event records can also be written to your SMF datasets. This is independent of any NetMaster processing of these events.
Reason:
The event receiver for the P2 type and class P1 of events using a receiver ID of P3 has a status of P4 . Status is one of the following:
ACTIVE - The receiver is active and able to receive events.
RETRYING - Define failed and is being retried. The activity Log contains messages (IPCM2509, IPCM2510) showing the reason for the define failing when it was last attempted.
INITIALIZING - The receiver process is being initialized. Retry in a short while to see the current status.
The relationship between the event receiver types, system receiver IDs, and SMF event types is as follows:
SMF Event Type Receiver ID( P3 ) Receiver Type( P2 )
------------------------------- -------------- --- -------------------
FTP Server and FTP Client $IPEVENT FTP
Telnet Server and Telnet Client $IPEVENT TELNET
Connection Initialization and $IPEVENT IPCONN
Connection Termination
------------------------------- ----------------- -------------------
System event receivers are controlled by using the TCP/IP Services Logging and Data Collection Administration panel.
System Action:
None
User Action:
None
Reason:
Controls for APPC multisystem support are being checked, including:
System Action:
None.
User Action:
None.
Reason:
This is an informational message specifying link definitions configuration status.
System Action:
None.
User Action:
None.
Reason:
When APPC links are defined, a specific MODE called P1 which has certain attributes required for multi-system support is used. This message indicates either that this MODE is not defined or that it has incorrect attributes.
For incorrect attributes, the exact details, including the required and actual attribute values, are written to the SOLVE Log.
SOLVE always defines the mode with the correct attributes. Incorrect attributes may be a result of a subsequent REPLINK command.
System Action:
None.
User Action:
Check the values specified on the Advanced Parameters Administration panel. Use the REPLINK command to correct the attributes.
Reason:
When APPC links are defined, a specific OPSET called P1 is used. The OPSET P2 must have a specific MODE specified as a valid mode for the OPSET and requires specific values for other OPSET attributes.
This message indicates that the OPSET is either undefined, or has invalid attributes. Invalid attribute details, including the required and actual attribute values, are written to the Activity Log.
System Action:
None.
User Action:
Check the values on the Advanced Parameters Administration panel. Use the REPOPSET command to correct the parameters.
Reason:
When APPC links are defined, a specific DEFLINK is used which must include the LU mask P1 and specific attribute values. This message indicates either that a DEFLINK for this mask is not defined or is defined but with incorrect attributes.
Details about incorrect attributes, including the required and actual attribute values, are written to the Activity Log.
The correct attribute values are always used. Incorrect values may be the result of a subsequent REPLINK command.
System Action:
None.
User Action:
Check the values on the Advanced Parameters Administration Panel. Use the REPLINK command to correct the attributes.
Reason:
You have specified a non-generic 'Automatically Defined LU Mask' in the Administration (Advanced Parameters) panel. APPC links will only be dynamically defined to this single, specific LU name.
System Action:
APPC link requests for any LU names other that this one will fail.
User Action:
If you want to allow APPC links to be defined to more than one LU, modify the LU mask to include a wildcard character.
Reason:
This message contains information on Links to synchronised regions. Status Mode MSGID MS Level
System Action:
None.
User Action:
None.
Reason:
A z/OS UNIX environment has been opened. A sample SHELL command has been processed. 'STDERR' output has been received in response to the UNIX command. This output has been written to the activity log.
System Action:
None.
User Action:
Examine the STDERR output and any subsequent error messages. STDERR output is sometimes the result of shell setup problems and may not always affect NetMaster processing.
For NetMaster to be able to access the z/OS UNIX environment, the RACF/ACF2 OMVS segment for the user ID associated with the NetMaster SSI started task must have been correctly set up. The NetMaster SSI performs all z/OS UNIX functions on behalf of this NetMaster region. If this OMVS segment is not correct, error conditions can occur.
If you receive this message, and either the Self Test UNIX Test fails, or some NetMaster TCP/IP functions do not appear to work correctly, investigate the specific UNIX shell error messages that appear on your NetMaster Activity log. These should be documented in the appropriate z/OS UNIX manuals.
Reason:
The status of the IPLOG NDB is indicated by P1 .
System Action:
None
User Action:
If the NDB is in a status other than ACTIVE, check the system log to determine the cause.
Reason:
This message indicates the next scheduled time that:
- Expired data records will be deleted from the IPLOG Event History File
- If you have chosen to produce the IPTREND CSV file, the IPFILE file will be input to the Trend Data Rollup process to aggregate the data and produce the IPTREND file.
Related parameters are all specified in the IPFILES parameter group.
To request an extract of event details from the IPLOG Event History file to a sequential file, use the EX option from /IPHIST.
To perform an immediate Trend Rollup to IPTREND, use the OCS command TRENDEX.
System Action:
None
User Action:
None
Reason:
Indicates whether or not the Reporting Listener task ($IPLO81Z) or the Trend Event Listener task ($IPTD21W) is active.
The Reporting Listener task is required for the logging of events to the Activity Log and to the IPLOG file.
The Trend Event Listener task is required for the accumulation of summary data into the IPFILE and the production of the IPTREND file. This will only be active if the IPFILES Customizer Parameter Group (/PARMS) has the field 'Produce IPTREND file?' set to YES.
System Action:
None.
User Action:
If you require Event History logging and $IPLO81Z is not running check the IPFILES Customizer Parameter Group (/PARMS). There needs to be an allocated dataset, keep days and delete time.
If you require expired event history to be written to the IPTREND data set and $IPTD21W is not running also check the IPFILES Customizer Parameter Group (/PARMS) and the Activity Log. Check that the IPFILES Customizer Parameter Group (/PARMS) has the field 'Produce IPTREND file?' set to YES.
Reason:
TCP/IP events of type P1 are being written to the IPLOG Event History file.
System Action:
None
User Action:
None
Reason:
The WebCenter HTTP Interface is being checked, including:
System Action:
None.
User Action:
None.
Reason:
The port for WebCenter access is in a condition indicated by P2 :
Not configured indicates that no port number has been specified.
Not active indicates that a port number was specified but the socket is not open (this generally indicates that TCP/IP may not have been started).
System Action:
None.
User Action:
If the WebCenter interface is required, update the WEBCENTER parameter group (/PARMS) to define a port number.
If the WebCenter interface is not active, investigate previous messages for errors with the socket or TCP/IP management interface.
Reason:
This message contains details of the WebCenter HTTP port and URL.
System Action:
None.
User Action:
The specified URL may now be used to access NetMaster WebCenter.
Reason:
This message contains extra details about the WebCenter configuration.
System Action:
None.
User Action:
None.
Reason:
Region authority and processing environment are being checked, including:
System Action:
None.
User Action:
None.
Reason:
Background system (BSYS) ID is not defined. NetMaster for TCP/IP requires the BSYS ID to be defined to your security system.
System Action:
None
User Action:
Define the background system ID to UAMS or external security system.
Reason:
An error occurred when obtaining user ID details. Complete text of error message is in log.
System Action:
None
User Action:
Refer to log for message ID indicated and perform appropriate action to resolve.
Reason:
Authorization for the indicated BSYS user ID is defined as 0 (none) for NetMaster for TCP/IP.
System Action:
None
User Action:
Define the indicated BSYS user to have authority of at least 1 (browse).
Reason:
Authorization for the indicated BSYS user ID is defined as 1 (browse) for NetMaster for TCP/IP.
System Action:
None
User Action:
Consider allowing the indicated BSYS user ID to have authority level 2 (update) for NetMaster for TCP/IP.
Reason:
The background system user P1 has the authority to perform the regularly scheduled tasks required for NetMaster NM for TCP/IP.
System Action:
None.
User Action:
None.
Reason:
Host override P1 cannot be confirmed as valid. Either the overriding hostname is not recognised by NSLOOKUP or the IP address is not associated with the stack used by this region, as specified in the SOCKETS Parameter Group (/PARMS).
System Action:
None.
User Action:
If the override value is invalid, correct it in the WEBCENTER parameter group (/PARMS). The value may be valid; this message can be caused by a domain name server problem.
Reason:
The UNIX System Services SSI Interface is being checked, including:
System Action:
None.
User Action:
Errors in the USS SSI Interface can result in loss of data to some functions.
Review the region setup information in the product Installation Guide, particularly relating to the OMVS segment required by the user ID of this region's MVS started task.
Reason:
In order to communicate with IBM's UNIX System Services (USS), the TCP/IP Services NETSTAT and ONETSTAT functions require services from a SOLVE Subsystem Interface (SSI) started task that is configured with the EndPoint Services (EPS) UNIX SHELL Service.
The SSI configured with the USS interface may be either:
This error usually occurs when you have specified the wrong SSID value. This region is connected to a SOLVE SSI. However, neither that SSI started task nor any interconnected SSI task is configured with the EPS UNIX SHELL Service.
System Action:
None.
User Action:
Ensure that one of the SSI started tasks in the LPAR provides the UNIX SHELL Service. To provide the service, an SSI started task must include the following parameter:
UNIX=YES
The following parameters can also be included, but must not be set to any other value than as shown:
XMS=YES XAPI=YES
Note: If you need to change the SSI started task parameters, you must restart that started task. You can have multiple SSI started tasks but only one of these can provide this service.
To determine the facilities provided by the SSI that this region is connected to, issue the following command in OCS or Command Entry:
SSI STATUS
To determine the facilities provided by any SSI started task, you must use the SYSCMD facility to send a message to that started task, for example:
F taskname,SSI STATUS (taskname is the SSI started task name)
If the SSI provides the UNIX SHELL Service, the output from the SSI STATUS command includes the following message:
NSC001 UNIX SHELL INTERFACE ACTIVE, NAME=$SYS.UNIX.SHELL.sysn
(sysn is the system name for the z/OS LPAR)
If you have connected this region to the wrong SSI started task, you need to change the SSID that is specified in this region.
To change the SSID, do one (or both) of the following:
To change the SSID value in this region, you must first stop the SSI.
To stop the SSI, issue the following command:
SYSPARM SSID=NO
You can then specify the new value using the following command:
SYSPARM SSID=xxxx (xxxx = the SSID value)
Reason:
USS/SSI support is required for issuing NETSTAT when using IBM stacks. The local system is using TCPAccess and does not require UNIX System Services for NETSTAT facilities.
System Action:
None.
User Action:
None.
Reason:
A UNIX environment has been opened, and sample SHELL commands have been successfully processed. The interface between this region and the SOLVE SSI region which communicates with UNIX System Services is fully functional.
System Action:
None.
User Action:
None.
Reason:
P1 displays the response from the id shell command. It displays the user ID and group name associated with the SOLVE SSI address space. This is the user ID under which all UNIX commands are executed.
The format is:
uid=runum(user) gid=rgnum(groupname)
For an explanation of this response, see the UNIX System Services Command Reference manual.
System Action:
None.
User Action:
None.
Reason:
P1 is the SOLVE SSI user's default working directory name. This is the initial directory path name set by the HOME=... operand specified in the OMVS segment of the security profile.
System Action:
None.
User Action:
None.
Reason:
A z/OS UNIX environment has been opened. A sample SHELL command has been processed. STDERR output has been received in response to the command, and the STDERR text indicates a problem with the home directory.
The home directory is defined in the OMVS segment for the user ID associated with the SOLVE SSI started task. See the message IPDI5274 for details of the user ID.
Common causes of home directory problems include:
System Action:
None.
In general, home directory related problems do not affect normal operation because the z/OS UNIX features used by the region do not involve the home directory. However, they may indicate other problems with your user ID security or z/OS UNIX setup.
User Action:
Proceed as normal. If any operational errors are encountered, investigate and rectify the condition, and retry the operation.
Accessing z/OS UNIX
The region needs to access z/OS UNIX to issue the NETSTAT and ONETSTAT commands, and to perform other socket-related processing provided by z/OS UNIX.
For the region to be able to access the z/OS UNIX environment, the CA ACF2, CA Top Secret, or RACF OMVS segment for the user ID associated with the SOLVE SSI started task must have been correctly set up. The SOLVE SSI performs all z/OS UNIX functions on behalf of this region.
If this OMVS segment is not correct, error conditions can occur.
Setting Up the SOLVE SSI user ID OMVS segment
For information about this task, see the Installation Guide for your product. Your CA ACF2, CA Top Secret, or RACF security administrator performs this task.
Investigating a z/OS UNIX home directory error
Get the exact STDERR message text from the activity log, for example, 'cannot change to HOME directory'.
'cannot change to HOME directory' is a common error. It generally indicates that the home directory defined for the SOLVE SSI user ID's OMVS segment does not exist or cannot be accessed.
Contact your security administrator to review the home directory path name defined for the SOLVE SSI user ID.
Contact your z/OS UNIX administrator or systems programmer to ensure that the HFS file system supporting this home directory path name is defined and correctly mounted, and that the user ID has read, write, and execute permission to the home directory.
The following OCS commands may be helpful:
USS WHOAMI displays the UID name of the SOLVE SSI user ID.
USS ID displays the UNIX user and group IDs, and names of the SOLVE SSI user ID.
USS PWD displays the working directory path name of the SOLVE SSI user ID.
Reason:
An attempt to communicate with the UNIX System Services shell has failed. This may be preceded by messages listing the exact error cause.
System Action:
None.
User Action:
Refer to any preceeding error messages for details.
Reason:
A UNIX operation attempted by the TCP/IP Services Self Test procedure has failed. P1 is the failing operation, P2 is the return code and feedback, and P3 is the reason text.
System Action:
None.
User Action:
If you received feedback code 5 (UNIX assembler call failed) or 9 (Subtask initialization failed), investigate the additional details provided by message IPDI5279.
Look at the SOLVE SSILOG and see if it contains any messages related to error conditions.
Confirm that you have set up the USS SSI interface correctly, including:
- Upgrading the SOLVE SSI software to the correct level
- Adding parameter UNIX=YES to the SOLVE SSI region
- Adding a RACF/ACF2/Top Secret OMVS segment, defined with a valid user ID, to the user ID associated with the SSI started task
- Verifying that, if present in the user's home directory, the .profile file is valid.
If you are unable to determine the nature of the error by using this information, contact your Techical Support Representative.
Reason:
A UNIX assembler call or subtask initialization call has failed.
P1 indicates the specific macro call which failed. The value shown corresponds to the call offset listed in the 'System Control Offsets to Callable Services' chapter in the OS/390 UNIX System Services Assembler Callable Services manual.
P2 and P3 are the return code and reason code from the failing macro call. These are listed in the OS/390 UNIX System Services Messages and Codes manual.
System Action:
None.
User Action:
Confirm that you have set up the USS SSI interface correctly, including:
- Upgrading the SOLVE SSI software to the correct level
- Adding parameter UNIX=YES to the SOLVE SSI region -
Adding a RACF/ACF2/Top Secret OMVS segment, defined with a valid user ID, to the user ID associated with the SSI started task
Reason:
The UNIX System Services SYSLOGD interface is being checked.
System Action:
None.
User Action:
None.
Reason:
This message displays the status of the syslogd pipe receiver. P1 has the following values:
System Action:
None.
User Action:
If you want to start or stop the syslogd pipe receiver, change the settings in the SYSLOGD parameter group and action the parameter group.
If the status is waiting for pipe to open, restart the USS syslog daemon.
Reason:
The OSA/SF interface is being checked, including:
System Action:
None.
User Action:
None.
Reason:
Communication from TCP/IP Services to the OSA/SF Interface has succeeded.
System Action:
None.
User Action:
None.
Reason:
The OSA/SF started task is not active.
System Action:
None.
User Action:
If you want to use OSA/SF functions, start the OSA/SF started task.
Reason:
An attempt to communicate through the OSA/SF interface failed. Specific errors have been written to the Activity Log.
System Action:
None.
User Action:
Investigate the specific messages on the Activity Log.
Reason:
An attempt to communicate through the OSA/SF interface failed because the OSA/SF API load module IOAEXEC cannot be loaded.
System Action:
None.
User Action:
If you do not intend to use OSA/SF for OSA monitoring, disregard this message.
The OSA/SF load library SYS1.SIOALMOD must be made accessible to this region by putting it in the LINKLIST or the STEPLIB concatenation.
Reason:
The OSA/SF Interface is not used by this region. No OSA definition has the field Use OSA/SF? set to YES.
System Action:
None.
User Action:
None.
Reason:
An attempt to communicate with the OSA/SF interface failed and its status cannot be determined.
System Action:
None.
User Action:
This condition is probably caused by an OSA/SF started task that is not responding; therefore, you may have to restart the started task.
For information about how to restart the started task, see the Open Systems Adapter Support Facility User's Guide.
Reason:
Configuration details have been collected and listed for this region. P1 indicates the existence of any of the following conditions:
Errors can affect region functions. You should investigate all errors.
Warnings may affect region functions. If you are experiencing any problems or unexpected results with region usage, you should investigate the warnings.
Notes are for information only. Assess these in the context of your specific environment.
System Action:
None.
User Action:
None.
Reason:
Specific help is available for many SELFTEST warning or error messages.
In OCS, Command Entry, or the activity log, place the cursor on the message and press F1=Help.
System Action:
None.
User Action:
None.
Reason:
The SAB and related control block chains are being checked, including:
System Action:
None.
User Action:
None.
Reason:
SELFTEST has determined that the System Anchor Block (SAB) does not exist. The SAB is created by the SOLVESSI region when it is initializing.
System Action:
None.
User Action:
Verify that the SOLVESSI region has been started. If not, start the SSI and retry. Note that the SSI must be at Delivery Level 5.0 or later.
Reason:
SELFTEST discovered that SWSS control block does not exist. This control block, part of the SAB structures, is created when the SOLVESSI region is started.
System Action:
None.
User Action:
See message IPDI52A1.
Reason:
SELFTEST discovered that DSAT control block does not exist. This control block, part of the SAB structure, is created when the SOLVESSI region is started.
System Action:
None.
User Action:
See message IPDI52A1.
Reason:
SELFTEST discovered that DSTE control block does not exist. This control block, part of the SAB structure, is created when the SOLVESSI region is started.
System Action:
None.
User Action:
See message IPDI52A1.
Reason:
SELFTEST discovered that SMFS has not been created. It should have been created by the starting of SSI.
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that SMFS has not been completed. This indicates incomplete SMF initialization.
P1 is an error description: header - invalid eyecatcher version - invalid version
System Action:
None.
User Action:
Check the SSI log for error messages, and fix reported problems.
Reason:
SELFTEST discovered that SMCT has not been created. This indicates incomplete SMF initialization.
System Action:
None.
User Action:
Check the SSI log for error messages, and fix reported problems.
Reason:
SELFTEST discovered that SMCT has not been completed. This indicates incomplete SMF initialization.
P1 is an error description: header - invalid eyecatcher version - invalid version
System Action:
None.
User Action:
Check the SSI log for error messages, and fix reported problems.
Reason:
An internal control block, and any subordinate control blocks, have been tested, and they pass all checks. The control block structure ( P1 ) that was tested is as follows:
System Anchor : System Anchor Block (SAB) structures
Packet Analyzer : Packet Analyzer structures
SMF exit : SMF exit and record intercept structures
System Action:
None.
User Action:
None.
Reason:
CA Common Services is active. Detected version (if not N/A) is P1
P1 denotes detected CA Common Services level in format vvrrmm or N/A if version is not available. vv denotes the Version level. rr denotes the Release level. mm denotes the Service Pack level.
System Action:
None.
User Action:
None.
Reason:
NetMaster SMF exits common code load module is resident.
System Action:
None.
User Action:
None.
Reason:
SMF records will be processed by NetMaster SMF exits code.
System Action:
None.
User Action:
None.
Reason:
Shows the actual NetMaster SMF exits code status, where P1 :
Registered - Loaded for the first time, SMF record processing active.
Deregistered - Unloaded and unactivvated, SMF records processing disabled.
Reregistered - Reloaded and reactivated, SMF record processing resumed.
System Action:
None.
User Action:
None.
Reason:
SMF records that are intercepted by NetMaster may be written to the SMF data sets (SYS1.MANx), or suppressed. The factors that determine when a record is written or suppressed are:
- The Application Name definition entries (see /IPAPPLS). These will specify either WRITE, NOWRITE, or DEFAULT.
- If DEFAULT, the SMF default action as specified by the PASMFWRITE parameter (WRITE or NOWRITE).
The message indicates that the SMF default action is WRITE so that, by default, records are written to the SMF data set.
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that the old SMF exit, NMSMFIBM, is active in the system. NMSMFIBM became obsolete in Delivery Level 5.1 (Version 7.0 of your product).
System Action:
None.
User Action:
If you are no longer using a Version 7.0 product, you should remove this exit. To do this, remove all references to module NMSMFIBM in any PARMLIB members, for example:
For more information, see Installation Guide.
Reason:
Self-testing of SMF support is terminated because the data returned by an SMF exit query request is corrupt. The corrupt data is displayed ( P1 ).
System Action:
None.
User Action:
This is an internal error. Contact Technical Support.
Reason:
SELFTEST discovered that the SMF exit P1 of CA Common Services version
P2 has a status of P3 . Status can be one of the following:
OK - No problems detected.
DEREG - One of the exit copies is deregistered.
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that the P1 SMF exit did not receive any SMF records.
If the situation continues, or records seem to be missing from connection lists or workload reporting, check for the following situations:
System Action:
None.
User Action:
None.
Reason:
SELFTEST indicates that the TCPIP SMF record currently being processed by SMF exits code is P1 .
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that CA Common Services was not started or failed to complete.
System Action:
None.
User Action:
Check whether CA Common Services was started or failed during execution. Check the system log for possible problems. Start CA Common Services.
Reason:
SELFTEST discovered that the NetMaster SMF exits common code load module is not resident. This indicates that, although SMF exit registration was attempted by theSSI, there were problems loading common NetMaster SMF exits code into memory.
System Action:
None.
User Action:
Check for error messages issued by SSI, fix the problems, and restart the SSI.
Reason:
A version of the SSI that supports SMF has been activated with the parameter IPSMF=NO. SMF record processing may be disabled.
This may be because you are running the current version of a product with an older product.
System Action:
None.
User Action:
Investigate why this occurred.
If you want to run the current version of the SSI (that is, the one distributed with r11.6) with an r11 SSI, you must ensure that the current SSI is started last.
Note: There are no compatibility problems between SSI code from r11.6 and r11.5 - only between r11.6 and r11.
IPDI52B7 SMF exit: Y7FU83, version: Y760, status: OK
IPDI52B7 SMF exit: Y7FU83, version: Y750, status: DEREG
IPDI52B7 SMF exit: Y7FU84, version: Y760, status: OK
IPDI52B7 SMF exit: Y7FU84, version: Y750, status: DEREG
IPDI52B7 SMF exit: Y7FU85, version: Y760, status: OK
IPDI52B7 SMF exit: Y7FU85, version: Y750, status: DEREG
NY3730 SMF EXITS DEREGISTERED SUCCESFULLY
NY3720 SMF EXITS REGISTERED SUCCESSFULLY
If you do not see the NY3730 and NY3720 messages, or IPDI52B7 messages with DEREG, consider the following actions while the r11.6 SSI coexists with r11:
F ssiname,SMF STATUS
F ssiname,STATUS
Verify that the SMF record count is growing.
If you have questions or problems with SSI compatibility between releases, contact Technical Support.
Reason:
SELFTEST discovered that SMF exits registration failed.
System Action:
None.
User Action:
Check SSI log for reasons, fix the problems, and restart the SSI.
Reason:
SMF records that are intercepted by NetMaster may be written to the SMF data sets (SYS1.MANx), or suppressed. The factors that determine when a record is written or suppressed are:
- The Application Name definition entries (see /IPAPPLS). These will specify either WRITE, NOWRITE, or DEFAULT.
- If DEFAULT, the SMF default action as specified by the PASMFWRITE parameter (WRITE or NOWRITE)
The message indicates that the SMF default action is NOWRITE so that, by default, records are not written to the SMF data set.
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that the SMF exit is not registered.
P1 is the functional name of the exit, for example, IEFU83, IEFU84, IEFU85.
P2 (if present) is the CA Common Services version of the exit.
System Action:
None.
User Action:
Check the SSI log for reasons and check if the exit was deregistered by a separate action. Reregister the exit, if required.
Reason:
SELFTEST was unable to obtain the status of the SMF exit that has been registered.
P1 is the name of the exit.
P2 is the reason:
NOTINSTL - TNG query function is not present or not operational.
EPSRDOWN - TNG query EPS receiver is not present (SSI not active).
NOENDPT - SSI EPS receiver servicing TNG query routine is not active.
OSLEVEL - Operating system level is lower than OS/390 2.5, or is not OS/390 or z/OS.
DYNSTOR - Serious storage constraints in SSI.
EPSRC=nn - Internal: Interface error nn.
REQSENT - Internal: Request was sent but reply was not received.
AREA - Internal: Dynamic reply area too short.
REQC - Internal: Invalid request code.
NOSRVC - Internal: SSI Query service routine has not been registered because CAISMFQ is not available.
NOSMFQ - Internal: CA Common Services (TNGFW) query routine (CAISMFQ) is not available.
System Action:
None.
User Action:
NOTINSTL - Make sure that installation did not fail.
EPSRDOWN - Make sure that SSI is running; if so, issue SSI STATUS and check message NY3201, and restart SSI if necessary.
NOENDPT - Restart SSI.
OSLEVEL - Make sure you are running OS/390 2.5+ or z/OS.
DYNSTOR - Check whether SSI has been started in a region with enough space.
EPSRC - Contact Technical Support with details.
REQSENT - Contact Technical Support with details.
AREA - Contact Technical Support with details.
REQC - Contact Technical Support with details.
NOSRVC - Verify that the current version of CA Common Services for z/OS has been installed. If yes, Contact Technical Support with details.
NOSMFQ - Verify that the current version of CA Common Services for z/OS has been installed. If yes, Contact Technical Support with details.
Reason:
SELFTEST discovered that the SMF exit is flagged as abended.
P1 is the real (load module) name of the exit.
System Action:
None.
User Action:
Check the system log for information, collect the necessary debugging information (SVC dump), and If yes, contact Technical Support.
Reason:
SELFTEST discovered that NetMaster SMF processing was disabled. It means that SSI command SMF DEREGISTER was executed. NetMaster SMF TCPIP records processing was stopped and code was removed from memory.
System Action:
None.
User Action:
Check the reasons of de-registration, re-register if necessary.
Reason:
SELFTEST was unable to obtain the status of CA Common Services.
P1 is the reason:
NOTINSTL - Agent Technology query function is not present or not operational.
EPSRDOWN - Agent Technology query EPS receiver is not present (SSI not active).
NOENDPT - SSI EPS receiver servicing TNG query routine is not active.
OSLEVEL - Operating system level is lower than OS/390 2.5; or not OS/390 or z/OS.
DYNSTOR - Serious storage constraints in SSI.
N/A - CA Common Services version is not available or is not valid. It is normal when SMF-aware SSI is not running or connected or IP SMF API is used to collect SMF data.
NOSMFQ - CA Common Services CAISMFQ function is not available.
EPSRC=nn - Internal: Interface error nn.
REQSENT - Internal: Request was sent but reply was not received.
AREA - Internal: Dynamic reply area is too short.
REQC - Internal: Invalid request code.
NOSRVC - Internal: Query service routine has not been registered.
System Action:
None.
User Action:
NOTINSTL- Ensure that the CA NetMaster installation did not fail.
EPSRDOWN- Ensure that SSI is running; if so, issue SSI STATUS and check message NY3201, and then restart SSI if necessary.
OSLEVEL - Ensure you are running OS/390 2.5+ or z/OS.
NOENDPT - Restart SSI.
DYNSTOR - Ensure SSI is started in a large enough region.
N/A - Contact your System Programmer to verify the level of CA Common Services installed.
NOSMFQ - Contact your System Programmer to verify the level of CA Common Services installed.
EPSRC - Contact Technical Support with details.
REQSENT - Contact Technical Support with details.
AREA - Contact Technical Support with details.
REQC - Contact Technical Support with details.
NOSRVC - Contact Technical Support with details.
Reason:
Socket Management is being checked, including:
System Action:
None.
User Action:
None.
Reason:
The event receiver for Socket Management has a status of P1. Status is one of the following:
* ACTIVE - The receiver is active and able to receive events.
* INACTIVE - The receiver is inactive. This is due to the system not being licensed for SocketMgmt or due to a define failure (check the activity log for SKEV25* messages for details).
* PENDING - The receiver process is pending. Retry in a short while to see the current status.
System Action:
None
User Action:
Contact your System Administrator.
Reason:
This message contains Socket Management servers information.
The information shown is a list of active Socket Management servers displaying CICS region name; command server address and port; whether the CICS is defined in the resource monitor; and whether CICS security is on.
Each of these active Socket Management servers is actively being monitored by the Socket Management event receiver.
System Action:
None
User Action:
None
Reason:
This message contains general information about Socket Management.
System Action:
None
User Action:
None
Reason:
SELFTEST discovered that CA Common Services SMF Query facility (CAISMFO) has not been found.
System Action:
None.
User Action:
Check whether the required version of CA Common Services was installed. Previous message IPDI52B0 shows the detected level.
Reason:
SELFTEST discovered that NetMaster SMF exits were started before the required environment was in place.
It may indicate that the exits code was activated before SSI started or SSI may have failed to create the required environment.
Note:
Although the situation may have been rectified, the error indicator stays on until the system is IPL-ed, to indicate the intermittent nature of detected errors.
System Action:
None.
User Action:
Check whether NetMaster exits were started manually or through SSI. Check if SSI was started before CA Common Services (CAS9) and if it was, restart SSI.
Reason:
SELFTEST discovered that NetMaster SMF exit P1 detected error P2 It indicates that NetMaster SMF exits code has been started (most probably manually) before SSI start.
P1 is exit name
P2 is an error code:
SMFS - unfinished SAB/SMFS detected
SMCT - missing/unfinished SMCT detected
CCDE - Common Code is not loaded
Note: Although the situation may have been rectified, the error indicator stays on until the system is IPL-ed, to indicate the intermittent nature of detected errors.
System Action:
None.
User Action:
Check whether NetMaster exits were started manually or through SSI. Check if SSI was started before CA Common Services (CAS9) and if it was, restart SSI.
Reason:
SELFTEST discovered that the P1 SMF exit detected an invalid SMF record. The record received for processing was not of Type 119. This is a result of logic check.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The P1 SMF exit detected Type 118 SMF records that contain IPv6 local or remote addresses. This indicates that IPv6 is active on an IBM TCP/IP stack and Type 118 SMF records are being produced. Type 118 SMF records are not compatible with IPv6, and should not be used with IPv6 or dual mode IBM TCP/IP stacks.
System Action:
None.
User Action:
Contact your Systems Programmer, and investigate whether you need to reconfigure the collection of SMF records to produce Type 119 SMF records instead.
Reason:
The SMF exit P1 detected type 119 SMF records that contain IPv6 local or remote host addresses. This indicates that IPv6 is active on an IBM TCP/IP stack. The current CA NetMaster release does not support IPv6 host addresses, and it ignores SMF records that contain them.
System Action:
None.
User Action:
None.
Reason:
SELFTEST discovered that multiple copies of SMF exits are concurrently active in the system.
P1 is the SMF exit load module name.
P2 is the CA Common Services version of the first active copy.
P3 is the CA Common Services version of the second active copy. The CA Common Services SMF version is of the format Y7ms, where ms is the product Delivery Level. Current versions are as follows: Y750 - Release 7.0 Y760 - r11 Y770 - r12
System Action:
None.
User Action:
Check if different versions of SSI are running concurrently. Identify which of them corresponds to each provided version. Issue the command
f ssiname,smf dereg for the SSI that corresponds to the older version.
Rerun SELFTEST to verify the results of the action. If the older version reported is Y750 and the SSI is not running, you can start it by issuing the deregistration command and stopping it.
If you experience problems running more than one SSI concurrently, you should consider using the SMFDEREG utility. It must be run from an authorized load library, the product library being the obvious choice.
The JCL example to run SMFDEREG is as follows:
// JOB //SMFDRG EXEC PGM=SMFDEREG,PARM='Y750' //STEPLIB DD DISP=SHR,DSN=HLQ.NMRXX.LOAD //
The program attempts to deregister Y750 version SMF exits. Information about the execution is provided in the form of console messages (WTO).
If you cannot determine which version to deregister, you can run SMFDEREG without specifying parameters. It will try to deregister all known versions of the SMF exits. You must start the latest version of the SSI with SMP support and issue f ssiname,smf reg after it starts.
Reason:
SELFTEST discovered that none of multiple copies of SMF exits known to CA Common Services are active in the system.
P1 is the SMF exit functional name.
P2 is the CA Common Services version of the first known copy.
P3 is the CA Common Services version of the second known copy.
System Action:
None.
User Action:
Check if any version of SSI is running. If it corresponds to the latest version of the exit, issue f ssiname,smf reg . If it fails, check the log and investigate. Rerun SELFTEST.
Reason:
SELFTEST of SMF support was terminated.
P1 is the reason:
SAB - System Anchor Block was not created. It indicates that NetMaster SSI was not run or it failed to create SAB. If NetMaster SSI was run, check SSI log for messages related to SAB creation.
SMFS - SMF Slot in SAB was not created or invalid. It indicates that NetMaster SSI was not run or it did not create/finalise SMFS. It may indicate the fact that none of NetMaster SSIs was started with SMF=YES specification. If NetMaster SSI was run with SMF=YES specified, check SSI log for messages related to SMF activation.
SMCT - SMF Control Table was not created or invalid. It indicates that NetMaster SSI was not run or it did not create/finalise SMCT. It may indicate the fact that none of NetMaster SSIs was started with SMF=YES specification. It may also indicate that SMF registration failed. If NetMaster SSI was run with SMF=YES specified, check SSI log for messages related to SMF activation.
System Action:
None.
User Action:
Make sure that one of NetMaster SSIs is dedicated as SMF controlling and is started with SMF=YES specified.
Reason:
The SSI and Packet Analyzer configuration is being checked, including:
System Action:
None.
User Action:
If SOLVE SSI is not active on this system, start it.
Errors in the SSI and Packet Analyzer will result in major loss of function.
The SOLVE SSI runs as a separate started task to this region and has its own specific setup requirements.
Review the SSI setup information in the product Installation Guide.
Reason:
The SOLVE Subsystem Interface is defined with P1 as the SSID value.
The SSID is specified in the $NM SSI Customizer parameter group (/PARMS).
System Action:
None.
User Action:
None.
Reason:
The connectivity being tested requires a connection to an SSI started task that includes support for the Packet Analyzer.
Packet Analyzer support is not configured in the connected SSI task (SSID P1), nor any interconnected SSI task. The Packet Analyzer may have been disabled by SSI parameter PKTANALYZER=NO or PALEVEL=NONE. Also, you may have connected this region to the wrong SSID.
Although Packet Analyzer is not necessary to operate CA NetMaster, it provides data needed by the following:
System Action:
None.
User Action:
Ensure that one of the SSI started tasks in the LPAR provides support for the Packet Analyzer. To provide the service, an SSI started task must include the parameter PKTANALZER=YES. Parameter PALEVEL must also be set to FULL.
Note: If you need to change the SSI started task parameters, you must restart that started task. You can have multiple SSI started tasks in an LPAR, but only one of these may be configured with Packet Analyzer support.
To determine the facilities provided by the SSI that this region is connected to, issue the following command in OCS or Command Entry:
SSI STATUS
To determine the facilities provided by any SSI started task, you must use the SYSCMD facility to send a message to that started task, for example:
F taskname,SSI STATUS
taskname is the name of the SSI started task.
If the SSI provides Packet Analyzer support, the output from the SSI STATUS command includes the following message:
NFST01 PACKET ANALYZER FEATURE IS ACTIVE
If you connected the region to the wrong SSI started task, you must change the SSID that is specified in the region. To do this, you must update the SSI parameter group in Customizer and action the group as follows:
Reason:
The Packet Analyzer is active and the indicated number of TCP/IP stacks have packet analysis enabled.
System Action:
None.
User Action:
Additional details regarding the status of the Packet Analyzer and of specific stacks for which packet analysis is either requested or enabled are available using the following commands and displays.
Use the /IPPAREQ shortcut to display the TCP/IP : Packet Analysis Request List. This list shows all packet analysis requests for this LPAR.
Use the SSI's SHOW STACKS command to display the stacks that the Packet Analyzer is aware of, and which have packet analysis enabled.
Use the SSI's STATUS command to display the status of the Packet Analyzer.
SSI commands can be entered from a NetMaster region using the SSISEND command. For example:
SSISEND SHOW STACKS SSISEND STATUS
Reason:
The connectivity being tested requires a connection to an SSI started task that includes support for the CA Common Services query support.
This error usually occurs when you have specified the wrong SSID value. This region is connected to an SSI region (using SSID P1). However, neither that SSI started task, nor any interconnected SSI task, is configured with the CA Common Services query support.
Although query support is not necessary for proper operation of this region, it is a prerequisite for SMF exit registration.
System Action:
None.
User Action:
Ensure that one of the SSI started tasks in the LPAR provides support for CA Common Services query.
To provide the service, an SSI started task must include the following parameter: TNGFWQ=YES (the default).
Note: If you need to change the SSI started task parameters, you must restart that started task. You can have multiple SSI started tasks in an LPAR, but only one of these can be configured with Packet Analyzer support.
To determine the facilities provided by the SSI that this region is connected to, issue the following command in OCS or Command Entry: SSI STATUS.
Reason:
The Packet Analyzer is currently running with statistics collection disabled. The SSI region may have started with PALEVEL=NOSTATS, or the level may have been dynamically changed to a value of NOSTATS.
When the Packet Analyzer is not collecting statistics, many of the performance data and data sampling facilities are unavailable.
System Action:
None.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, many IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
The Packet Analyzer is currently running with packet intercept disabled. The SSI region may have started with PALEVEL=NOPACKETS, or this level may have been modified dynamically.
When the Packet Analyzer has packet intercept disabled, many tracing and traffic facilities are unavailable.
System Action:
None.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
The Packet Analyzer is not using the current software level for this release. SmartTrace facilities are not available.
System Action:
None.
User Action:
Your region should be connected to an SSI region of the same or later release. The SSI facilities are backward-compatible, so that an older release of the region can successfully connect to a later release of SSI; however, connecting a region to a back-level SSI results in loss of functionality.
Reason:
This message displays the usage of a Packet Analyzer database. The database is a dataspace, not a physical file.
P1 is the database type.
P2 is the maximum database size in MB.
P3 is the current percentage used.
P4 is the highest percentage used since the SSI region was last started.
System Action:
None.
User Action:
If the database utilization is approaching 100%, consider increasing the database size on the next restart of the SOLVE SSI region. The database size is set by SSI startup parameters:
Dynamic database : PDYNDBSIZE
Synch Database : PSYNDBSIZE
Trace Database : PTRCDBSIZE
Reason:
The Packet Analyzer is not running in the mode that was requested,for example, zIIP mode execution may have been requested, but cannot be provided.
System Action:
None.
User Action:
See the help for messages NF1018 and NF1019, which precede this one. The NF1019 help contains information about diagnostic codes. To access the message help, place the cursor on message ID NF1019 and press Enter.
For information about SSI configuration, use the SSI STATUS command.
Reason:
The SSI region has started with the PAEESTACK parameter set to the name of the z/OS stack that does Enterprise Extender (EE) processing on this LPAR.
Specifying the PAEESTACK parameter enables all of the CA NetMaster EE management functions, which you can access using shortcut /EE .
If you do not have EE implemented on this LPAR, leave the PAEESTACK parameter to default to NONE.
Generally, PAEESTACK is generated by the Install Utility that creates the SSI JCL, when you enter an EE Packet Processing Stack Name.
System Action:
The packet analyzer recognizes EE packets, and performs specialist traffic analysis, connection analysis, and tracing for EE.
User Action:
All of the CA NetMaster Enterprise Extender functions are now available from the Enterprise Extender Management Menu, shortcut /EE . These include the following:
Reason:
The SSI region was not started with the PAEESTACK parameter; however, an EE XCA Major Node is active on this LPAR.
Specifying the PAEESTACK parameter enables all of the CA NetMaster advanced Enterprise Extender management functions.
System Action:
The packet analyzer contines to count EE packets as part of normal UDP traffic, but does not recognize them as EE.
Specialist EE traffic analysis, connection analysis, and packet tracing are not available on this CA NetMaster region.
User Action:
Perform the following:
1. Contact your Systems Programmer or CA NetMaster Administrator and ensure that the SSI region is updated with the PAEESTACK parameter set to the name of the z/OS stack that does Enterprise Extender (EE) processing on this LPAR.
Note: If there are multiple stacks on this LPAR, only one performs EE processing.
2. Restart the SSI region.
3. Explore the CA NetMaster Enterprise Extender functions. They are available from the Enterprise Extender Management Menu, shortcut /EE . They include the following:
Reason:
This message provides headers for the following IPDI52G1 messages.
System Action:
None.
User Action:
None.
Reason:
This message provides the following information about each of three SMF exits stubs:
P1 : SMF Exit module name.
P2 : Entry Point address of the starting module.
P3 : Management Services version of the starting module.
P4 : PFT level of the starting module.
P5 : Compilation time stamp of the starting module.
System Action:
None.
User Action:
None.
Reason:
This message provides the information on the latest status change of each of the SMF exits stubs:
P1 : Type of the change, i.e: registered or deregistered . If the change is 'deregistered' it means that manual action was taken to disable SMF support.
P2 : Jobname of the STC/Job which changed exit status, i.e: registered or deregistered the exit.
P3 : The date of the status change in YYYYMMDD format.
P4 : The time of the status change in HHMMSS format.
System Action:
None.
User Action:
If the change is registered : None.
If the change is deregistered : Investigate the reasons for the deregistration, analysing the System/SSI log may help in identifying the person deregistering the SMF support. Check if SelfTest detected that the exits abended. If the reasons for deregistration were not serious, system exposure for example, it is important to enable SMF processing again to restore the full functionality of the Product. Issue 'f ssiname,SMF REGISTER' where ssiname is the STC/Jobname of the SSI controlling SMF activities of the Product.
Reason:
A Self Test Collect recovery code was entered due to the invalid storage address detection. P1 provides the line number in the Self test source. This message indicates that the control block contents chained from SMCT (SMF Control Table) is corrupted.
System Action:
None.
User Action:
1. Preserve the Self Test execution log.
2. From the OCS (Operator Console Services) command prompt, enter $NMUT31L and press ENTER.
3. When presented with the control block selection list, select SMCT and press ENTER. You will be presented with an SMCT hexadecimal dump.
4. Preserve the SMCT hexadecimal dump.
5. Contact your local Technical support providing:
- Self Test execution log
- SMCT dump
Reason:
The SMF configuration of the IBM z/OS Communications Server TCP/IP stack is being checked, including:
System Action:
None.
User Action:
None.
Reason:
IBM IP SMF configuration check encountered TCPAccess Stack while scanning through the connected Stacks list.
System Action:
None.
User Action:
None.
Reason:
The IBM stack configuration for stack P1 does not contain an SMF configuration section.
This message indicates serious IP Stack configuration problems. P1 is the stack name.
System Action:
None.
User Action:
Perform the following steps:
1. From the Operator Console Services (OCS) command prompt, enter the following command and verify the absence of the section that starts with SMF Parameters:
-onetstat - p P1 -f
2. Verify and correct the IBM TCP/IP stack configuration.
3. Contact Technical Support if the section exists.
Reason:
The IBM stack configuration for the P1 stack does not contain the section for Type 119 SMF records.
This message indicates serious IP Stack configuration problems.
System Action:
None.
User Action:
1. From the Operator Console Services (OCS) command prompt, enter the following command and verify the absence of the section that starts with Type 119:
-onetstat - p P1 -f
2. Verify and correct the IBM TCP/IP stack configuration.
3. Contact Technical Support if the section exists.
Reason:
The IBM stack configuration for stack P1 does not contain the section that corresponds to the TCP/IP SMF records to process by the product. P1 is the Stack Name. P2 is the number of the SMF record section missing.
System Action:
None.
User Action:
Perform the following steps:
1. From the Operator Console Services (OCS) command prompt, enter the following command and verify the absence of the section that starts with Type P2 :
-onetstat - p P1 -f
2. Verify and correct the IBM TCP/IP stack configuration.
3. Contact Technical Support if the section exists.
Reason:
The IBM stack configuration for stack P1 , section for record P2 does not have subrecord type P3 turned on.
P1 is the Stack Name
P2 is the SMF record number
P3 is the SMF subrecord type:
- TCPINIT
- TCPTERM
- FTPCLIENT
- TN3270CLIENT
System Action:
None.
User Action:
Perform the following steps:
1. From the Operator Console Services (OCS) command prompt, enter the following command and verify the setting of the P3 subrecord type in the Type P2 : section.
-onetstat -p P1 -f
2. Verify and correct the IBM TCP/IP stack configuration.
Reason:
The configuration of the IBM stack Telnet server does not have SMF recording specified for the identified port.
P1 is the name of the stack.
P2 is the Telnet server port number.
P3 is the type of SMF record:
ALL - No SMF specification for the port
INIT119 - SMF initialization record for SMF record type 119
TERM119 - SMF termination record for SMF record type 119
STD - SMF records for SMF record type 118
Note: CA NetMaster NM for TCP/IP r11 supports SMF record types 118 and 119; however, r11.5 supports only record type 119. Specifying record type 118 while working with r11.5 is not an error and may be present due to the requirements of other products.
System Action:
None.
User Action:
If you do not want the port or the SMF record type, take no action; otherwise, take the following action.
If the port is an active Telnet data port, change its specification in the TELNET section of the Stack configuration to add SMF record collection.
You may consider using the TELNETGLOBALS section to activate SMF record collection if all defined Telnet ports are active.
Reason:
The stack detected is defined in the region tables but not currently active.
System Action:
None.
User Action:
Start the stack, if required.
Reason:
An attempt to send a Netstat or Display command to the IBM Stack failed.
P1 is the Stack Name
P2 is the Internal Return Code
P3 is the Reason message, if provided
System Action:
None.
User Action:
Address the issue as explained in the reason message and then repeat the test.
Reason:
The available IP Stack SMF configuration has the parameters set for correct generation of SMF records utilized by CA NetMaster. Specified parameters, for example, port number specifications, are correct but may be incomplete, that is, some port numbers used by the IP Stack may not be configured and are not detected or verified.
System Action:
None.
User Action:
None.
Reason:
The IBM MVS SMF configuration is being checked, including: The TCP/IP SMF record is not excluded from processing by the MVS SMF facility.
System Action:
None.
User Action:
None.
Reason:
An attempt to issue P1 MVS command ended with unexpected results.
P1 is the command executed.
System Action:
None.
User Action:
See message IPDI5209 and follow the instructions.
Contact Technical Support if you are unable to to resolve the problem.
Reason:
MVS SMF configuration excludes from processing the TCP/IP SMF record P1 specified as processed by the product. P2 is the SMF configuration statement that contains the exclusion.
System Action:
None.
User Action:
Verify and correct the MVS SMF configuration, removing the exclusion.
Reason:
The SSI SMF exit registration and setup is being checked.
System Action:
None.
User Action:
None.
Reason:
MVS SMF configuration has all of the required parameters set for correct generation of SMF records.
System Action:
None.
User Action:
None.
Reason:
SMF exit P1 detected that an invalid code was detected by one of the Common Code stages. This indicates internal error.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
SMF exit P1 detected that an invalid return code was returned by one of the Common Code stages. This indicates internal error.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
SELFTEST discovered that the P1 SMF exit detected an invalid SMF record. This indicates that one of the processed SMF records failed one of the basic integrity and validity checks. It may indicate a misformatted IBM SMF record, or the occurrence of an SMF record of Type 119 that was probably produced by a program other than the IBM TCP/IP stack (IBM Communications Server for eBusiness).
System Action:
None.
User Action:
Verify that no other program is producing SMF records of Type 118 or 119.
Issue F ssiname,SMF STATUS, and check the rejected record count in the NY3137 message. If the count is significant compared to the number of received records, you may be able to find those records by analyzing the SMF data sets.
For assistance, contact your Systems Programmer.
Reason:
The IBM stack configuration for stack P1 contains the section for SMF record 118, which is not supported.
System Action:
None.
User Action:
Remove SMF record 118 definitions from IBM stack configuration, unless SMF record 118 is collected for purposes other than connection awareness.
Reason:
The Telnet server configuration of the IBM stack has SMF recording specified for a given port, and the Network Management API is active.
P1 is the name of the stack.
P2 is the port number of the Telnet server.
P3 (if specified) is the SMF record type:
ALL - No SMF specification for the port
INIT118 - SMF initialization record for SMF record type 118
TERM118 - SMF termination record for SMF record type 118
INIT119 - SMF initialization record for SMF record type 119
TERM119 - SMF termination record for SMF record type 119
Note: r11 product supports both SMF record types 118 and 119, while r11.5 product supports only record type 119. Specification of record type 118 when working with an r11.5 product is not an error and may be present due to the requirements of another product.
System Action:
None.
User Action:
If only an r11.5 product is processing SMF records, disable the collection of Type 118 SMF records for the identified port.
Reason:
There are two ways to collect IP SMF data present at the same time. SMF Exit-based IBM TCPIP SMF record 119 collection is present on the system that is configured to use IBM Stack Network Management API. This is acceptable as a transtion situation, but should not be running on a permanent basis.
System Action:
None.
User Action:
Stop using old SMF exit-based IP data collection. Remove the definitions from STACK configurations.
Reason:
There is more than one Data Space type data collection active at the same time.
The list of job names of those services is provided as P1 - P6. There is a possibility of discontinued Data Space running concurrently with the Packet Analyzer, which may introduce duplicated information.
System Action:
None.
User Action:
Discontinue using old Data Space.
Reason:
The NMFTP Monitor, utilizing the IBM Stack Network Management SMF API, is being checked.
System Action:
None.
User Action:
None.
Reason:
The IBM P1 stack network management configuration does not have P2 specification.
P1 is the name of the Stack
P2 is one of the following:
TcpCnn - TCP connection services specification
SmfSrv - SMF services specification
System Action:
None.
User Action:
Perform the following steps:
-onetstat -p P1 -f
Reason:
The IBM P1 stack network management configuration P2 specification is not set to Yes.
P1 is the name of the Stack
P2 is one of the following:
TcpCnn - TCP connection services specification
SmfSrv - SMF services specification
System Action:
None.
User Action:
Perform the following steps:
-onetstat -p P1 -f
Reason:
If P1 is Y, IP SMF records received from Network Management API are written to the SMF data sets (SYS1.MANx).
If P1 is N, SMF records are not written.
System Action:
None.
User Action:
None.
Reason:
The EPS server P1 providing SMF API Network Management status information is not active. It may indicate that the NMFTP Monitor providing SMF API support is not active; however, it is required by CA NetMaster File Transfer Management for monitoring FTP events.
System Action:
None.
User Action:
If you are using CA NetMaster File Transport Management, make sure that the NMFTP Monitor providing SMF API was started. Start it if it is not active.
Perform the following steps if it is active:
SH EPS SERV=P1
Check the NMFTP Monitor log for possible explanations.
Reason:
The EPS server P1 providing SMF API Network Management status information returned unexpected result P2. This message may be issued because of the intermittent status of the EPS receiver maintained by the NMFTP Monitor. This is required by CA NetMaster File Transfer Management for Monitoring FTP events.
System Action:
None.
User Action:
If you are using CA NetMaster File Transport Management, make sure that the NMFTP Monitor providing SMF API was started. Start it if it is not active.
Perform the following steps if it is active:
SH EPS SERV=P1
Check the NMFTP Monitor log for possible explanations.
Reason:
An unexpected result was received while obtaining the Packet Analyzer Information (PAI) record. P1 is the return code.
System Action:
None.
User Action:
If the error persists, contact Technical Support with the SELFTEST output.
Reason:
You specified PASMFWRITE=YES, but no SMF records were written to SMF data sets. IBM's Network Management SMF API, which is used by the FTP Monitor Address Space, processes only FTP SMF record 119 subtypes 101 and 102.
This message may also indicate that there are no application definitions requesting writing of those records.
System Action:
None.
User Action:
If you want to write FTP SMF record 119 subtypes 101 and 102 only, specify PASMFWRITE=YES for the CA NetMaster FTP Monitor; otherwise, specify PASMFWRITE=NO.
Reason:
The interface to IBM Stack Network Management lost some SMF data blocks. This indicates that it is not performing fast enough.
System Action:
None.
User Action:
Check if CA NetMaster is performing in a low priority performance group or heavily-constrained environment. If it is, correct the situation. Contact Technical Support if you cannot rectify the situation.
Reason:
This message is the beginning of the Network Management Interface status information. It is followed by IPDI52L7, IPDI52L8, and IPDI52L9 messages. P1 is the job name of the SSI running it.
System Action:
None.
User Action:
None.
Reason:
This message provides a header for Network Management Interface status information. It is followed by IPDI52L8 and IPDI52L9 messages.
System Action:
None.
User Action:
None.
Reason:
This message provides a header for Network Management Interface status information. It is followed by message IPDI52L9.
System Action:
None.
User Action:
None.
Reason:
This is the last message for Network Management Interface status information.
P1 is the date and time the interface started.
P2 is the number of SMF records processed.
P3 is the number of SMF records written to SMF data sets. Unless PASMFWRITE=YES is specified, it should be 0.
P4 is the number of SMF blocks that were not processed by the Interface. Under normal conditions, it should be 0.
System Action:
None.
User Action:
None.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
A vartable error occurred. The vartable action was P1 , the feedback code was P2 . If relevant P3 contains the key value which experienced the problem.
System Action:
The action fails.
User Action:
Determine the cause of the error based on the feedback code.
Reason:
You attempted to add an entry for the address P1 . However the entry already exists.
System Action:
The action fails.
User Action:
None.
Reason:
An internal error occurred because the map P1 was not found in the map dataset.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
An internal error occurred. The map P1 experienced the error described by MDORC= P2 and MDOFDBK= P3 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
An attempt was made to start the IP Node Monitor but a previous copy is already running. The most likely scenario is that a LOAD has been requested and the current IP Node Monitor is performing cleanup processing before terminating.
System Action:
The existing IP Node Monitor continues and this one waits for it to conclude before continuing.
User Action:
None.
Reason:
The IP Node Monitor has been asked to stop.
System Action:
The IP Node Monitor terminates.
User Action:
None.
Reason:
The IP Node Monitor has started.
System Action:
The IP Node Monitor continues.
User Action:
None.
Reason:
An alert has been created by the IP Node Monitor function. The monitor attempted to ping the node with IP address P1
P2 is the status detected, it may be one of:
Timeout - The ping request for device timed out.
Unknown - Either a ping has not yet been done or the TCP/IP Services interface is unavailable.
System Action:
An alert is created.
User Action:
Check the status of the resource, by issuing the Check action against the node in the IP Node Monitor or against the alert in the Alert Monitor.
Reason:
The Check action has been issued for the IPNODE identified by P1.
System Action:
A sample is taken immediately.
User Action:
None.
Reason:
An alert has been created by the IP Node Monitor function. The monitor attempted to ping the node with IP address P1 . P2 is the average time to respond which is over the threshold specified as P3 .
System Action:
An alert is created.
User Action:
Check the status of the resource, by issuing the Check action against the node in the IP Node Monitor or against the alert in the Alert Monitor.
Reason:
A default monitor group definition has been added to the IPFILE.
System Action:
A monitor group definition is created.
User Action:
Review IP node monitoring requirements. You may wish to use one of the supplied monitoring groups.
Reason:
An error occurred adding a default monitor group definition to the IPFILE.
System Action:
The associated error message is logged after this message.
User Action:
Use the following log message to determine the cause of the failure. If necessary notify Technical Support.
Reason:
An alert has been created by the IP Node Monitor function. The monitor attempted to ping the node with IP address P1
P2 is the status detected, it may be one of:
Timeout - The ping request for device timed out.
Error - The ping request received an error response.
Unknown - Either a ping has not yet been done or the TCP/IP Services interface is unavailable.
System Action:
An alert is created.
User Action:
If a Timeout status was returned, check the status of the device, using the Check action in the IP Node Monitor or Alert Monitor. If the device appears to be available, consider increasing the wait period of the ping.
In an Unknown status was returned, the TCP/IP Socket Interface may be unavailable. Ensure that TCPIP is started on this region. Consider setting up a custom event detector to monitor the Socket Interface.
Error status indicates that the TCP/IP Socket is up, but an error, other than Timeout, occurred while doing a Ping to this specific device. Possible causes including storage problems, security restrictions, and other connectivity problems.
Check the status of your TCP/IP stack, and examine the TCP/IP stack job output for messages.
An Error status may be accompanied by an error message. Check the Activity Log for messages relating to PING activity, in particular, message 'N3D692 PING/TRACEROUTE raw socket send failure'. If present, this message will indicate the specific failing return code, reason code, socket error number, and any vendor-specific error information.
Examine the error codes to determine the cause of the PING failure. For feedback and socket error codes, see Appendix F, '&SOCKET Verbs', of the Network Control Language Reference.
Reason:
During monitor initialization, the Monitor Group P1 associated with IP NODE P2 was not found in the RAMDB.
System Action:
Initialization continues with IP NODE P2 status set to Unknown .
User Action:
Define a Monitor Group with a name P1 .
Reason:
An alert has been created by the IP Node Monitor function. The monitor attempted to traceroute node with IP address P3 . P1 is the number of Hops it took which exceeds threshold specified as P2 .
System Action:
An alert is created.
User Action:
Check the status of the node, possibly by issuing the CH=Check action for the node in the IP Node Monitor.
Reason:
An attempt to view performance data on IP node P1 was not successful because the node is not currently being monitored in the IP Node Monitor.
System Action:
The request is ignored.
User Action:
Add the node to the IP Node Monitor /IPNODE via the ADD command.
Reason:
A change in the definition of IP Node Monitor group P1 will take effect on the next sampling interval for P2 resources.
System Action:
None.
User Action:
Reason:
A change in a monitoring attribute for IP Node Monitor group P1 will take effect on the sampling interval for P2 resource(s). An RMDBMS00 message describes the attribute that was recently updated.
System Action:
None.
User Action:
Reason:
The field P1 must contain a time value in the range P2 to P3 entered in the format MM.SS.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
Intensive Monitoring Mode is already active for IP node attribute P1 with sampling set to complete at time P2 .
System Action:
On completion of Intensive Monitoring Mode, the IP node attribute rate will be set back to the group attribute rate.
User Action:
You may issue an IMR command to Reset, and then issue the IMM command. The IMR command will reset the IP node to the group attribute rate. Updating the group attribute rate in the IP Node Monitor Group List will also reset the IP node attribute rate.
Reason:
Intensive Monitoring Mode is already active for IP node attribute P1 with sampling set to complete at time P2 . Intensive Monitoring can still be set for the selected attribute; however, it will be reset once Intensive Monitoring for the reported attribute P1 has completed.
System Action:
On completion of Intensive Monitoring Mode, the IP node attribute rate will be set back to the group attribute rate.
User Action:
You may issue an IMR command to Reset, and then issue the IMM command. The IMR command will reset the IP node to the group attribute rate. Updating the group attribute rate in the IP Node Monitor Group List will also reset the IP node attribute rate.
Reason:
Intensive Monitoring Mode is being attempted on a Node with no Monitoring Activities defined. This is due to the Monitoring Activity Operational Override being inactive, or because no Monitoring Activities have been defined to the Monitoring Group.
System Action:
None.
User Action:
Check the IP Node Monitoring Activity Operational Override via the S command. If this is inactive, set it to active and reissue IMM command. If no Monitoring Activities have been defined to the Monitoring Group, update the Monitoring Group via shortcut /IPMONG
Otherwise, notify your Systems Administrator.
Reason:
You attempted to perform a TCPaccess related function on stack P1 which is not configured for managing that TCP/IP stack type.
System Action:
The request is rejected.
User Action:
Make sure you have specified the correct Link and/or Stack name, as you may be pointing to a system that is managing a different TCP/IP stack.
Reason:
You attempted to perform a function not supported by TCPaccess on stack
P1 which is configured for TCPaccess management.
System Action:
The request is rejected.
User Action:
Make sure you have specified the correct Link and/or Stack name, as you may be pointing to a system that is managing a different TCP/IP stack.
Reason:
This message explains what will happen if you press the action key (F6). The displayed data (along with any updates you make) will be saved to dataset P1 overwriting any existing data. The saved statements will be executed immediately, via a VARY TCPIP,CMD=OBEYFILE issued to the stack.
System Action:
None
User Action:
Update the statements if required. Use the F6 key to save and action the change or F12 to cancel.
Reason:
You attempted to browse the P1 configuration data set for stack P2 , but the name of the data set is not available in the stack resource definition.
System Action:
The request is rejected.
User Action:
Update the stack definition for P2 with the name of the configuration data set.
Reason:
An error occured whilst processing an APPC verb.
P1 is the APPC verb that was issued
P2 is the return code set by the APPC verb
P3 is the feedback code set by the APPC verb
P4 is the qualified remote LU name
P5 is the APPC conversation state
System Action:
Request Fails.
User Action:
Check the status of the remote LU and check that TCP/IP Services has been initialized on the remote system.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An invalid action was received from the client in a request. The action specified in the request was P1 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The file identified by P1 could not be opened for input as the file is either a partitioned dataset (PDS) with no member name specified or is a VSAM dataset.
System Action:
Request is rejected.
User Action:
Check that you have specified the correct dataset name.
Reason:
TCP/IP Services sucessfully read P1 lines in the dataset P2 .
System Action:
None.
User Action:
None.
Reason:
TCP/IP Services sucessfully saved P1 lines in the dataset P2 .
System Action:
None.
User Action:
None.
Reason:
The member name P1 already exists in the nominated dataset name but REPLACE=NO was specified.
System Action:
The field is highlighted as an error.
User Action:
Either specify REPLACE=YES or change the member name.
Reason:
TCP/IP Services sucessfully opened the dataset P1 .
System Action:
None.
User Action:
None.
Reason:
The device links diagram display encountered an internal error while processing a vartable.
P1 was the vartable action being attempted
P2 was the feedback code
P3 was the key (if relevant)
System Action:
The diagram is not displayed
User Action:
Determine the cause of the error and retry.
Reason:
You requested an action on an object displayed on a device links diagram. The requested action is not supported by that object.
P1 is the name of the object.
System Action:
None.
User Action:
Correct the action request, or retry on another object.
Reason:
An MDO assignment failed. The MDORC was P1 the MDOFDBK value was P2
System Action:
The action terminates.
User Action:
Refer to the NCL user reference for details of the codes.
Reason:
There are no actions that can be performed on your selection.
System Action:
None.
User Action:
None.
Reason:
The Enterprise Extender XCA Major Node was not found. Some possible causes are:
- No XCA Major Node is defined with MEDIUM=HPRIP
- The XCA Major Node is not activated
- There is a problem with issuing VTAM display commands
System Action:
None
User Action:
If the Enterprise Extender XCA Major Node is active use the following command to diagnose the problem. $IPEE01H TRACE=YES CLASS=EE ATTR=NODENAME ACTION=FIND
Reason:
An unexpected response was received from a VTAM command used to diagnose Enterprise Extender.
System Action:
The requested action does not complete successfully.
User Action:
Use the following commands to diagnose the problem. $IPEE01H TRACE=YES CLASS=EE ATTR=NODENAME ACTION=FIND $IPEE01H TRACE=YES CLASS=EE ATTR=SESSION ACTION=GET NAME=xcaNodeName
Reason:
The supplied XCA major node name is not a valid Enterprise Extender node. Possible causes are that the XCA major node name is not:
- The name of an active XCA Major Node
- Defined with MEDIUM=HPRIP
System Action:
The requested action does not complete successfully.
User Action:
Ensure that the supplied XCA Major Node name is correct and that the node has been activated before using the Enterprise Extender diagnosis commands.
Reason:
A request to display Enterprise Extender information failed because either the XCA major node is not active or the wrong node name was supplied.
System Action:
The request fails.
User Action:
If Enterprise Extender is active, determine the correct XCA major node name and retry.
Reason:
A request for information about the Enterprise Extender port failed because the started task P1 for the TCP/IP stack is not active.
System Action:
The request fails.
User Action:
Verify that the started task is active, and retry the request.
Reason:
The Enterprise Extender XCA Major Node has been activated but there are no active lines.
System Action:
None
User Action:
None
Reason:
Filter criteria such as line name, line status or remote IP address was supplied on a request to display Enterprise Extender session information. No sessions matched the criteria.
System Action:
None
User Action:
None
Reason:
This is an internal failure.
An attempt to retrieve UDP port details has failed. P1 is the return code, and P2 is the feedback code.
For RC=12, some possible feedback code values are as follows:
1 indicates that a NEXT request was rejected with no outstanding GET request.
2 indicates that failure occurred while preparing an MDO.
3 indicates that failure occurred while assigning an MDO.
4 indicates that failure occurred while connecting to a map.
5 indicates that the subtask processing this request abended.
6 indicates that this region is not authorized.
7 indicates that loading of the API module EZBNMIFR failed during initialization.
8 indicates that the interface was disabled due to excessive number of abends.
10 indicates that region shutdown is in progress.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt to retrieve UDP connection details from IBM's EZBNMIFR API failed. P1 is the return code (errno), and P2 is the reason code (errnojr).
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
You attempted an EE action on the P1 stack, but the stack is not active.
System Action:
The action fails.
User Action:
Check the status of the stack.
If the stack is active, check that the SOLVE SSI PAEESTACK parameter is specified correctly. PAEESTACK must match the JOBNAME of the stack that is providing EE services.
Reason:
You attempted an EE action for stack P1 but the stack is not the EE stack.
System Action:
The action fails.
User Action:
Supply the correct stackname.
Reason:
Your product does not support the TCP/IP EE Management functions.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
The Packet Analyzer has determined that IPSec is used on this system. If any EE traffic is protected by IPSec, that traffic is not included in these statistics.
System Action:
None.
User Action:
None.
Reason:
A request to update Enterprise Extender performance monitoring was successful but the monitoring could not be restarted. A message indicating the reason for the failure was written to the activity log.
System Action:
The monitoring definition is updated but current monitoring does not reflect the changes made.
User Action:
Review the message preceding this message in the activity log to determine the cause of the problem.
Reason:
The VTAM level indicated by P1 does not support the requested function. For an EE Connectivity Test, the DISPLAY NET,EEDIAG,TEST=YES is not supported by VTAM levels less than z/OS 1.8.
System Action:
None.
User Action:
None.
Reason:
VTAM message IST1203I was returned for a D EEDIAG,TEST=YES,ID= P1 . The PU is no longer active.
System Action:
None.
User Action:
Press F3 (Exit) to return to the Enterprise Extender Management panel and press F6 (Refresh) to refresh the display.
Reason:
The Packet Analyzer has determined that IPSec is used on this system. The content of the IPSec traffic cannot be determined. If the content includes EE data, the protected EE traffic is not included in these statistics.
System Action:
None.
User Action:
None.
Reason:
The EE traffic category P1 did not have any items for which statistics were collected. This may indicate that no EE activity has been detected or that the TCP/IP stack identified to the Packet Analyzer SSI is not correct and no statistics for EE are being gathered.
System Action:
No items are display in the EE traffic explorer list.
User Action:
If the EE stack has not been correctly specified in the SSI then determine the correct stack that is enabled for EE traffic and specify it in the SSI's startup parameters.
Reason:
The Packet Analyzer has determined that IPSec is used by this stack. The content of the IPSec traffic cannot be determined. If the content includes EE data, the protected EE traffic is not included in these statistics.
System Action:
None.
User Action:
None.
Reason:
The EEDIAG,TEST=YES detected interfaces for which Enterprise Extender connectivity failed.
System Action:
None.
User Action:
Review the Connectivity Test results and determine if the unsuccessful interfaces are an indication of a network error condition.
Reason:
The EEDIAG,TEST=YES failed for all interfaces with a route to the destination host.
System Action:
None.
User Action:
Review the Connectivity Test results to determine the cause of the failure.
For a time-out condition where all intermediate hops have responded, take the following actions:
For a time-out condition where not all intermediate hops responded or where some ports have responded OK, review the firewall configuration of the last successful hop.
Reason:
There are no actions that can be performed on your selection. There is no remote host associated with the selected line.
System Action:
The selection in error is highlighted.
User Action:
Blank the highlighted selection.
Reason:
The EEDIAG,TEST=YES command was rejected by VTAM with an IST2142I message indicating that a test for the same local and remote IP address combination is currently in progress.
System Action:
The test request is rejected.
User Action:
Retry the request at a later time.
Press F4 (EEDiag) to determine if VTAM has test requests in progress.
Reason:
The EEDIAG,TEST=YES command was specified using NAME= P1 and this PU is not active.
System Action:
The test request is rejected.
User Action:
Press F6 to retry the request using the IP address of the remote host.
On return to the EE Major Node Summary press F6 to refresh the display. Inactive PUs are displayed in blue.
Reason:
A request to perform an EE connectivity test cannot proceed because there is no remote host (CP) currently connected to EE.
System Action:
None.
User Action:
To perform a connectivity test to a specific remote host, enter the host name or address in the 'Remote Host Name/Addr' field on the /EE menu.
To check the overall status of EE, display the EE XCA Major Node Summary (/EEXCA).
Reason:
The EEDIAG,TEST=YES failed for all interfaces with a route to the destination host. However, Packet Analyzer has seen IPSec traffic for the remote address. If EE traffic is IPSec-protected, EEDIAG TEST=YES does not work.
System Action:
None.
User Action:
If the link is IPSec-protected, the connectivity test is not useful. Use the /IPSEC menu options to check on the status of the tunnel used by the EE Link.
If IPSec is not in use, review the Connectivity Test results to determine the cause of the failure.
For a time-out condition where all intermediate hops have responded, take the following actions:
For a time-out condition where not all intermediate hops responded or where some ports have responded OK, review the firewall configuration of the last successful hop.
Reason:
An attempt to display traffic statistics for the p1 address space failed. The Packet Analyzer has seen no packets to or from the monitored ports for this resource in the last hour.
System Action:
None.
User Action:
Determine what ports are being monitored for this address space. From /IPMON, enter UM against the address space name to view the values in the TCP Port(s), UDP Port(s), and Associated STACK Jobname fields. Update the values if necessary, and retry the operation.
If the resource definition is correct, check the status of the address space.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are only available when PALEVEL is FULL.
System Action:
No packet statistics are displayed.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
A Packet Analyzer scan must complete within 60 seconds so that record data is consistent. The current scan exceeded 60 seconds and has been terminated.
System Action:
The scan is terminated prior to completion.
User Action:
This message may indicate that the system is very busy, and that the requesting region or SSI region is not running with a sufficiently high priority to process requests in a timely manner. Retry the action when the system is less busy. If this condition persists, contact Technical Support.
Reason:
An attempt to display traffic statistics for resource P1 failed. The ports for P1 could not be determined from stack P2 (which is the associated stack named in the P1 definition).
System Action:
None.
User Action:
Check that status of stack P2 . The stack may be inactive or not processing onetstat requests.
Reason:
A Packet Analyzer scan to generate IP summary data has returned an excessive amount of data. Processing has been aborted so as not to use excessive system resources.
System Action:
Processing terminates and no summary data is available. Processing is retried on demand after a delay of at least four minutes.
User Action:
This message may occur on a busy system, and will usually self-correct. If this condition persists, contact Technical Support.
Reason:
An attempt to display P1 traffic statistics failed. No P1 statistics were returned from the Packet Analyzer.
System Action:
None.
User Action:
Check the status of the stack.
Reason:
An attempt to display EE traffic statistics failed. No EE statistics were returned from the Packet Analyzer. However, the packet analyzer has seen IPSec traffic on this stack. This may include EE traffic. No IPSec-protected traffic is included in the statistics.
System Action:
None.
User Action:
If IPSEC is being used for EE traffic, this option is not useful.
Reason:
The Packet Analyzer has determined that IPSec is used by this stack. The content of the IPSec traffic cannot be determined. If the content includes EE data, the protected EE traffic is not included in these statistics.
System Action:
None.
User Action:
None.
Reason:
A request was made to the Packet Analyzer record list to display a record type that is not supported currently. The following record types are supported currently:
System Action:
The Packet Analyzer record list is not displayed.
User Action:
Contact CA Support.
Reason:
The expression provided on the FILTER command is invalid.
For TCP applications and business applications, the filter must be either a full application name or a partial name ending in an * (indicating a generic match).
For remote IP addresses, the filter must be an IP address mask. For example: 10 or 10.*.*.*, 10.20 or 10.20.*.*, 10.20.*.30, and so on.
For TCP ports, the filter must be either an individual port number or a port range, with a space, a hyphen, or a colon separating the ports. For example: 80, 80 90, 80-90, 80:90, and so on.
System Action:
The filter is not applied.
User Action:
Reissue the filter command, correctly specifying your filter.
Reason:
The LIMIT command was issued, and the limit value has been set to the value shown in the message. If the value requested is less than 1, the limit is set to 1. If the value requested is greater than the Packet Analyzer Maximum List Size (as set in the DISPLAYS parameter group), the limit is set to the Packet Analyzer Maximum List Size. If no value was specified, the limit is set to the Packet Analyzer Initial List Size (as set in the DISPLAYS parameter group). Otherwise, the limit is set to the value specified.
System Action:
The limit is set to the value shown in the message.
User Action:
None.
Reason:
A connections list was requested for the selected item but there are no active connections for the selected item.
System Action:
The connections list is not displayed.
User Action:
None.
Reason:
A port list was requested for p1 but there are no ports in use for this item.
System Action:
The port list is not displayed.
User Action:
None.
Reason:
A request has been sent to the Packet Analyzer for a list of records, but no records were found matching the scan criteria on the request.
System Action:
The request fails.
User Action:
If the Packet Analyzer has been restarted recently, wait a while and reissue this command. You can also try removing filtering limitations such as stack name.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are available only when PALEVEL is FULL.
System Action:
No statistics are included on the display.
User Action:
Check why the SSI is not running with PALEVEL=FULL.
The PALEVEL setting can be altered using the SSI command, PACTL. SSI commands can be entered from a region using the SSISEND command, for example:
SSISEND PACTL PALEVEL=FULL
Reason:
The received SMF record is of an unexpected record type, P1 , or structure. Supported SMF record types are 119 and 130.
System Action:
The record is ignored.
User Action:
If the situation persists, contact Technical Support.
Reason:
An FTP logon failed for a user:
P1 is the user ID of the failed login attempt.
P2 is the IP address of the connection.
P3 is the FTP task name of the FTP server.
P4 is the Login Failure code:
01 - Password invalid
02 - Password expired
03 - User ID has been revoked
04 - User does not have server access
05 - FTPCHKPWD User exit rejected login
06 - Excessive bad passwords
07 - Group ID process failed
08 - User ID is unknown
System Action:
None
User Action:
None
Reason:
An FTP server action completed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended
P2 is the user performing the action
P3 is the IP address of the connection
P4 is the name of the dataset affected
P5 is the number of bytes transmitted
P6 is the number of seconds taken by the transaction
P7 is the number of bytes per second transmitted in the transaction
P8 is the task name of the FTP server.
System Action:
None.
User Action:
None.
Reason:
An FTP server delete completed.
P1 is the user performing the delete
P2 is the IP address of the connection
P3 is the name of the dataset deleted
P4 is the task name of the FTP server
System Action:
None.
User Action:
None.
Reason:
An FTP server rename completed.
P1 is the user performing the rename
P2 is the IP address of the connection
P3 is the old name of the dataset
P4 is the new name of the dataset
P5 is the task name of the FTP server
System Action:
None.
User Action:
None.
Reason:
An FTP server action has completed but the action failed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended
P2 is the user performing the action
P3 is the IP address of the connection
P4 is the last reply code. These are documented in RFC959.
P5 is the name of the dataset affected
P6 is the number of bytes transmitted
P7 is the number of seconds taken by the transaction
P8 is the task name of the FTP server.
System Action:
None.
User Action:
None.
Reason:
An FTP server delete has completed but the delete failed.
P1 is the user performing the delete
P2 is the IP address of the connection
P3 is the last reply code. These are documented in RFC959.
P4 is the name of the dataset deleted
P5 is the task name of the FTP server
System Action:
None.
User Action:
None.
Reason:
An FTP server rename completed but the rename failed.
P1 is the user performing the rename
P2 is the IP address of the connection
P3 is the Last reply code. These are documented in RFC959
P4 is the old name of the dataset
P5 is the new name of the dataset
P6 is the task name of the FTP server
System Action:
None.
User Action:
None.
Reason:
An FTP client action completed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended.
P2 is the user performing the action.
P3 is the IP address of the connection.
P4 is the name of the dataset affected.
P5 is the number of bytes transmitted.
P6 is the number of seconds taken by the transaction.
P7 is the number of bytes per second transmitted in the transaction.
System Action:
None
User Action:
None
Reason:
An FTP client action has completed but the action failed.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended.
P2 is the user performing the action.
P3 is the IP address of the connection.
P4 is the last reply code. Refer to the note below.
P5 is the name of the dataset affected.
P6 is the number of bytes transmitted.
P7 is the number of seconds taken by the transaction.
The last reply code ( P4 ) is the value set in bytes 28-31 of the FTP Client SMF record, as described in the appendices to the OS/390 Communications Server IP Configuration manual. A value of 0 or 2nn represents a successful transmission (and will cause message IPFM2123 to be issued rather than this message). Other values are as set by the TCP/IP stack.
System Action:
None
User Action:
None
Reason:
An FTP server action started.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended
P2 is the user performing the action.
P3 is the IP address of the connection.
P4 is the name of the dataset affected.
P5 is the task name of the FTP server.
System Action:
None.
User Action:
None.
Reason:
An FTP client action started.
P1 is the action performed: RETR=retrieved, STOR=stored, APPE=appended.
P2 is the user performing the action.
P3 is the IP address of the connection.
P4 is the name of the dataset affected.
System Action:
None.
User Action:
None.
Reason:
The message displays an FTP transfer event trace record. P1 is the trace ID and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An incomplete FTP event has been received from the FTP Post Processing Exit (FTPOSTPR). The event status is as follows:
8 - One or more fields truncated.
16 - One or more fields missing.
System Action:
A hexadecimal dump of the event is written to the activity log. The event is discarded.
User Action:
Contact Technical Support.
Reason:
This message displays an FTP transfer event trace record. P1 is the trace ID and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The field must contain either zero or a positive integer.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value and retry.
Reason:
An invalid value P1 was specified as a member name/mask.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the member name and retry. Valid member mask characters are:
'*' - match any character
'?' - match one character
Reason:
No data was entered in a mandatory field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the field.
Reason:
The FTP connection diagram display utility encountered an internal error while processing a vartable.
P1 was the vartable action being attempted
P2 was the feedback code
P3 was the key (if relevant)
System Action:
The diagram is not displayed
User Action:
Determine the cause of the error and retry.
Reason:
You requested an action on an object displayed on an FTP connection diagram. The requested action is not supported by that object.
P1 is the name of the object.
System Action:
None
User Action:
Correct the action request, or retry on another object.
Reason:
An MDO assignment failed. The MDORC was P1 the MDOFDBK value was P2
System Action:
The action terminates.
User Action:
Refer to the NCL User Reference for details of the codes.
Reason:
User P3 has issued a command to drop the connection to local port P2 from the P1 IP connection.
System Action:
None.
User Action:
None.
Reason:
You requested a CICS SocketMgmt action on an object that is not a CICS region. The requested action is not supported by that object.
P1 is the name of the object.
System Action:
None
User Action:
Correct the action request, or retry on another object.
Reason:
The procedure which collects data for the display has abended. No connection data is available.
System Action:
No data is collected. This message, plus messages IPGP0603 and IPGP0604 are written to the Activity Log detailing the error.
User Action:
Contact your product supplier.
Reason:
This message follows IPGP0602, issued as a result of a procedure abending, supplying the error text ( P1 ). The message is followed by IPGP0604 which supplies additional details.
System Action:
Refer to message IPGP0602.
User Action:
Refer to message IPGP0602.
Reason:
This message follows IPGP0602 and IPGP0603, issued as a result of a procedure abending, supplying the specific error details:
LINE= P1 - the line number in the source code
COND= P2 - the error condition
STMT= P3 - the statement name (verb name)
KEYWORD= P4 - the keyword name (operand name)
NAME= P5 - the name specification
VAR= P6 - the variable name causing the error
System Action:
Refer to message IPGP0602.
User Action:
Refer to message IPGP0602.
Reason:
An attempt to list connections using a remote backlevel CA NetMaster region failed because the remote region does not support the selection criteria specified.
The remote region is linked to this region in Migration Mode. This type of linkage is used during migration to a new release level.
System Action:
Processing terminates.
User Action:
Upgrade the remote region to the latest release level.
Reason:
An attempt to list connections for a stack failed because the stack is TCPaccess. Criteria P1 only applies to IBM stacks.
System Action:
Processing terminates.
User Action:
Change the selection criteria to remove criteria P1.
Reason:
An attempt to produce a P1 list for a stack failed because the stack is a CA TCPaccess CS stack. P1 lists are supported for IBM stacks only.
System Action:
Processing terminates.
User Action:
None.
Reason:
The procedure which collects data for the display has created a Mapped Data Object (MDO) that exceeds the system limit of 32K.
System Action:
No data is collected.
User Action:
This is an internal error. Contact your product supplier.
Reason:
You attempted a Ping or TraceRoute action against an IPv6 address on region P1. The action failed because the sockets API on region P1 supports IPv4 addresses only.
System Action:
The request is rejected.
User Action:
Check the SOCKETS parameter group (/PARMS) on region P1. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
You attempted a Ping or TraceRoute action, specifying a source address. The action failed because the address to ping or traceroute is not the same IP version as the Source Address.
System Action:
The request is rejected.
User Action:
Correct the request and retry.
Reason:
The address identified by P1 was not available on the local host. This may have been because a network broadcast address was given.
System Action:
None.
User Action:
Correct the entry and retry the operation. If the address is valid, contact your local support representative.
Reason:
The TCP/IP socket interface did not receive a normal response to the PING from the host identified by P1 .
This error normally occurs if the host specified is either incorrect or unreachable. However it may also occur if the packet size requested exceeds the maximum transmission unit (MTU) size for the first hop.
System Action:
An error message is returned to the user.
User Action:
Check the host name is a valid host name and retry. If you have specified a packet size, try reducing the size. Check also that the route to the host is available and the host is active. A TRACERTE command may be useful in determining the point where routing fails.
Reason:
The TCP/IP socket interface procedure $IPGP12H failed because a TCP/IP socket operation failed. The Return Code from the &SOCKET call is P1 , the Feedback Code is P2 and the Socket Error is P3 .
P4 is the vendor-specific error information. The failing socket request was P5 .
System Action:
Procedure $IPGP12H terminates. Control is returned to the NCL procedure which executed $IPGP12H.
User Action:
Contact your System Administrator.
Reason:
An MDO error occurred. The MDO is identified by P1 the map name by P2 the MDO return code by P3 and the feedback code is P4 .
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action failed because the request was denied.
System Action:
None.
User Action:
Communications Server Systems: Ensure the user ID associated with this address space is defined as a superuser (UID(0)) to UNIX system services.
Reason:
The TCP/IP socket interface procedure $IPGP12H failed because a required parameter was omitted from the call to $IPGP12H in the command
P1 .
System Action:
The request is rejected and procedure $IPGP12H terminates. Control is returned to the NCL procedure which executed $IPGP12H.
User Action:
Contact your System Administrator.
Reason:
An &ASSIGN operation failed because the ASN1 map identified by P1 could not be found.
System Action:
None.
User Action:
Contact your System Administrator.
Reason:
A call was made to perform a PING on the host identified by P1 with the IP address P2 . The value P3 is a compound of the minimum, average and maximum values delimited by the '/' character if the PING request was successful, else the value NO RESPONSE is returned.
System Action:
None.
User Action:
The message is informational.
Reason:
A PING was requested for a host. The number of packets sent is P1 . The number of packets received is P2 . The overall packet loss is indicated by P3 .
System Action:
None.
User Action:
The message is informational.
Reason:
A LOOKUP was requested for hostname P1 which has IP Address P2 .
System Action:
None.
User Action:
The message is informational.
Reason:
A PING has been requested and the Minumum, Average and Maximum trip times in milliseconds are returned concatenated with a space between the values.
System Action:
None.
User Action:
The message is informational.
Reason:
A PING request has been made which has returned values of P1 bytes sent from host P2 which took P4 milliseconds. The sequence number is P3 .
System Action:
None.
User Action:
The message is informational.
Reason:
A call was made to perform a name lookup on the host identified by P1 . No entry could be found for this host.
System Action:
None.
User Action:
None.
Reason:
A PING request has timed out for host P1 . The sequence number is P2 .
System Action:
None.
User Action:
The message is informational.
Reason:
The message forms part of the returned responses from the TRACEROUTE command.
System Action:
None.
User Action:
None.
Reason:
The message forms part of the returned responses from the TRACEROUTE command.
System Action:
None.
User Action:
None.
Reason:
The message forms part of the returned responses from the TRACEROUTE command.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the returned responses from the TRACEROUTE command and provides column headings for subsequent IPGP1225 messages, each of which represent one hop along the path to the target host.
The number of columns for Round Trip Time is determined by the value specified for the keyword parameter COUNT (default:3). Round trip times appear in milliseconds.
The Notes column provides the following information about the monitored status of the hop address:
MON - The address is defined to the IP Node Monitor but there are no outstanding alerts.
ALERT - The address is defined to the IP Node Monitor and has one or more outstanding alerts.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the returned responses from the TRACEROUTE command and provides column headings for subsequent IPGP1225 messages, each of which represent one hop on the path to the target host.
The number of columns for Round Trip Time is determined by the value specified for the keyword parameter COUNT (default:3). Round trip times appear in milliseconds.
The Notes column provides the following information about the monitored status of the hop address:
MON - The address is defined to the IP Node Monitor but there are no outstanding alerts.
ALERT - The address is defined to the IP Node Monitor and has one or more outstanding alerts.
System Action:
None.
User Action:
None.
Reason:
The message forms part of the returned responses from the TRACEROUTE command. Refer to message IPGP1223 for a description of the fields displayed.
System Action:
None.
User Action:
None.
Reason:
A call was made to perform a PING on the host identified by P1 . No entry could be found for this host.
System Action:
None.
User Action:
None.
Reason:
A call was made to perform a TRACEROUTE on host identified in message IPGP1220 or IPGP1221 resulted in the error indicated by P1.
System Action:
None.
User Action:
None.
Reason:
No destination address was specified for the socket operation.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
The socket operation failed because the destination network was unreachable.
System Action:
None.
User Action:
Determine the cause and retry the operation.
Reason:
The socket operation failed because the destination host was down.
System Action:
None.
User Action:
Determine the cause and retry the operation.
Reason:
The socket operation failed because the destination host was unreachable.
System Action:
None.
User Action:
Determine the cause and retry the operation.
Reason:
The socket operation failed because the TCP/IP stack subtask abended.
System Action:
None.
User Action:
Contact your System Administrator.
Reason:
The socket operation failed because the TCP/IP sockets interface is not available.
System Action:
None.
User Action:
Contact your region administrator and ensure that the SOCKETS parameter group successfully activated the TCP/IP Interface. The following message should appear in the log:
N3B201 TCPIP START COMPLETE
Note: If the failing request is for an Enterprise Extender connection and the SOCKETS interface is not using the same stack as VTAM, you need to issue a TCPIP START with PRI=NO to define a secondary SOCKETS interface that is using the same stack as VTAM.
Reason:
An asynchronous request using APPC has been terminated due to a state error.
System Action:
The request terminates.
User Action:
Report the error to your product support representative.
Reason:
The IP address or remote node name specified for the PING operation is invalid. PING is only available to individual IP hosts. This error will occur if, for example, you specify the IP address of a network.
P1 is the vendor-specific error code.
System Action:
The PING operation cannot be performed.
User Action:
Correct the IP address or node name and retry the Ping.
Reason:
You tried to perform a name lookup specifying ADDRTYPE=6. This is not valid on system P1 because it is using IBM's DNR and it does not have IPv6 sockets support enabled.
System Action:
The request is rejected.
User Action:
Remove the ADDRTYPE=6 operand. Alternatively, use the /PARMS shortcut on region P1 and review the values in the SOCKETS Customizer parameter group.
Reason:
The socket operation failed because the sockets interface does not support an interface name specification.
Use of the interface name requires running the USS sockets interface.
System Action:
None.
User Action:
Blank out the interface name specification, and retry the operation.
If you want to use the interface name, contact your region administrator to specify USS as the type in the SOCKETS parameter group.
Reason:
The socket operation failed because the specified interface name is not a physical interface such as an OSA. VIPA or internal interfaces cannot be specified for the operation.
System Action:
None.
User Action:
Correct the interface name to specify a physical interface.
Reason:
The socket operation failed because the specified interface name is not a physical interface that is defined to the stack.
System Action:
None.
User Action:
Correct the interface name to specify a physical interface for the stack.
Reason:
This message indicates the end of returned messages.
System Action:
None.
User Action:
None.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
An attempt to extract the Channel Path ID for device P1 has failed. The reason is provided in P2. Possible reasons for failure are: DEVINFO RC=aa bb aa is the DEVINFO verb return code, bb is the FDBK. DEVINFO returned multiple CHPIDs more than one CHPID value was returned for the device.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
A Packet Trace request has been issued using a VARY TCPIP command. The command operands used were P1.
System Action:
None.
User Action:
None.
Reason:
A Packet Trace request has been issued using a VARY TCPIP command. The command operands used were P1 .
System Action:
None.
User Action:
None.
Reason:
A request to start a TCP/IP device was executed. The device is P1 .
System Action:
None
User Action:
None
Reason:
A request to stop a TCP/IP device was executed. The device is P1 .
System Action:
None
User Action:
None
Reason:
The port mnemonic identified by P1 is not known.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
A VARY TCPIP command was issued. The messages returned by TCPIP indicate that an error was detected.
System Action:
The messages returned by the VARY TCPIP command are written to the activity log.
User Action:
Refer to the activity log for the messages returned.
Reason:
A VARY TCPIP command was issued to process the request. No errors were detected.
System Action:
The VARY TCPIP messages are written to the Activity Log.
User Action:
None.
Reason:
A list of TCP/IP entities was requested, but none are defined to the system. P1 is the type of entity requested, one of:
TCP/IP Stacks - IBM and TCPaccess stacks
Telnet Servers - IBM and TCPaccess stacks, channel cards, routers
Links` - Region links, channel cards, routers
System Action:
No list is displayed.
User Action:
None.
Reason:
A request to create a new monitor group has completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to update a monitor group completed successfully.
System Action:
None.
User Action:
Reason:
The indicated procedure ( P1 ) has abended whilst running on the region indicated by the INMC link name ( P2 ).
System Action:
This message, plus messages IPGP9902 and IPGP9903, are written to the Activity Log that details the error.
Note: This message is displayed on the panel of the local region domain. However the problem may have occurred when the procedure was executed on a remote region. The entire group of messages are written to the Activity Log on the system where the procedure was actually executed as indicated in the message ( P2 ).
User Action:
Contact your product supplier.
Reason:
This message follows IPGP9901 that was issued as a result of a procedure abending. This message supplies the error text ( P1 ) and is followed by IPGP9903 which supplies additional details.
System Action:
Refer to message IPGP9901.
User Action:
Refer to message IPGP9901.
Reason:
This message follows IPGP9901 and IPGP9902 that were issued as a result of a procedure abending. This message supplies the specific error details:
LINE= P1 - The line number in the source code
COND= P2 - The error condition
STMT= P3 - The statement name (verb name)
KEYWORD= P4 - The keyword name (operand name)
NAME= P5 - The name specification
VAR= P6 - The variable name causing the error
System Action:
Refer to message IPGP9901.
User Action:
Refer to message IPGP9901.
Reason:
An attempt to connect to one of the ASN1 maps required for the CLAW Subchannel (ESCON) support has failed.
System Action:
The CLAW Subchannel List is unavailable. Attributes associated with CLAW Subchannel data are not included in the CMCC Resource List.
User Action:
Check that all maintenance regarding CLAW Subchannel (ESCON) has been installed correctly. Ensure that APARs relating to ASN1 maps have been applied and that the ASN1 maps have been compiled as instructed in the APAR(s) comments.
Reason:
This generic trace message is produced by IP Growth Tracker.
System Action:
Other trace messages can be written to the activity log as IP Growth Tracker processing continues.
User Action:
None.
Reason:
The IP Growth Tracker was attempting to collect statistics from the Packet Analyzer, but no Packet Analyzer record was returned. This may be due to the Packet Analyzer's SSI region not running.
System Action:
The IP Growth Tracker terminates the statistics collection process.
User Action:
Check to see whether the Packet Analyzer SSI region is running and statistics collection is enabled.
Reason:
The IP Growth Tracker statistics collection process has started.
System Action:
The IP Growth Tracker continues to collect statistics.
User Action:
None.
Reason:
The IP Growth Tracker statistics collection process has ended.
System Action:
The IP Growth Tracker has finished collecting statistics.
User Action:
None.
Reason:
An IP Growth Tracker shutdown listener was started; however, a listener is already running.
System Action:
The second shutdown listener terminates.
User Action:
Do not start an IP Growth Tracker shutdown listener if one is already running.
Reason:
The IP Growth Tracker statistics collector could not access the Packet Analyzer records indicated by p1, such as:
STK - Stack records
IPR - IP protocol records
System Action:
The IP Growth Tracker continues processing, but statistics is not calculated for the indicated records.
User Action:
Investigate whether there are any problems with the Packet Analyzer or SOLVE SSI that is causing record access to fail.
Reason:
The IP Growth Tracker web page was requested with criteria that resulted in no records being returned.
System Action:
The IP Growth Tracker web page displays this message.
User Action:
If a day-based timeframe was requested then no day records were found in the database matching the specified range. This may be caused by the IP Growth Tracker never having collected statistics, or the day statistics are too recent for the specified timeframe. Check again in 24 hours.
If a month-based timeframe was requested then no month records were found in the database. This is because the IP Growth Tracker has never rolled up day records into month records. Check again in a month's time.
If a year-based timeframe was requested then no year records were found in the database. This is because the IP Growth Tracker has never rolled up month records into year records. Check again next year.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are only available when PALEVEL is FULL.
System Action:
No packet statistics are displayed.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, we recommend that you always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions are not available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
The charts displayed on the IP Growth Tracker web page are Java applets and therefore require a Java Runtime Environment (JRE) in order to display their data. This message is displayed after 15 seconds if no JRE has been detected.
System Action:
The IP Growth Tracker charts are not displayed.
User Action:
If a Java Runtime Environment is already installed for your browser then click Refresh to reload the web page. A delay while loading may have prevented the JRE from initializing within 15 seconds.
If you are using a 32-bit browser then an auto-download and install of the JRE may have been initiated. Reload the page once the installation has completed.
If you are using a 64-bit browser then you will need to install the JRE manually. Go to http://java.sun.com and navigate to downloads where you can choose an appropriate JRE to install.
Reason:
A request to sample interface statistics failed because the IF-MIB table contained no entries. P1 is the name of the TCP/IP stack.
System Action:
Sampling for the period is not performed.
User Action:
Check the contents of the MIB table for the stack. This can be done by using the 'MIB' command against the stack, selecting IF-MIB, and reviewing the ifTable and ifXtable contents.
Reason:
A request to sample interface statistics for stack P1 failed because the stack's home address could not be determined.
System Action:
Interface sampling for the period is not performed.
User Action:
From Command Entry, enter SELFTEST and check for errors related to the socket interface. If no errors are reported, issue a Netstat command to the stack to check whether there is a problem with the Netstat interface.
For assistance, contact Technical Support.
Reason:
A request to sample interface statistics failed because the interfaces could not be accessed. P1 is the address of the TCP/IP stack.
System Action:
Sampling for the period is not performed.
User Action:
Check the log for related messages that will indicated the reason for the error.
The most likely cause of the error would be a community name (other than 'public') not being specified. If this is the case specify the correct community name for the stack in the SNMP Community List of the TCP/IP Administration Menu.
Reason:
The interface workload monitoring procedure found stack P1 to be unknown to the Packet Analyzer.
The most likely cause is that this is a CA TCPaccess stack that does not have the requisite level of maintenance for Packet Analyzer support.
System Action:
The interface workload attributes sourced from the Packet Analyzer are not sampled.
User Action:
Do the following:
If the cause of the problem is not apparent, contact Technical Support.
Reason:
An attempt to perform interface workload monitoring returned P1 while attempting to access interface information from the packet analyzer.
System Action:
Attributes sourced from the packet analyzer are not sampled.
User Action:
See message P1 for more information.
Reason:
Interface workload monitoring has queried the Packet Analyzer in the SSI and found that it is currently not collecting statistics. Packet statistics are collected only when the SSI is running with PALEVEL=FULL.
System Action:
None of the interface attributes sourced from the Packet Analyzer are available.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
The Interface list processor was passed an unsupported value for the parameter P1 - the unsupported value was P2 .
System Action:
The list processing stops.
User Action:
Contact your local System Administrator.
Reason:
An unsupported option was entered on the Interface list.
System Action:
None.
User Action:
Correct the option and retry - the supported actions are shown on the 4th line of the screen.
Reason:
An MDO assignment failed. The MDORC was P1 and the MDOFDBK value was
P2 .
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
The call to the procedure failed because the call type P1 is not supported.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
$IPINIT was run during system initialization. Any values specified as parameters to $IPINIT are loaded as defaults.
System Action:
Records values specified on $IPINIT.
User Action:
Remove $IPINIT execution from your initialization procedure.
Reason:
The initialization process completed successfully.
System Action:
None.
User Action:
None.
Reason:
The $IPINIT command was executed but it is only used for migrating initialization values from SOLVE:Netmaster for TCP/IP V1.1 systems.
System Action:
$IPINIT terminates.
User Action:
None.
Reason:
The initialization of NetMaster for TCP/IP requires the feature P1 which is not licensed or is excluded from this system.
System Action:
Initialization terminates.
User Action:
Obtain a feature license or include the feature on this system.
Reason:
The initialization of NetMaster for TCP/IP failed because $IPINIT was called with incorrect parameter syntax. This message is followed by another message detailing the nature of the error.
System Action:
Initialization terminates.
User Action:
Correct the parameter specification and retry.
Reason:
The initialization of NetMaster for TCP/IP failed because $IPINIT was called with an incorrect parameter value. The parameter specified in error is P1 and P2 is the unacceptable value.
System Action:
Initialization terminates.
User Action:
Correct the parameter specification and retry.
Reason:
The initialization of NetMaster for TCP/IP could not start the TCP/IP interface. This message is preceeded in the log by messages which detail the error.
System Action:
Initialization continues.
User Action:
Determine the cause of the error and retry.
Reason:
The initialization of NetMaster for TCP/IP could not allocate the P1 DD. This message is followed by a message which details the error.
System Action:
Initialization continues.
User Action:
Determine the cause of the error and retry.
Reason:
The initialization of NetMaster for TCP/IP set the values of the parameters listed in the messages to follow.
System Action:
Parameter settings are displayed.
User Action:
None
Reason:
The initialization of NetMaster for TCP/IP set the value of the parameter P1 to the value P2
System Action:
None.
User Action:
None.
Reason:
The initialization of NetMaster for TCP/IP detected an incorrect DSORG for a specified dataset.
P1 is the parameter specified.
P2 is the dataset name.
P3 is the DSORG of that dataset.
System Action:
Initialization terminates.
User Action:
Specify a dataset which has a DSORG of PS and retry.
Reason:
The initialization of NetMaster for TCP/IP could not allocate the P1 DSN. This message is followed by a message which details the error.
System Action:
Initialization fails.
User Action:
Determine the cause of the error and retry.
Reason:
The initialization for TCP/IP tried to allocate a dataset to the DD name P1. No suitable datasets could be found.
System Action:
The DD is not allocated.
User Action:
Specify a valid dataset name that exists.
Reason:
Initialization failed to allocate a dataset P1 with the DD name P2 .
System Action:
The DD is not allocated. Processing continues.
User Action:
Enter a valid dataset name for the dataset required.
Reason:
TCP/IP Services initialization tried to open a dataset for VSAM processing however the file is not VSAM. P1 is the dataset name.
System Action:
The file is not opened.
User Action:
Specify a valid VSAM dataset and action the parameter group again.
Reason:
An error occurred during the initialization of the P1 function. The action in error is P2, The object that had the error is P3, and the return code is P4.
System Action:
Initialization is incomplete.
User Action:
Refer to your system administrator. Check the system log for further information.
Reason:
The DD name P1 was successfully allocated and opened using dataset name
P2.
System Action:
None.
User Action:
None.
Reason:
IPLOG is undergoing database maintenance which requires exclusive control. No further action is possible.
System Action:
Request is rejected.
User Action:
Retry later.
Reason:
The list of ports associated with the p1 protocol has been set to p2. SmartTrace uses the p1 protocol to decode the packets to and from these ports.
System Action:
None.
User Action:
None.
Reason:
The global variable P1 was set to the value P2 .
System Action:
None.
User Action:
None.
Reason:
You specified an invalid value for Trace Expiry.
System Action:
The field is set in error.
User Action:
Specify a period from 0:01 through p1 in the valid time format (hhh:mm).
Reason:
Access to the IP Security P2 facility has not been granted by your site's security system.
System Action:
Access to the selected IP Security function is denied.
User Action:
Contact your security administrator.
Reason:
Verification by your external security system failed. A SAF VERIFY check on user ID P1 resulted in SAF RC=4 and security system RC=4. This probably indicates that one of the following SERVAUTH class resources is not defined:
System Action:
Access to the selected IP Security function is denied.
User Action:
Contact your security administrator.
Reason:
Verification by your external security system has failed. A SAF VERIFY check on user ID P1 has resulted in SAF RC=8 and security system RC=28 (x'1C'), indicating that user access is revoked.
System Action:
Access to the selected IP Security function is denied.
User Action:
Contact your security administrator.
Reason:
A SAF call to verify access to the IPSec facility failed with an unexpected error. This message is written to the activity log together with messages IPISPK05 and IPISPK06 which contain more information about the failure.
System Action:
Access to the selected IP Security function is denied.
User Action:
Review the messages in the activity log.
Contact your security administrator.
Reason:
This message is part of a message set that is written to the activity log when an unexpected SAF resource check error occurs. The message shows the parameter string that was passed to the SAF program, NM022.
System Action:
Access to the selected IP Security function is denied.
User Action:
See messages IPISPK04 and IPISPK06.
Reason:
This message is part of a message set that is written to the activity log when an unexpected SAF resource check error occurs. The message shows the response details returned by the SAF program, NM022.
REQ=P1 is the RACROUTE REQUEST=operand
SAFRC=P2 is the SAF (RACROUTE) return code (R15)
SECRC=P3 is the security system return code
SECREAS=P4 is the security system reason code
For more information about the RACROUTE request macros, and the associated return codes and reason codes, see the (IBM) RACF System Macros manual. The most common SAFRC/SECRC combinations are:
04 PROGRAM ACTIVATION FAILURE
04 Program not APF-authorized
08 Invalid parameter
0C Missing parameter
10 Parameters inconsistent
08 SAF INTERFACE FAILURE
SAF/RACROUTE return codes:
04 Requested function was not processed
08 Requested function was processed, but failed
12 ACCESS VERIFICATION FAILURE
RACROUTE REQUEST=VERIFY return codes:
04 No security profile defined
08 Password invalid
0C Password expired
10 New password invalid
14 Group definition is missing
18 Security exit denied access
1C User temporarily revoked
20 Security system not active
24 Access to group is revoked
?? Others as per specific security subsystem
16 ACCESS AUTHORIZATION FAILURE
RACROUTE REQUEST=AUTH return codes:
04 Resource is not security protected
08 Resource access not allowed
99 NO ENTRY PARAMETERS
System Action:
Access to the selected IP Security function is denied.
User Action:
Contact your security administrator. Use the error codes and messages provided above to investigate the cause of the error. You also need:
Ensure that the region is running from an authorized load library. Ensure that your external SAF security system is active.
Ensure that your security administrator has set up SAF security for use with this region correctly.
Reason:
An error has occurred calling the SAF program, NM022. P1 describes the error.
System Action:
Access to the selected IP Security function is denied.
User Action:
This is an internal error that should be reported to your product supplier.
Reason:
The process to set up an IP Traffic test is cancelled.
System Action:
None.
User Action:
None.
Reason:
An action against a tunnel has been canceled by the user.
System Action:
None.
User Action:
None.
Reason:
The 'T' action was entered against an IP filter with no associated tunnelId, or with an associated tunnelId of 'Y0'.
System Action:
The request is rejected
User Action:
Chose a different filter, with a valid tunnelId
Reason:
The 'T' action was entered against an IKE tunnel. No dynamic tunnels were found for this tunnel.
System Action:
The request is rejected
User Action:
None.
Reason:
No details for the requested tunnel or filter were returned from IPSECNMI, or the tunnel or filter could not be uniquely identified.
System Action:
The request fails.
User Action:
Press F6 to refresh the list of filters or tunnels.
Reason:
An IPSECNMI request to SOLVE SSI failed with a USS error.
P1 is the USS function name, for example, BPX1CON, BPX1SND, or BPX1RCV.
P2 is the USS return value.
P3 is the USS return code.
P4 is the USS reason code.
System Action:
The request fails.
User Action:
Use the USS return and reason codes to determine the cause of the error. Check the SOLVE SSI log and IKED daemon output for other error messages. For assistance, contact Technical Support.
Reason:
The IPSECNMI interface between SOLVE SSI and the IKE daemon has terminated in error.
P1 is the IPSECNMI return code from the termination call.
P2 is the IPSECNMI reason code from the termination call.
System Action:
The request fails.
User Action:
Use the return and reason codes to determine the error. Typically, return and reason codes of zero indicate an orderly shutdown of the interface.
Reason:
An IPSECNMI request issued from the SOLVE SSI has failed. P1 is the failure reason from the IPSECNMI call.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
An IPSECNMI request to the SOLVE SSI failed because the SSI region cannot be contacted or does not include support for IPSECNMI.
The SSID (P1) and system (P2) identify the SSI region where the request is issued.
This message corresponds to EPS error numbers 39 and 70.
System Action:
The request fails.
User Action:
Check the following in the region running on P2:
Note: In order to use IPSECNMI, the user ID associated with your SOLVE SSI region must be authorized for IBM's Network Management API. See the product Installation Guide for details.
Reason:
An IPSECNMI request to SOLVE SSI did not complete in a reasonable time. The SSID (P1) and system (P2) identify the SOLVE SSI region where the request is issued.
System Action:
The request fails.
User Action:
Check the SOLVE SSI log and IKED daemon output for error messages, which can help you determine the cause of the problem. For assistance, contact Technical Support.
Reason:
An EPS request to the IPSECNMI function in the SOLVE SSI has failed. The message includes the following details:
P1 is the EPS request type, for example, Connect, Send, Receive.
P2 is the EPS error number.
P3 is an explanation of the EPS error number.
System Action:
The request fails.
User Action:
Use the EPS Error Number and Reason to determine the error:
This indicates that the connection between this region and the SSI region is not active. Use the $LOG command to check the activity log for related messages.
Use the $NM SSI Customizer parameter group to restart the SOLVE SSI.
For all other errors, contact Technical Support.
Reason:
An IPSECNMI request has failed. The type of request is shown in P1. P2 is the return code (NMsMRc) and P3 is the reason code (NMsMRsn).
System Action:
The request is rejected.
User Action:
For an explanation of the return and reason code, see IBM's Communication Server IP Programmer's Guide and Reference manual.
If the resolution of the problem is not evident, contact Technical Support.
Reason:
The selected stack is not configured with the IPCONFIG IPSECURITY statement.
System Action:
The request is rejected.
User Action:
Select a stack that is configured for IP Security.
Reason:
The selected tunnel has been activated or inactivated, as requested.
System Action:
None.
User Action:
None.
Reason:
A request to activate, inactivate or refresh a tunnel has failed, because the tunnel was not found.
System Action:
The request failed.
User Action:
Press F6=Refresh on the list of tunnels to ensure the list is up to date.
Reason:
A request to activate or inactivate a tunnel did not proceed, because the tunnel is already in the state requested.
System Action:
The request is not executed.
User Action:
None.
Reason:
An action request P1 against tunnel P2 has failed. P3 is the failure reason.
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
An attempt to access IPSECNMI for the indicated stack (P1) has failed, because the stack is inactive.
System Action:
The request is rejected.
User Action:
Investigate why the stack is inactive.
Reason:
The requested function is not currently supported by TCPaccess.
System Action:
Processing of the function is terminated.
User Action:
None.
Reason:
The displayed list is incomplete. P1 records are displayed out of a possible total of P2.
This situation occurs when there are too many records for the IPSECNMI interface to handle. An internal limit in IPSECNMI has been exceeded.
System Action:
The incomplete list is displayed.
User Action:
Contact Technical Support.
Reason:
A request to list items of type P1 for stack P2 has failed. No P1 items were returned from IPSECNMI.
System Action:
None.
User Action:
None.
Reason:
A request to list P1 items, using criteria supplied from the menu input fields, has returned with no matches.
System Action:
None.
User Action:
None.
Reason:
Tunnel P1 has been activated, inactivated or refreshed by user P4.
System Action:
This message is written to the activity log as an audit trail of actions against a tunnel.
User Action:
None.
Reason:
An IPSECNMI request has failed with a return code of 'EACCES'. This means the SOLVE SSI region has insufficient authority to perform the requested P1 IPSECNMI function against stack P2.
System Action:
The request is rejected.
User Action:
The IPSECNMI facility needs the userid associated with the SOLVE SSI address space to be authorized to the following SERVAUTH resources:
Alternatively, the userid associated with the SOLVE SSI region must be an OMVS superuser or must be permitted to the BPX.SUPERUSER resource in the FACILITY class.
Check whether this authorization has been granted, and review the SOLVE SSI, PAGENT, and IKE daemon logs for additional error messages.
For further information, contact Technical Support.
Reason:
An IPSECNMI request issued from SOLVE SSI has failed because the message returned from the NMI was too large to process.
System Action:
The request fails.
User Action:
Specify values in the Filter Type, Tunnel State, and/or Remote Endpoint fields to limit the size of the list requested.
If this is unsuccessful, contact Technical Support.
Reason:
The stack name entered in the Stack Name field is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack Name field to list the defined stacks, from which you can select one.
Reason:
No stacks are defined for the selected system.
System Action:
The request fails.
User Action:
Press F3 to return to the menu, and select another system.
Reason:
You requested an FTP connection summary, but this option is supported only on systems running z/OS V1R10.0 or later.
System Action:
The request is rejected.
User Action:
Select a stack running on a later z/OS version, or select another option.
Reason:
You entered a SORT command with an invalid operand. The valid operands are ACTIVE, SECURE, and P1.
System Action:
The request fails.
User Action:
Reissue the SORT command with a valid operand.
Reason:
An attempt to build a secured connection summary for all stacks on a system has found one or more inactive stacks, as indicated in P1.
System Action:
The summary is generated for the other stacks on the system.
User Action:
Check whether the indicated stack or stacks are active. If so, the resource definition for the stack may be incorrect. Review and correct the definitions, and request the summary again.
To review and correct a STACK resource definition
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 and the value by p2 .
System Action:
None
User Action:
Contact your System Administrator.
Reason:
The TCP/IP Link Monitor task, which maintains the TCP/IP Link Names List, is now active.
System Action:
None.
User Action:
None.
Reason:
The SOLVE TCP/IP Link Monitor task, which maintains the TCP/IP Link Names List, failed to initialize. The failure reason ( P1 ) is shown in the following message.
System Action:
The link monitor is inactive.
User Action:
Refer to the message explanation for the message which follows. When this problem is resolved, restart the link monitor by using the FILE command (F3) within the TCP/IP Administration, Multi-system Support option.
Reason:
An MDO assignment failed with ZMDORC 16 and ZMDOFDBK 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated during the installation of the product and any maintenance.
Reason:
An MDO assignment failed. The MAP was P1 , the MDORC was P3 , the MDOFDBK value was P4 , and the MDO component involved in the last operation was P2.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
This is an informational message indicating that the TCP/IP Link Monitor task, which maintains system configuration has processed the indicated event.
System Action:
System configuration information is updated as per the event.
User Action:
None.
Reason:
An attempt to start a background procedure to receive TN3270 log messages from a Cisco channel card ( P1 ) failed for the reason shown ( P2 ).
System Action:
The process is not started and the TN3270 log for the specified channel card is not available.
User Action:
Review the reason ( P1 ) that the start failed and use this to fix the problem.
Reason:
The TCP/IP Link Monitor task has received an error message from a remote system call. P1 identifies the remote system, P2 is the message received.
System Action:
None. The link monitor continues processing.
User Action:
Investigate the cause of the error on the remote system. More information may be available in the activity log of the remote system.
Reason:
A blank event name is received.
System Action:
None. The link monitor continues processing.
User Action:
Investigate the cause of the event with the process ID and message.
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 and the value by P2 .
System Action:
None.
User Action:
Contact your system administrator.
Reason:
The procedure failed because an &VARTABLE verb gave an unexpected return code. In the message:
P1 is the VARTABLE name.
P2 is the &VARTABLE request type.
P3 is the key for the entry.
P4 is the return code.
System Action:
The request is rejected and the procedure terminates.
User Action:
Contact your system administrator.
Reason:
An error has occurred while requesting device link information from the region identified by P1 . The error message is P2 .
System Action:
The procedure terminates.
User Action:
Contact your system administrator.
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 and the value by P2 .
System Action:
None.
User Action:
Contact your system administrator.
Reason:
The procedure failed because an &VARTABLE verb gave an unexpected return code. In the message:
P1 is the VARTABLE name.
P2 is the &VARTABLE request type.
P3 is the key for the entry.
P4 is the return code.
System Action:
The request is rejected and the procedure terminates.
User Action:
Contact your system administrator.
Reason:
The selected option is invalid if multiple links have been selected. The option is only valid for a single link name.
System Action:
None.
User Action:
Correct the entry and retry the operation.
Reason:
The selection list was exited without selecting an item.
System Action:
None
User Action:
None
Reason:
The name entered, P1 ,does not conform to the specification for a valid link or stack name.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter '?' in the stack field to obtain a list of stacks.
Reason:
There are no TCP/IP stacks known or defined to the local system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack field to obtain a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
If necessary, use the administration functions to define a stack for the sockets interface and/or define secondary stacks for connection awareness.
Reason:
There are no TCP/IP stacks that match the generic mask.
System Action:
The request is rejected.
User Action:
Enter '?' in the stack field to obtain a list of stacks.
Reason:
The Link Name identified by P1 is not currently active.
System Action:
The request is rejected.
User Action:
Investigate the cause of the link failure and retry the operation.
Reason:
The selected link is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the link name field to display a list of known links.
Reason:
Stack P1 is not suitable for the selected function. The function is only available for type P2 stacks.
System Action:
The request is rejected.
User Action:
Enter '?' in the stack field to obtain a list of stacks.
Reason:
There are no TCP/IP stacks of the P1 type defined.
System Action:
The request is rejected.
User Action:
The current function is only supported for stacks of the P1 type. If the environment should have stacks of this type defined, check the STACK resource definitions. You can check the definitions on the IP Resource Monitor (/IPMON shortcut).
Otherwise, select a different function.
Reason:
The TCP/IP Services log browse service procedure $IPLO80B does not support the calltype P1 from the browse utility ($CABU000).
System Action:
Log browse processing terminates.
User Action:
Contact your System Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An attempt was made to start the TCP/IP event logger but it was already running.
System Action:
The existing TCP/IP event logger continues.
User Action:
None.
Reason:
The TCP/IP Event Logger encountered an error when trying to perform an P1 command on the IPLOG database. The return code is P2. The TCP/IP Event Logger may terminate or continue processing as indicated by its status.
System Action:
The TCP/IP Event Logger may terminate if it cannot continue processing.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
The Event Logger received a VSAM I/O error when trying to add a record to the IPLOG database. This is a serious error, and the Event Logger has terminated. The most likely reason for this error is that the IPLOG database has become full.
System Action:
The Event Logger cannot continue processing and has terminated. The IPLOG database is most likely in a status of BAD-LOCKED.
User Action:
Check the Activity Log for further messages that indicate why the I/O error occurred. To access the log, type $LOG from any panel.
If the NDB is full and is marked BAD-LOCKED , the only solution is to delete and redefine the NDB. However, before doing this, if you wish to extract the data currently in the NDB, perform the following steps:
1. Issue the NDB START IPLOG UNLOCK INPUT command to open the database as input only. If you issue this command without the INPUT option, the SOLVE region will attempt to reapply the last transaction, causing the NDB to remain BAD-LOCKED .
2. Type the name of your extract dataset into the field provided on the History Data Menu ( /IPHIST ), and select option EX to start the extract process.
3. Go to the Activity Log ( $LOG ) for progress messages on the extract process.
4. When the extract process has finished, deallocate the IPLOG database by issuing the following commands:
- NDB STOP IPLOG to stop the database
- UDBCTL CLOSE=IPLOG to close the file
- DEALLOC DD=IPLOG to deallocate the file
5. After the IPLOG database has been deallocated, submit your batch job to delete and redefine the dataset (optionally giving it more space). For information about the attributes of the distributed database, see the SOLVE Installation and Setup Instructions .
6. Upon successful completion of the batch job, go to the Customizer : Parameter Groups menu ( /PARMS ) and check that all parameters in IPFILES parameter group are correct. You might want to decrease the number of days worth of records to be stored within the database.
7. Press F3 (File) to action the parameters. This reinitializes the Event Logging environment, and the Event Logger should restart with no problems.
Reason:
The Event Logger tried to add a record to the IPLOG database and discovered that the database was locked. This is a serious error, and the Event Logger has terminated. The most likely reason for this error is that the IPLOG database has become full.
System Action:
The Event Logger cannot continue processing and has terminated. The IPLOG database is in a status of LOCKED or BAD-LOCKED.
User Action:
Check the Activity Log for further messages that indicate why the I/O error occurred. To access the log, enter $LOG from any panel.
It is uncommon for the NDB to have the LOCKED status. However, if this occurs, issue an NDB START IPLOG UNLOCK command and then action the Customizer : Parameter Groups ( /PARMS ) IPFILES parameter group by pressing F6. If the NDB is full and has the BAD-LOCKED status, the only solution is to delete and redefine the NDB. However, before doing this, if you wish to extract the data currently in the NDB, perform the following steps:
1. Issue the NDB START IPLOG UNLOCK INPUT command to open the database as input-only. If you issue this command without the INPUT option, the SOLVE region will attempt to reapply the last transaction, causing the NDB to remain BAD-LOCKED .
2. Type the name of your extract dataset into the field provided on the History Data Menu ( /IPHIST ), and select option EX to start the extract process.
3. Go to the Activity Log ( $LOG ) for progress messages on the extract process.
4. When the extract process has finished, deallocate the IPLOG database by issuing the following commands:
- NDB STOP IPLOG to stop the database - UDBCTL CLOSE=IPLOG to close the file - DEALLOC DD=IPLOG to deallocate the file
5. After the IPLOG database has been deallocated, submit your batch job to delete and redefine the dataset (optionally giving it more space). For information about the attributes of the distributed database, see the SOLVE Installation and Setup Instructions .
6. Upon successful completion of the batch job, go to the Customizer : Parameter Groups menu ( /PARMS ) and check that all parameters in IPFILES parameter group are correct. You might want to decrease the number of days worth of records to be stored within the database.
7. Press F3 (File) to action the parameters. This reinitializes the Event Logging environment, and the Event Logger should restart with no problems.
Reason:
The Event Logger has determined that the IPLOG database is currently being upgraded to a newer version.
System Action:
The Event Logger waits for the upgrade process to complete.
User Action:
None
Reason:
The Event Logger tried to add a record to a full IPLOG database and failed, so it is initiating the IPLOG database reorganization process.
System Action:
Event logging is paused while the reorg is in process.
User Action:
None.
Reason:
The IPLOG initialization is complete. P1 may indicate (SMF ONLY), which means that no records are written to the IPLOG due to errors during startup.
System Action:
Logging continues. If P1 indicates (SMF ONLY), SMF recording is available only if SMF logging is enabled; otherwise all records are discarded.
User Action:
Check the initialization log to determine the cause of the failure, if any.
Reason:
An NDB error prevented records from being written to IPLOG, and caused the logger to only record events through SMF, if SMF logging is enabled.
System Action:
Logging continues if SMF logging is enabled; otherwise, all records are discarded.
User Action:
Check the initialization log to determine the cause of the failure.
To enable SMF logging, set the Write samples to SMF? field to YES in the IPFILES Customizer parameter group and specify a non-zero value in the SMF Record Identifier field of the SMF Customizer parameter group.
Reason:
The IPLOG is recovered and the logger resumes writing records to the NDB.
System Action:
Logging continues.
User Action:
None.
Reason:
IPLOG Logger has stopped. If P1 is present, the logger was terminated due to errors.
System Action:
None.
User Action:
Review the activity log to determine the reason for the logger being stopped.
Reason:
While logging a file transfer event, the first P1 characters of Dataset Name 1 or Dataset Name 2 were truncated and the last 255 characters retained in the log record. The succeeding message IPLO8116 shows the complete name.
System Action:
Event logging continues.
User Action:
Contact your local support representative.
Reason:
This message follows IPLO8115 message, which displays the complete Dataset Name P2 .
System Action:
None.
User Action:
None.
Reason:
The TCP/IP P1 procedure has started. This procedure will extract records from the IPLOG TCP/IP event database and write them in comma-delimited format to a sequential dataset. If the process is an ARCHIVE, then the records will also be deleted.
System Action:
The TCP/IP P1 process continues running.
User Action:
None.
Reason:
The TCP/IP P1 procedure has finished. This procedure extracts records from the IPLOG TCP/IP event database and writes them in in comma-delimited format to a sequential dataset. If the process is an ARCHIVE then the records are also deleted.
System Action:
The TCP/IP P1 process finishes.
User Action:
None.
Reason:
An error occurred while performing a p1 command on the IPXTRACT file. The return code is p2.
System Action:
The process may or may not continue processing.
User Action:
To determine the cause of the error, review the activity log. The probable causes can vary from not having enough space or the selected file is not available to the current user. For further assistance, contact your system administrator.
Reason:
An error occurred when trying to perform an P1 command on the IPLOG database. The NDB return code is P2.
It is normal to get this error message with an action of 'START:1' when the NDB is first accessed. The reason for this is that the dataset is not an NDB at this point, and will only be formatted as an NDB as a result of this error.
System Action:
The process will P3 processing.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
The extraction process is commencing the WRITE step.
System Action:
The extraction process continues.
User Action:
None.
Reason:
The TCP/IP archive process is commencing the 'DELETE' step of its processing.
System Action:
The TCP/IP archive process continues running.
User Action:
None.
Reason:
The call to the procedure failed because the Keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP P1 process did not find any records that qualify for
P1.
System Action:
The TCP/IP P1 process terminates.
User Action:
None.
Reason:
The TCP/IP events extraction process has written p1 records to the IPXTRACT file.
System Action:
The extraction process continues.
User Action:
None.
Reason:
An error was encountered when trying to format the dataset P1 as an NDB
System Action:
Reporting will not continue.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
An 'NDB START' command was issued for the IPLOG Reporting database but another domain ID was present in the NDB control record.
System Action:
Reporting will not continue.
User Action:
Check to ensure that this dataset is not currently in use by another region. If it is not being used and you are sure that this is the dataset you wish to open, issue the 'NDB START IPLOG FORCE UNLOCK' command from an OCS window and then re-initialize the Reporting feature from the Administration menu.
Reason:
The TCP/IP archive process has deleted P1 records from the IPLOG dataset.
System Action:
The TCP/IP archive process continues running.
User Action:
None.
Reason:
The Reporting initialization process has discovered that the IPLOG database was created by an earlier release of NetMaster for TCP/IP and is now upgrading the database to the version indicated by P1
System Action:
IPLOG NDB conversion continues.
User Action:
None.
Reason:
The IPLOG upgrade process is converting the IPLOG database to a newer version. This process updates records by copying data from old fields into new fields. This message indicates how many records have been processed thus far.
System Action:
The IPLOG upgrade process continues running.
User Action:
None.
Reason:
The IPLOG database upgrade process has completed.
System Action:
The IPLOG Event Logger will now continue.
User Action:
None.
Reason:
An error occurred when trying to access the IPLOG NDB. The action being attempted is P1 and the NDB return code is P2. The optional NDB error indicator is P3.
System Action:
Processing terminates.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
The data component of the IPLOG dataset has reached P1 capacity. If it reaches 100% then logging to the IPLOG dataset will stop and the automatic reorg process may fail if no space can be reclaimed.
System Action:
IPLOG initialization continues.
User Action:
Verify that the parameters controlling your IPLOG environment are set satisfactorily. These include:
1) The size of your IPLOG dataset.
2) The number of days you wish to keep records for.
The IPLOG dataset must be large enough to hold the TCP/IP event records generated by your system for the number of days you wish to keep.
3) Time of day to extract. Your NetMaster region needs to be up at this time if any expired records are to be deleted from the IPLOG dataset.
Reason:
The IPLOG reorg process has started.
System Action:
Reorg processing continues.
User Action:
None.
Reason:
The IPLOG reorganization process is beginning step 1 - copying all records from the IPLOG NDB to the sequential dataset indicated by P1.
System Action:
Reorg processing continues.
User Action:
None.
Reason:
The IPLOG reorganization process is beginning step 2 - copying all records from the sequential dataset indicated by P1 to the IPLOG NDB.
System Action:
Reorg processing continues.
User Action:
None.
Reason:
This is an IDCAMS message produced by the IPLOG reorg process.
System Action:
Reorg processing continues.
User Action:
None.
Reason:
The IPLOG reorg process has either successfully finished or it has failed, depending upon the status of P1.
System Action:
Reorg processing has finished. TCP/IP event logging should resume normally if the reorg was successful. If it failed then TCP/IP event logging has stopped and an alert is raised.
User Action:
None.
Reason:
The IPLOG reorg process could not continue as no sequential dataset has been defined for the reorg.
System Action:
Reorg processing terminates.
User Action:
Define a sequential dataset with a record length of 4096, a block size of 23445, and a record format of VB. Then add the dataset name to the IPLOGSEQ Reorg Dataset field on the TCP/IP Reporting Configuration panel.
Reason:
An automated attempt to start the IPLOG reorg process has failed because it is already running.
System Action:
Processing terminates.
User Action:
None.
Reason:
An NDB STOP command for the IPLOG failed with RC= P1 .
System Action:
Processing terminates, and the logger is not restarted.
User Action:
See the NCL programmer Guide to determine the appropriate action for this return code.
Reason:
An NDB PURGE command for the IPLOG failed with RC= P1 .
System Action:
Processing terminates, and the logger is not restarted.
User Action:
See the NCL Programmer Guide to determine the appropriate action for this return code.
Reason:
The IPLOG could not be processed because an NDB START command has not been issued or has failed. The meaning of status P1 is described in message N89503 .
System Action:
Processing terminates.
User Action:
Check the IPFILES initialization log to determine the appropriate action
Reason:
The IPLOG record deletion processing has failed.
System Action:
Processing terminates.
User Action:
Check the IPFILES Initialization Log for details of the failure and determine the appropriate action.
Reason:
During IPLOG START or automatic REORG, it was determined that the current dataset is no longer usable. An attempt was made to backup and rename the current IPLOG but the new name is already in use. The backup dataset name would have the format:
&ZDNSQLCL.&ZJOBNAME.IPLOG.annnv
where:
&ZDNSQLCL = value of the local dataset qualifier as set in the DSNQLCL JCL parameter &ZJOBNAME = jobname of the NetMaster region a = is an alphabetic character from A to J and is indexed by the last digit of the current year + 1 nnn = current Julian day v = version number from 0 to 9
System Action:
Processing terminates with the logger processing unable to write records to IPLOG but SMF processing continues.
User Action:
Specify a new IPLOG dataset in the IPFILES parameter panel.
Reason:
The VSAM DATA and INDEX component names of the current IPLOG could not be determined from an IDCAMS LISTCAT.
System Action:
Processing terminates with the logger processing unable to write records to IPLOG but SMF processing continues.
User Action:
Specify a new IPLOG dataset in the IPFILES parameter panel.
Reason:
This is an IDCAMS message produced during renaming of the IPLOG.
System Action:
Processing continues.
User Action:
None.
Reason:
IPLOG is undergoing database maintenance which requires exclusive control. No further action is possible.
System Action:
The current request waits until exclusive control is released.
User Action:
None.
Reason:
During IPLOG START or automatic REORG, it was determined that the current dataset is no longer usable. An attempt to define a new IPLOG dataset failed.
System Action:
Processing terminates with the logger processing unable to write records to IPLOG but SMF processing continues.
User Action:
Review the initialization log to determine the cause of the failure or specify a new IPLOG dataset form the IPFILES parameter display panel.
Reason:
The IPLOG dataset has been RENAMED or RESTORED to P2 .
System Action:
Processing continues.
User Action:
None.
Reason:
The IPLOG is being resized. The new size is determined by the product of the average record length and the total number of records rounded up to the next megabyte.
System Action:
Processing continues with records being cached during resizing.
User Action:
None.
Reason:
An NDB START command for the IPLOG completed without errors.
System Action:
None
User Action:
None
Reason:
The IPLOG file is not available to process an IMPORT request due to one of the reasons indicated by P1.
System Action:
Processing terminates.
User Action:
To enable IPLOG:
Reason:
An error occurred when trying to execute an IMPORT request against the source described in action P1. The corresponding NDB return code P2 and optional error information P3 is shown.
System Action:
Processing terminates.
User Action:
For more information about NDB Response Codes and corresponding error information, see the NCL Programmer Guide.
For further assistance, contact Technical Support.
Reason:
The IPLOG import process started.
System Action:
Import processing continues.
User Action:
None.
Reason:
The import process wrote P1 records to the IPLOG data set.
System Action:
The import process continues.
User Action:
None.
Reason:
The import process completed.
System Action:
Processing terminates.
User Action:
None.
Reason:
The import process failed with the preceding message, which indicates the cause of the failure.
System Action:
Processing terminates.
User Action:
Review the preceding error messages to determine the reason for the failure and retry the request when appropriate.
Reason:
Initialization for the logging of events is incomplete because the supplied data set is not compatible with the current release of the product.
System Action:
Logging continues without a log data set. SMF records are written if SMF logging is enabled; otherwise, all records are discarded.
User Action:
To enable the logging of events to IPLOG:
If you want to retain the records from an earlier version of IPLOG, perform additional steps to migrate the records.
Follow these steps:
SUBMIT BSYS $IPLO82Z ACTION=IMPORT DSNAME=old_IPLOG_dataset_name
Reason:
The import process detected P1 duplicate records during IPLOG import processing.
System Action:
The duplicate records are rejected.
User Action:
None.
Reason:
The IPLOG may not be usable or correct. Either the user does not have the necessary OCS command authority or NPF is restricting access.
System Action:
The ACTION is not performed.
User Action:
Contact administrator to obtain authorization to execute the NDB command.
Reason:
An attempt was made to start the IPLOG Monitor, but it is already running.
System Action:
Processing terminates.
User Action:
None
Reason:
An attempt to query the status of the IPLOG failed bacause it is not allocated or the Logger was disabled.
System Action:
Processing terminates.
User Action:
Review the initialization log to determine why logging has been stopped.
Reason:
Automatic IPLOG reorganization processing has failed.
System Action:
Process terminates and re-scheduled at the next monitoring cycle.
User Action:
Review the IPFILES Initialization log to determine the cause of the failure.
Reason:
The IPLOG P1 component currently has a utilization space of P2 extents.
System Action:
The IPLOG Monitor continues processing.
User Action:
None.
Reason:
The IPLOG Monitor determined that no significant space was reclaimed after an automatic REORG was performed. The DU( P1 ) and IU( P2 ) values display the data and index utilization respectively after the completion of the REORG.
System Action:
Processing continues. At the next REORG, the file will be resized,
User Action:
Review space utilization. If necessary, reallocate the IPLOG with more space or schedule a deletion of old records.
Reason:
The IPLOG Monitor failed to initialize since it was not enabled.
System Action:
Processing terminates.
User Action:
Action (PF6) the initialization parameters for $IP IPFILES to restart the IPLOG monitor.
Reason:
IPLOG Automatic Reorg has determined that the last execution did not alleviate the IPLOG full condition. A new reorganization will not be scheduled.
System Action:
Processing terminates and logging remains inactive.
User Action:
Schedule an archive to delete old records or allocate more space to the IPLOG.
Reason:
Errors are detected in the Dataset or HFS file field. p1 provides the following explanation:
Indicates that the specified text is not the name of a file.
Indicates that the specified text does not have a PDS member name.
Indicates that the specified text does not conform to path naming rules.
Indicates that the specified path either does not exist or is not available for processing the request.
Indicates that a relative directory path was specified, which is not supported.
Indicates that the specified text does not conform to file naming rules.
Indicates that the specified name points to a directory.
Indicates that the specified text does not conform to PDS member naming rules.
Indicates that the specified text does not contain a qualified data set name.
Indicates that the specified name points to a data set that is not valid for this function.
Indicates that the specified name points to a data set that is not a partitioned data set.
Indicates that the target data set has a logical record length less than n bytes.
System Action:
None.
User Action:
Correct the indicated error, and retry the operation.
Reason:
The value entered is not a valid data set name, or a valid file path and name.
System Action:
The field is set in error.
User Action:
Specify a valid data set name or a valid file name.
Reason:
You have selected an IP History option but the IPLOG file is not configured. IP history is stored in the IPLOG file.
System Action:
Option not processed.
User Action:
Use Customizer (/PARMS) to configure the IPLOG file in the IPFILES parameter group.
Reason:
The Reporting database (IPLOG NDB) is in a status of P1 and is not available for Reporting.
System Action:
Option not processed.
User Action:
Determine why the IPLOG NDB is not ACTIVE and resolve the problem.
Reason:
The line print daemon command handling procedure does not recognize the action P1 and is unable to process it.
System Action:
The request is rejected and the procedure terminates.
User Action:
Contact your local support representative.
Reason:
A portion of the file PRINT command to the Line Printer Daemon failed during processing. P1 describes the particular section during which the failure occurred.
System Action:
The print request processing is terminated.
User Action:
Retry the operation and, if unsuccessful, report the problem to your network systems administrator.
Reason:
The print request command was successfully sent to the line print daemon.
System Action:
None.
User Action:
None.
Reason:
A line printer command process received an error indication while freeing TCP/IP resources. P1 and P2 are the return values from SOCKET DEALLOCATE.
System Action:
Processing continues.
User Action:
Report the error to your product support representative.
Reason:
A line print command process has been started using TRACE=YES. The message text is one of the three indicated formats. The first two formats are heading lines that display the direction relative to the terminal of the data flow and P1 its length. The third format is a dump of the datastream that is repeated until the entire datastream is displayed. The fields are:
P1 - The offset into the datastream
P2-P5 - The hexadecimal display of the ASCII characters
P6 - The EBCDIC character form of the data
Note: When data has been entered using the Hide function of the fullscreen interface or using TRACESUP=YES, the datastream is replaced by the characters '**SUPPRESSED**'.
System Action:
None.
User Action:
Use the trace output to verify that session operation is as desired.
Reason:
A request to connect to the line print daemon was refused by the host. This is usually because the print services process on the host is not active or is not installed.
System Action:
The request is terminated.
User Action:
Determine if printing services are available at the host. If not available contact your network administrator to activate them.
Reason:
A request for TCP/IP print services sent to host P1 was unable to be serviced because the host machine is down.
System Action:
The request is terminated.
User Action:
Advise your system administrator of the host machines problem.
Reason:
A request for TCP/IP print services sent to host P1 was unable to be serviced because the host machine is unreachable.
System Action:
The request is terminated.
User Action:
Advise your system administrator of the problem with the host machine.
Reason:
An LPD request cannot proceed. The target address is IPv6, but the sockets API in region P1 supports IPv4 addresses only.
System Action:
The action terminates.
User Action:
Check the SOCKETS parameter group (/PARMS) in the P1 region. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
A line print request SOCKET verb has indicated an error condition.
P1 is the verb which failed. P2, P3 and P4 indicate the error received. P5 is the interpretation of the error code indicating the reason for the failure.
System Action:
The line print request process is terminated.
User Action:
Use the error information to determine the cause of the error. If necessary restart the session.
Reason:
A line print command process did not be start because TCP/IP services are not active.
System Action:
None.
User Action:
Use the SHOW TCPIP STATUS command to determine the state of the Interface. If necessary issue the TCPIP START command to activate the interface.
Reason:
The line print command connection request did not recieve a response from the peer host within the one minute limit.
System Action:
The line print process terminates.
User Action:
Use the PING command to determine if the peer host is reachable.
Reason:
The line print command connection was closed by the peer host.
System Action:
The line print command process terminates.
User Action:
Use the PING command to determine if the peer host is reachable.
Reason:
A Line Print request SOCKET verb has indicated an error condition.
P1 is the verb which failed. P2, P3 and P4 indicate the error received.
System Action:
The Line Print request process is terminated.
User Action:
Use the error information to determine the cause of the error. If necessary restart the session.
Reason:
The line print command connection request was not responded to by the peer host before the wait interval expired.
System Action:
The line print process terminates.
User Action:
Use the PING command to determine if the peer host is reachable.
Reason:
The request to delete the print queue entry P1 was rejected by the print server. This may be because the requester does not have sufficient authority at the P2 print server.
System Action:
The print request processing is terminated.
User Action:
Retry the operation and, if unsuccessful, report the problem to your network systems administrator.
Reason:
The delete print queue entry request command was successfully sent to and accepted by the Line Print Daemon.
System Action:
None.
User Action:
None.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command. To display valid line commands, enter ? next to the record.
Reason:
The 'DELETE' command was requested against the first entry in the list. This is not allowed as the only way to recover other deleted entries is by issuing a GetNext request against the first entry.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
A request was made to initiate the MIB browser but no valid host name or IP address was passed to it. Thus the browser cannot determine what device is to be browsed.
System Action:
The MIB browser does not initialize.
User Action:
Provide a valid host name or IP address and retry.
Reason:
If the MIB browser has not been passed one or more OIDs with which to prime its display it will normally present a list of loaded MIBs from which the user can select the MIBs whose OIDs are to be used to prime the display. This message indicates that no MIB definitions have been loaded and were therefore not available to be selected.
It also means that the browser will not be able to make an intelligent interpretation of the OIDs that are eventually displayed.
System Action:
The MIB browser continues with limited intelligence.
User Action:
If you require a more intelligent display then proceed to the MIB Administration display (/MIBD) and load the MIBs that you require then restart the browser.
Reason:
You have requested the GetNext, GetTable, or Skip line command, or the Walk primary command, but you have specified an invalid GetNext amount. The GetNext amount must be a number between 1 and 100, inclusive.
This value is used by the GetNext action to limit the number of Object IDs requested. The GetTable action uses this value to limit the size of the GetNexts it issues when populating a table. The Skip action is a GetNext action that begins with the first object after the current table or group. The Walk command is a GetNext action performed on the last object in the current MIB Browser.
System Action:
The user request is not actioned.
User Action:
Change the GetNext amount to a value between 1 and 100 inclusive and retry the requested action.
Reason:
An SNMP request has resulted in an IPSNPK09 message which indicates either that SNMP is unavailable on this host or that the SNMP security details supplied with the request did not warrant authorization (in which case the request fails).
System Action:
The SNMP request fails with an IPSNPK09 message.
User Action:
If SNMP is available on the host, then try typing CHGSEC on the command line to change your user-level SNMP security details.
Reason:
The MIBinsight browser does not contain any OIDs for browsing, that is, it is an empty list.
System Action:
The MIBinsight browser continues but no browsing can be done until the browser obtains at least one OID.
User Action:
Issue one of the following primary commands to add OIDs to the browser:
ADDMIB - Adds OIDs from a compiled MIB definition
FIRST - Adds and gets the value for the first OID in the device MIB
OID - Adds a specific OID to the browser (the OID must be provided as a parameter on the command)
WALK - Starts walking through the MIB (this gets the first set of OIDs)
Reason:
The 3270 MIB browser can display a maximum of 9998 list items. This includes MIB objects, groups, tables, and table sort groupings. Your current browser session has more than 9998 items to display. This is not possible.
System Action:
List formatting stops when 9998 items are formatted for display.
User Action:
Hide (collapse) or delete any unnecessary objects to display objects beyond the end of the list.
Reason:
The OID command adds a specific OID to the MIBinsight Browser; therefore, it requires a valid OID as a parameter, otherwise no OID is added.
System Action:
The command is rejected.
User Action:
Include a valid OID as a parameter on the OID command.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command. To display valid line commands, enter ? next to the record.
Reason:
The initial Object ID provided to the MIBinsight Browser is not a valid Object ID.
System Action:
The MIBinsight Browser continues but does not add the requested Object ID to its display.
User Action:
Restart the MIBinsight Browser and provide a valid Object ID. Alternatively, use the OID command to add a valid Object ID to the MIBinsight Browser display.
Reason:
An SNMP request cannot proceed. The target address is IPv6, but the sockets API on region P1 supports IPv4 addresses only.
System Action:
The action terminates.
User Action:
Check the SOCKETS parameter group (/PARMS) on region P1. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
A request was made to the MIB Browser Data Manager to return information for an OID but no OID key was passed to the Data Manager. This should never occur, if it does it would indicate a problem with the MIB Browser
System Action:
The MIB Browser Data Manager returns nothing.
User Action:
Contact your support personnel and pass them the details of your MIB Browser session to see if they can replicate the problem.
Reason:
An error occurred performing an ASSIGN of an MDO. The MDO is identified by P1 , the Map is identified by P2 , the MDO return code is identified by P3 and the MDO Feedback value is identified by P4 .
System Action:
The procedure terminates.
User Action:
Contact your system administrator.
Reason:
The MIB Browser encountered an error when trying to fetch the user's SNMP security information.
System Action:
The MIB Browser will continue the SNMP request using default information
User Action:
Update your SNMP security information using the facility provided. If you are using the 3270 MIB Browser interface then type the 'CHGSEC' command at the command line and press <ENTER>. If you are using the MIB Browser via the NetMaster web interface then click on the 'Change user security details' link.
Reason:
The MIB Browser encountered an error when trying to save the user's SNMP security information. The error feedback code is P1.
System Action:
The MIB Browser will continue to function using default SNMP security.
User Action:
Contact your system administrator.
Reason:
The value of the MIB object indicated by the Object Id in P2 has been successfully changed to the value shown in P3 in the MIB of the device whose IP address is P1 by user P4.
This is simply an informational message to provide an audit trail.
System Action:
None.
User Action:
None.
Reason:
A GetNext, GetTable, Skip, or Walk request has reached the end of this device's MIB.
System Action:
None.
User Action:
Do not issue any further GetNext, GetTable, Skip, or Walk commands because there are no more OIDs available in the device's MIB.
Reason:
A GetGeneric (GetTable) request returned no OIDs that match the generic OID provided. This is probably because a MIB definition was loaded into the browser that contains tables and SNMP levels that do not exist in this device's MIB.
System Action:
No OIDs are returned.
User Action:
Do not issue Get requests for OIDs in this table or SNMP level. We recommend that you delete the table or SNMP level from the MIBinsight browser.
Reason:
A GetGeneric (GetTable) request has returned 10,000 objects and there are more.
System Action:
The request terminates when 10,000 objects are returned.
User Action:
This table is extremely large. Be careful when you perform further GetTable or GetNext requests for this table.
The 3270 MIB browser supports a maximum of 32,767 sort entries (objects, groups, and so on), but displays a maximum of 9,998 lines of output only. The WebCenter MIB browser supports a maximum of 500 objects (plus SNMP groups and sort groupings). After 500 objects are browsed, no more objects are added to the MIB browser until you create space by deleting unwanted objects.
Reason:
Browsing the objects in this MIB has resulted in a list that contains more than 32,767 sort entries.
System Action:
The sorting process has stopped at the 32,767th entry. The resulting list is incomplete.
User Action:
Delete some unwanted objects from your browser list.
Reason:
This is an information message. All OIDs returned by a GetNext request begin with the initial OID. This indicates that all OIDs are probably in a large SNMP Group or Table.
System Action:
The OIDs and their values are returned correctly.
User Action:
If the GetNext is issued for a collapsed SNMP Group or Table, any subsequent GetNexts at the same level return the same OIDs. Try using a GetTable command to populate the entire level, or the Skip command if you are not interested in this level. Alternatively, expand the Group or Table and continue issuing GetNexts from OIDs in the structure.
Reason:
This message is information only. A GetGeneric (GetTable) request has finished populating a table or SNMP group.
System Action:
The request completes.
User Action:
If the table or group is collapsed, expand it to view all objects in this level.
Reason:
The web interface for the MIBinsight Browser limits the number of objects that can be browsed to 500. This maintains a reasonable response time on the web. The browser can display more than 500 lines due to groups and sort groupings being inserted.
System Action:
No new OIDs are added to the display.
User Action:
If you want to browse more OIDs, you must delete unwanted OIDs. Alternatively, use the 3270 interface for the MIBinsight Browser.
Reason:
A Delete OID or Delete MIB command has resulted in P1 objects being removed from the MIBinsight Browser.
System Action:
None.
User Action:
None.
Reason:
You tried to update an object value, but the MIB browser could not get the SNMP object type which is required for update. Either the object does not exist within the run-time MIB or SNMP access to this object is either unavailable or unauthorized.
System Action:
The MIB browser prevents update access to this object.
User Action:
Determine why the SNMP information could not be accessed. Is an SNMP agent running on the device being browsed? Have the required security levels been set up correctly? If not, fix these issues and try again.
Reason:
You successfully updated the value for MIB object P1.
System Action:
The MIBinsight browser returns you to either the main browser display or the 'Object Details' display in browse mode, showing the new value for the MIB object.
User Action:
None.
Reason:
You tried updating the value of a MIB object with a value other than an integer when the syntax of the object indicates that it can only contain an integer value (e.g. INTEGER, TruthValue, TestAndIncr, etc.)
System Action:
Update is rejected.
User Action:
Enter a valid integer value and try again.
Reason:
This is an informational message to remind you that you can type CHGSEC on the command line while browsing a MIB if you need to change your user-level SNMP security details for the host whose MIB you are browsing.
System Action:
None
User Action:
None
Reason:
A request was made to update MIB browser user security details, but no host name or IP address was passed on the request. Therefore the correct user security details cannot be determined.
System Action:
The MIB browser user security details interface terminates.
User Action:
Provide a host name or IP address and retry.
Reason:
The Security Level value indicates either authentication or privacy. The field specified in P1 is required.
System Action:
The field is highlighted.
User Action:
Enter a value in field P1 .
Reason:
An invalid value has been entered in field P1 . Correct values for this field are described in P2 .
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
The field P1 has been omitted. This field is required when field
P2 has the value P3 .
System Action:
The omitted field is highlighted.
User Action:
Enter a value in the field.
Reason:
You have entered a password in a non-display field. This message prompts you to reenter the password for confirmation.
System Action:
Processing continues.
User Action:
Reenter the password.
Reason:
The password value entered for confirmation differs from the value first entered.
System Action:
The password value is rejected.
User Action:
Reenter the password.
Reason:
An attempt to access the MIB import/export dataset failed. No import/export dataset is allocated to the region.
System Action:
The MIB compile may fail.
User Action:
The MIB import/export dataset (IPMIBX) is defined in the IPFILES parameter group. Review this parameter group and ensure that a dataset is defined for IPMIBX.
Reason:
An error occurred when trying to perform a P1 action on the IPMIBX Data Set. The Error Code is P2 .
System Action:
The MIB Compilation will continue processing, but errors may result.
User Action:
The Error Code P2 is the RPLERRCD value returned by the VSAM macro. Look up the RPLERRCD value in the IBM Manual 'DFSMS Macro Instructions for Datasets'. If the cause of the problem is not evident, contact your System Administrator. After addressing the Data Set problem the MIB Compilation should be retried.
Reason:
The compiled data for MIB P1 has been saved successfully.
System Action:
No further action.
User Action:
No action.
Reason:
An attempt was made to read MIB data from an external file but no data was returned. The file is either an empty HFS file or sequential file, or a PDS file.
System Action:
Request fails and control is returned to the user.
User Action:
Make sure you have specified the correct file name for the external source file. The source file must be a HFS file or a sequential file containing data, or a PDS member containing data.
Reason:
The MIB "Browse Source" function was requested but no source was found for the saved MIB definition specified or for the external file provided
System Action:
Request fails and control is returned to the user.
User Action:
Make sure you have specified the correct file name for an external browse source request from the add, copy or compile MIB panels.
Reason:
An invalid HFS filename or DSN P1 was specified in the External Source
File field.
System Action:
None.
User Action:
Correct the HFS filename or DSN and retry. The file must be a HFS file, a sequential dataset or a PDS member.
Reason:
No value was provided in field P1 . It is a required field.
System Action:
None.
User Action:
Provide the necessary data and retry the action.
Reason:
Either no value or an invalid value was provided in the "Batch Compilation Order" field. This field is a required field and must be an integer between 1 and 9 inclusive.
System Action:
None.
User Action:
Provide the necessary data and retry the action.
Reason:
'Export Definitions' cannot be set to 'YES' if no MIB Import/Export dataset has been defined.
System Action:
Validation fails.
User Action:
Update the $IP IPFILES parameter group in Customizer and specify a valid dataset in the MIB Import/Export dataset field.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
This is an informational message to remind you that you can type ADDMIB on the command line while browsing a MIB if you wish to add more MIB definitions to your MIB browser.
System Action:
None
User Action:
None
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
A line command was entered against a record that does not support the command.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
An object with a minimum ACCESS level of NOT-ACCESSIBLE cannot be used as a monitoring attribute.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request for a list of qualifying objects has resulted in an empty list because all possible qualifying objects has a minimum ACCESS level of NOT-ACCESSIBLE.
System Action:
None.
User Action:
None.
Reason:
The MIB batch compiler is starting.
System Action:
The MIB batch compiler proceeds.
User Action:
None.
Reason:
The MIB batch compiler has finished its processing.
System Action:
The MIB batch compiler ends.
User Action:
None.
Reason:
The MIB batch compiler is processing the MIB indicated by P1 . The current batch compilation order is indicated by P2 .
System Action:
The MIB batch compiler continues.
User Action:
None.
Reason:
The MIB batch compiler has finished compiling the MIB indicated by P1 . The return code is indicated by P2 .
System Action:
The MIB batch compiler continues.
User Action:
None.
Reason:
The MIB batch compiler has submitted itself to the background system region for processing. All messages from the batch compiler will be recorded in the activity log.
System Action:
The MIB batch compiler continues.
User Action:
None.
Reason:
The MIB batch compiler is beginning its first pass through all MIB definitions to determine the compilation order.
System Action:
The MIB batch compiler continues.
User Action:
None.
Reason:
The MIB batch compiler is processing the MIB indicated by P1 and saving its IMPORT information so that the compilation order can be determined.
System Action:
The MIB batch compiler continues.
User Action:
None.
Reason:
A request was made to start the MIB Batch Compiler but another one was already running in the background system region. As a result this request is rejected.
System Action:
The request to start the MIB Batch Compiler is rejected.
User Action:
Wait for the current MIB Batch Compiler to finish and then start the new MIB Batch Compiler.
Reason:
The MIB Batch Compiler was successfully submitted to the background system region but it could not start as the exclusive lock was unavailable. The most likely reason for this is that 2 batch compiles were submitted at the same time and only 1 managed to obtain the lock.
System Action:
This instance of the MIB Batch Compiler does not continue.
User Action:
Ensure the reason for the termination is because another batch compile is already running in the background system region.
Reason:
The parameters passed on a P1 call to to MIB file handler were in error. Either no MIB name was passed, or the MDO containing header information is empty.
System Action:
The request is rejected.
User Action:
Contact your systems administrator.
Reason:
An attempt to compile or delete MIB P1 has failed. The MIB is currently being maintained by user P1.
System Action:
The request is rejected.
User Action:
Wait until the other user has completed his update and try again.
Reason:
An error has occurred on an I/O operation on file P1 .
P2 is the file operation that was attempted.
P3 is the key of the record.
P4 is the message returned by the operation.
System Action:
The request fails.
User Action:
If the cause of the problem is not evident, contact your systems administrator.
Reason:
An error has occurred on an I/O operation on file P1 .
P2 is the file operation that was attempted.
P3 is the return code from the operation.
P4 is the VSAM error code.
P5 is the full or partial key used.
System Action:
The request fails.
User Action:
The error code P4 is the RPLERRCD value returned by the VSAM macro. Look up the RPLERRCD value in the IBM Manual 'DFSMS Macro Instructions for Datasets'. If the cause of the problem is not evident, contact your systems administrator.
Reason:
An attempt to locate MIB P1 has failed. The MIB does not exist in any concatenated MODS file.
System Action:
The request is rejected.
User Action:
None
Reason:
An attempt to select a MODS file in order to access MIB data failed.
P1 shows details of the failure.
System Action:
The request is rejected.
User Action:
Report this error to your systems administrator.
Reason:
An attempt to delete MIB P1 has been rejected. The MIB is not located in the top level of the MODS concatenation. MIBs in lower-level MODS files can be updated/deleted by authorized users only, via the administration panels.
System Action:
The request is rejected.
User Action:
None
Reason:
An attempt to build a list of MIBS failed. An error occurred on a vartable P1 operation. P2 is the feedback from the operation.
System Action:
The request fails.
User Action:
Contact your systems administrator.
Reason:
This is an audit message showing activity on the MIB repository. MIB file P1 had the action P2 issued against it at time P3 on date P4 by user P5 . The MODS file used was P6 .
System Action:
None
User Action:
None
Reason:
An invalid value has been entered in field P1 . Correct values for this field are described in P2 .
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
An attempt was made to add a new attribute with the same name as a pre-existing attribute.
System Action:
The attribute is not added.
User Action:
Change the attribute name and try again.
Reason:
An attribute was successfully stored in the activity MDO.
System Action:
The attribute is added to the activity.
User Action:
None.
Reason:
An attempt was made to define an attribute with an attribute type other than ENUMERATED from a MIB object whose syntax is P1 . Only MIB objects whose syntax is either Counter, Counter32, Counter64, Gauge32, INTEGER or Integer32 can be defined as a non-ENUMERATED type.
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
MIBinsight attribute sampling failed for resource P1 because no IP address could be determined for the resource.
System Action:
MIBinsight attribute sampling fails for this resource.
User Action:
Contact your systems administrator.
Reason:
The sampling application has returned a non-numeric value for an attribute that has been defined as type P1 . Only attributes whose type is ENUMERATED can have non-numeric values.
System Action:
The value is rejected.
User Action:
Review the attribute definition and determine the correct sampling attribute type for the MIB attribute in error.
Reason:
A MIB attribute has returned numerous values for the same resource/ attribute/qualifier combination. The Data Sampling Framework can only cater for one value per qualifier, per sample. The extra sample values are recorded in the transient log for reference.
System Action:
The extra samples are discarded after their value is written to the transient log.
User Action:
Review the attribute definition and determine whether a unique qualifier can be defined for this attribute.
Reason:
A MIB attribute has returned numerous values for the same resource/ attribute/qualifier combination. The Data Sampling Framework can only cater for one value per qualifier, per sample. The extra sample values are recorded in the transient log for reference through message IPMB3403. P1 is the resource name for which multiple values were detected.
System Action:
The extra samples are discarded after their value is written to the transient log through message IPMB3403.
User Action:
View the transient log for resource P1 and review all IPMB3403 messages. You may need to redefine the attributes reported in these messages and give them a qualifier with unique values.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
No selection was made from a group pick list.
System Action:
None.
User Action:
None.
Reason:
You tried to delete an IP node monitor group that is used by IP nodes.
System Action:
The delete request is rejected.
User Action:
Use the LM (List All Members) action to view the IP nodes in the monitor group.
Reason:
You tried to file or save a definition that has not been changed. The requested action is not performed.
System Action:
The definition is not saved again.
User Action:
None.
Reason:
An attempt was made to access a NetMaster for TCP/IP function, but region P1 has not been configured for that product.
System Action:
None.
User Action:
Contact your Systems Administrator. The RUNSYSIN member should be changed to include PROD=TCPIP.
Reason:
The VFS operation identified by P1 failed with FILERC P2 and VSAM feedback code P3 for the VFS key identified by P4 .
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An attempt to open the VFS file failed as the user does not have the authority to access the file.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An attempt to update the VFS database failed as the user does not have update authority.
System Action:
None.
User Action:
Contact your Systems Administrator.
Reason:
The dataset name specified in the Extract Dataset name field either does not exist or is not the right format for an extract dataset.
System Action:
Option not processed.
User Action:
Ensure that the dataset specified has been allocated as a sequential dataset with a record format of VB and a record length of at least 502 bytes.
Reason:
The data entered into the device name field is not the name of an IBM 2216 router defined to this system.
System Action:
Option not processed.
User Action:
Enter the name of a 2216 router (or '?' for a selection list) and retry the operation.
Reason:
The data entered into the Channel Card Name field is not a defined channel card entry.
System Action:
Option not processed.
User Action:
Correct the field, or define the Channel Card, and retry the operation.
Reason:
The selection list was exited without selecting an item.
System Action:
None.
User Action:
None.
Reason:
The requested function is not supported by CA TCPaccess CS.
System Action:
Processing of the function is terminated.
User Action:
None.
Reason:
A requested menu option is not available because the TCP/IP sockets interface is not active.
System Action:
Request is rejected.
User Action:
To start the TCP/IP sockets interface, perform the following steps:
1. Review the SOCKETS Parameter group ( /PARM ). Verify that all the details are correct and then press PF6 to action the group.
2. If actioning the group fails, verify that the associated stack address space is available and completely initialized. Retry and action the parameter group.
Reason:
The selected link name uses TCPaccess as its primary stack but packet tracing using CTRACE is available for IBM stacks only.
System Action:
Request is rejected.
User Action:
For TCPaccess stacks, select a SmartTrace option.
Reason:
The name specified in the Telnet Server Address Space Name field is not the name of a Telnet server defined to NetMaster. A Telnet server running in its own address space must be defined as an ASMON resource of type TNSERVER.
System Action:
Request is rejected.
User Action:
If the named address space is a Telnet server, update the ASMON definition (use /RADMIN.R). If your Telnet server runs as part of the stack address space, use the stack menu (/STACK or /CONFIG).
Reason:
Link P1 represents a backlevel region linked in migration mode. The selected option is not supported on the backlevel region.
System Action:
The request is rejected.
User Action:
Select a different link, or upgrade the remote region to the latest release.
Reason:
The requested function is not available for the indicated stack. The stack is defined to the system image, but the stack resource definition has Monitoring Activity set to OFF.
System Action:
Processing of the function is terminated.
User Action:
To update a STACK resource definition
Reason:
The name, p1, in the Address Space Name field is not the name of a resource defined as a DB2 task. The name must be that of an ASMON resource of the DB2 type.
System Action:
The request is rejected.
User Action:
If the named address space is a DDF task, the resource is defined incorrectly.
To correct the definition
The list of resource definition classes appears.
Reason:
A ? was entered in the Address Space Name field to list the defined DB2 resources, but no resources were found in the p1 system image.
System Action:
The request is rejected.
User Action:
Enter the /RADMIN.R panel shortcut, set the system image, and select ASMON to see what resources are defined.
If your DDF task is listed, update the definition and change the Address Space Monitor Type field on the General Description page to DB2.
If your DDF task is not listed, press F4 (Add) on the Address Space Monitor List to create a resource definition.
Reason:
The value p1 in the Address Space Name field is not the name of a resource defined in the p2 system image.
System Action:
The request is rejected.
User Action:
Enter ? in the Address Space Name field to see a list of defined DB2 resources.
If the name you are looking for is not listed, create the definition.
To create the definition
The list of resource definition classes appears.
The Address Space Monitor List appears.
Reason:
The value p1 in the Address Space Name field is not the name of a resource defined in the p2 system image. The TRS option is available only for resources defined in the system image.
System Action:
The request is rejected.
User Action:
Check that p1 is entered correctly. If so, ask your administrator to add p1 as an ASMON resource of the DB2 type to the p2 system image.
Reason:
p1 does not meet the requirements of a DDF address space name. The name must have the format ssidDIST. Wildcards are not allowed.
System Action:
The request is rejected.
User Action:
Correct the address space name, and retry.
Reason:
The TCP/IP monitor interface procedure $IPNM01Z failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected.
User Action:
Report the error to your technical support representative.
Reason:
The IPMON GROUP keyword specifies a group that is not defined.
System Action:
The request is rejected.
User Action:
Correct the group name entered on the GROUP keyword. If necessary use the TCP/IP Administration Monitor Group List to confirm the groups defined.
Reason:
The recording for a IP node monitor group has been modified. A value of ACTIVE indicates that all sampling for the IP nodes in the group has been started. A value of INACTIVE indicates that sampling will be stopped.
System Action:
The GROUP definition on the IPFILE is updated.
User Action:
Use the IPMON GROUP=name COLLECT=YES|NO command when required to stop or start monitoring.
Reason:
A request to define an SNMP attribute to the IP Node Monitor was invalid. The field passed was P1 and the invalid value for that field was P2.
System Action:
The request is rejected.
User Action:
Ensure that all the required fields have been set and that they are of the correct type.
Reason:
A request to define an SNMP attribute to the IP Node Monitor was invalid. The attribute ID specified is a system defined attribute and cannot be overwritten.
System Action:
The request is rejected.
User Action:
Specify a different attribute ID.
Reason:
A request to define an SNMP attribute to the IP Node Monitor was successfully processed.
System Action:
The attribute is made available for use.
User Action:
None.
Reason:
A request to define an SNMP attribute to the IP Node Monitor failed because a qualifier specification was present but the object ID requested did not have the '.*' qualifier indicator present.
System Action:
The request is rejected.
User Action:
Either specify the '.*' qualifier indicator in the OID field or do not specify the QUALIFIER field. Retry the request.
Reason:
A request to define an SNMP attribute to the IP Node Monitor failed because the object ID had the '.*' qualifier indicator present but a qualifier specification was not present.
System Action:
The request is rejected.
User Action:
Either remove the '.*' qualifier indicator in the OID field or specify the QUALIFIER field. Retru the request.
Reason:
A request to define an SNMP attribute to the IP Node Monitor failed because a qualifier enumerated value set was specified but no qualifier object ID was specified.
System Action:
The request is rejected.
User Action:
Either specify the qualifier object ID or remove the enumerated values for the qualifier.
Reason:
The TCP/IP socket interface did not receive a normal response from the destination host identified by P1 and is deemed unreachable. This occurs for one of the following reasons:
- The specified destination host address is not powered on or does not exist.
- The IP route to the destination address is unusable due to a network outage.
- The packet size exceeds the maximum transmission unit (MTU) size allowed for an IP route.
- The response time wait has been exceeded for a PING or TRACEROUTE.
System Action:
No sample is taken and the NETSTATUS attribute is set to Timeout.
User Action:
Check the existence of the destination host. If you specified a packet size, try reducing the size or increase the response time wait if it is available. Check also that the route to the host is available and the host is active. A TRACERTE command is useful to determine the point where routing fails.
Reason:
A socket request cannot be completed because the TCP/IP sockets interface has terminated or never started.
System Action:
No sample is taken and the NETSTATUS attribute is set to Unknown.
User Action:
To start the TCP/IP sockets interface:
1. Enter /PARMS and review the SOCKETS Parameter group. Verify that all of the details are correct and then press F6 to action the group.
2. If actioning the group fails, verify that the associated stack address space is available and initialized, then action the parameter group.
Reason:
The TCP/IP socket interface returned a TCP/IP socket error where P1 indicates the failing socket request code and P2 describes the monitored attribute.
System Action:
No sample is taken and the NETSTATUS attribute is set to Error.
User Action:
Contact your System Administrator and provide the error details indicated for P2 attribute.
Reason:
The TCP/IP socket interface returned a TCP/IP socket error where P1 indicates the failing socket request code and P2 describes the requested SNMP action. This message is accompanied by an IPSNPK01 error message for a monitored MIB attribute.
System Action:
No sample is taken and the NETSTATUS attribute is set to Error.
User Action:
Contact your System Administrator and provide the error details in IPSNPK01 for a monitored MIB attribute.
Reason:
During sampling of attribute PINGRTT for IPNODE, P1 ended with socket errors.
System Action:
No sample is taken.
User Action:
Contact your System Administrator and advise that a socket PING function ended with errors - RC P2 , Feedback Code P3 and Socket Error P4.
See the NCL Reference for a description of the &SOCKET verb return codes.
Reason:
Data sampling of PINGRTT for IPNODE P1 completed without an MDO map. This is probably due to an error in a socket call.
System Action:
No sample is taken.
User Action:
Contact your System Administrator.
Reason:
IPNODE monitoring of resource P1 failed while attempting a ping. The IP address of the node is IPv6. The ping failed because the current sockets API supports IPv4 addresses only.
System Action:
The PINGRTT attribute for resource P1 is set in error.
User Action:
Check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
The IP node monitor ping sample did not receive responses for all packets. p1 is the percentage of packets that did not receive a response. p2 is the total number of ping attempts.
Packet loss can be an indicator of an overloaded router not being able to process all packets.
System Action:
The NETSTATUS attribute is set to PktLoss.
User Action:
Issue a traceroute against the IP node to determine the routers used to access the host. Review the Mon column for indicators of alerts for monitored routers. If the problem persists, notify your IP network support staff.
Reason:
The PINGRTT source address is not a valid home address for the stack show in P1. The source address is specified as part of the IP node resource definition. This error occurs because of one of the following reasons:
System Action:
The PINGRTT sample fails with a socket error.
User Action:
Determine the cause of the error, and review the value in the Source Address field of the IP node resource definition.
Reason:
During sampling of attribute NoOfHops for IPNODE P1 ended with socket errors.
System Action:
No sample is taken.
User Action:
Contact your System Administrator and advise that a socket TRACEROUTE function ended with errors - RC P2 , Feedback Code P3 and Socket Error P4.
See the NCL Reference for a description of the &SOCKET verb return codes.
Reason:
Data sampling of NoOfHops for IPNODE P1 completed without an MDO map. This is probably due to an error in a socket call.
System Action:
No sample is taken.
User Action:
Contact your System Administrator.
Reason:
IPNODE monitoring of resource P1 failed while attempting a traceroute. The IP address of the node is IPv6. The traceroute failed because the current sockets API supports IPv4 addresses only.
System Action:
The NoofHops attribute is set in error.
User Action:
Check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
Monitoring of the P1 IP node failed while attempting a traceroute. P2 is the error condition returned from the traceroute.
System Action:
The NoofHops attribute is set in error.
User Action:
Review P2 and correct the error.
Reason:
The NoOfHops source address is not a valid home address for the stack show in P1. The source address is specified as part of the IP node resource definition. This error occurs because of one of the following reasons:
System Action:
The NoOfHops sampling fails with a socket error.
User Action:
Determine the cause of the error, and review the value in the Source Address field of the IP node resource definition.
Reason:
The site file (HOSTS.LOCAL) loader utility failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected.
User Action:
Correct your request and retry.
Reason:
The site file (HOSTS.LOCAL) loader utility encountered an invalid HOST statement reading the dataset P2 the invalid address was P1 the line number where it occcurs is P3
System Action:
The address on this entry is ignored.
User Action:
Correct the HOSTS.LOCAL file, reset the loaded data by issuing the $IPNR05Z ACTION=RELOAD command.
Reason:
The site file (HOSTS.LOCAL) loader utility encountered an error while performing the action P1 on the table P2 using key P3.
System Action:
The current entry is ignored.
User Action:
Ensure the HOSTS.LOCAL file is in the correct format and reload the table using the $IPNR05Z ACTION=RELOAD command.
Reason:
The site file (HOSTS.LOCAL) loader utility has loaded entries from the file P3. P1 address entries and P2 NAME entries were loaded, based on the HOST entries in the file.
System Action:
None.
User Action:
None.
Reason:
The site file loader utility failed during request processing because it was passed an invalid keyword value. The keyword was P1 and P2 was the invalid value.
System Action:
The request is rejected.
User Action:
Correct the request and retry the operation.
Reason:
The member containing host table entries does not exist in the TCPaccess configuration parms dataset.
System Action:
None.
User Action:
None.
Reason:
The site file loader utility has successfully loaded host name and address entries from the P3 file. P1 address entries and P2 name entries were loaded based on the HOST entries in the file.
System Action:
None.
User Action:
None.
Reason:
The site file loader utility issued system command P1 to the operating system for execution but the command was rejected.
System Action:
None.
User Action:
None.
Reason:
An unexpected reponse to the TCPaccess TASK command was received. The suffix of the member name containing information for the task P1 could not be determined,
System Action:
The requested action is not processed.
User Action:
Check that the jobname specified in the TCPaccess Job Name field in the TCPaccess Management Interface panel from the TCP/IP : Administration Menu is correct.
Reason:
A recognized response to a Syscmd issued to TCPaccess was not received within the time limit specified. P1 is the command issued.
System Action:
The process terminates.
User Action:
None.
Reason:
A command issued to Tcpaccess failed because the Task/Job P1 is not active.
System Action:
The process terminates.
User Action:
Check that the TCPaccess Job name specified in the TCPaccess Management Interface of the TCP/IP Administration Menu matches the actual TCPaccess job running.
Reason:
A command to determine information about a TCPaccess TASK was not processed by the operating system. Message P1 provides more information about the failure.
System Action:
The process terminates.
User Action:
Determine the cause for failure, correct the problem and retry the operation.
Reason:
A command to determine information about a TCPaccess TASK failed because the group name P1 was invalid or not installed in TCPaccess.
System Action:
The process terminates.
User Action:
Determine the cause for failure, correct the problem and retry the operation.
Reason:
The TCP/IP NETSTAT command handler procedure $IPNS06H failed during request processing because it passed non-keyword parameters.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
The requested maximum number of connections ( P1 ) has been reached but more connections satisfy the criteria. The remaining connections are ignored.
System Action:
None.
User Action:
If more connections are required, increase the Max Connections option and retry.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack field to obtain a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
The message indicates NETSTAT processing has failed. The message, which is also logged, indicates the cause of the failure.
System Action:
None.
User Action:
Check the status of the stack and ensure it is ACTIVE.
Check that the stack definition has been correctly defined and configured.
Check that NETSTAT functionality is enabled for this TCPaccess stack configuration (see the TCPaccess System Administration Guide).
Record the associated error message for problem determination.
Contact your Systems Administrator.
Reason:
An unexpected message ( P1 ) was returned by the NETSTAT message process.
System Action:
The NETSTAT message ( P1 ) is written to the Activity Log where it may be viewed when this message is truncated for display on a panel.
User Action:
Determine the cause for failure, correct the problem and retry the operation.
Reason:
The NETSTAT process for TCPaccess does not support the P1 option specified.
System Action:
Control is returned to the calling procedure.
User Action:
Contact your System Administrator.
Reason:
The specified session has been successfully terminated.
System Action:
None.
User Action:
None.
Reason:
The $IPNETAX subsystem generates and sends Netstat commands which obtain information from TCPaccess. An error occurred in the processing, and an attempt was made to clear the error by stopping and restarting the $IPNETAX subsystem. The recovery attempt failed.
System Action:
The request for information from TCPaccess fails.
User Action:
Use the OCS command "SHOW SUBSYS=$IPNETAX" to diagnose the problem. Determine the cause of the error, and retry the operation.
Reason:
Netstat commands issued to TCPaccess are being traced. Command P1 has been issued. This message marks the start of a group. It will be followed by TCPaccess messages T01NTnnn and TCP/IP services messages IPNS0634 and IPNS0635.
System Action:
None.
User Action:
None - this message is used for debugging purposes only.
Reason:
Netstat commands issued to TCPaccess are being traced. This message is issued in response to return code 4 from $IPNETAX (the TCPaccess Netstat interface subsystem). This indiates that $IPNETAX has returned a group of messages, but there are still more messages to be returned.
System Action:
None.
User Action:
None - this message is used for debugging purposes only.
Reason:
Netstat commands issued to TCPaccess are being traced. This message is issued in response to return code 0 from $IPNETAX (the TCPaccess Netstat interface subsystem). This indicates that $IPNETAX has returned all remaining messages for the request listed in the preceding IPNS0633 message.
System Action:
None.
User Action:
None - this message is used for debugging purposes only.
Reason:
The $IPNETAX subsystem which is used to communicate with TCPAccess stacks is unavailable to this region.
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
The P1 action for the $IPNETAX subsystem failed. The $IPNETAX subsystem is used to communicate with TCPAccess stacks.
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
The user ID identified by P1 is not authorized to issue the SUBSYS command identified by P2 .
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
The $IPNETAX subsystem is in a state of STARTING.
System Action:
The procedure terminates.
User Action:
If the system is heavily loaded, wait and retry the operation, otherwise contact your System Administrator.
Reason:
The selected stack is not active.
System Action:
The request is rejected.
User Action:
Investigate why this stack is inactive.
Reason:
The message indicates NETSTAT processing has failed. The return code is indicated by P1 .
System Action:
Control is returned to the calling procedure.
User Action:
Contact your Systems Administrator.
Reason:
The TCP/IP Netstat command handler procedure failed during request processing because it passed non-keyword parameters.
System Action:
The request is rejected and the procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
The Netstat request handler procedure has attempted to locate the Netstat request server procedure $IPNS08Z to queue a Netstat request to it. The server procedure cannot be located.
System Action:
The Netstat request fails.
User Action:
If the problem, contact Technical Support.
Reason:
The Netstat request handler procedure has attempted to start the Netstat request server procedure $IPNS08Z to process a Netstat request. The start request has failed.
System Action:
The Netstat request fails.
User Action:
If the problem persists, contact Technical Support. Refer to the error messages in the log which preceed this message.
Reason:
The Netstat request handler procedure has queued a Netstat request to the Netstat request server procedure $IPNS08Z, and has not received a reply.
System Action:
The Netstat request fails.
User Action:
If the problem persists, contact Technical Support.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the stack field to obtain a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
An attempt to use the Netstat interface for the indicated stack (P1) has failed. For IBM TCP/IP stacks, the Netstat interface requires the procedure (job) step name (P2). The request has failed for one of the following reasons:
System Action:
The request is rejected.
User Action:
First, check that the stack is correctly defined to ResourceView.
Follow these steps:
Second, if the resource definition is correct, check if the stack is active.
Follow these steps:
Reason:
The specified session has terminated successfully.
System Action:
None.
User Action:
None.
Reason:
This is a message used internally by SOLVE to send requests to be processed by NETSTAT.
System Action:
None.
User Action:
None.
Reason:
A request has been received for a buffer pool display indicating storage usage by IBM's Communications Server. The request has been rejected because this function is not supported by Communications Server.
System Action:
The request is rejected.
User Action:
None.
Reason:
The message indicates Netstat processing has failed and no specific error information is available. The corresponding command responses have been written to the activity log.
System Action:
Netstat request fails.
User Action:
Review the activity log entries for the corresponding command responses to determine the cause of the failure. Correct the problem and retry the request.
Reason:
This is an informational message. It indicates the end of output from a Netstat request.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP NETSTAT server procedure has been started, but during procedure initialization it has detected that another server with the same name is active.
System Action:
The new server procedure terminates.
User Action:
Retry your request. If the problem persists, contact your Systems Administrator.
Reason:
A message was expected from the z/OS UNIX System Services Shell. The receive request which was waiting for the message has timed out.
System Action:
None.
User Action:
None.
Reason:
A command was issued to the z/OS UNIX System Services Shell. All output from the command has now been received.
System Action:
None.
User Action:
None.
Reason:
An attempt has been made to communicate with the UNIX System Services Shell. The request has failed for the reason shown.
P1 shows the request that failed (OPEN, SEND or RECEIVE).
P2 shows the reason for the failure. It could be one of the following values:
storage shortage - A storage shortage has occurred
duplicate ID - The ID specified on OPEN is already in use
unknown ID - The ID specified is invalid
SHELL subtask termination - The shell subtask terminated unexpectedly
buffer overflow - A buffer overflow has occurred
UNIX interface not available - Probably caused by no SSI providing the UNIX service (UNIX=YES)
transport not available - Probably caused by the region not being connected to an SSI.
service not available - Probably caused by the SSI not being available
System Action:
The request fails.
User Action:
Contact your Systems Administrator.
If P1 is SERVICE NOT AVAILABLE, ensure that the:
- SSI settings in Customizer /PARMS are correctly defined.
- SSIPARMS member has UNIX=YES.
Reason:
A attempt has been made to communicate with the z/OS UNIX System Services Shell. The request has failed for the reason shown.
P1 shows the request that was made (OPEN, SEND or RECEIVE).
P2 shows the specific macro call that failed. This value is the system control offset of the macro call that was made, as described in IBM's UNIX System Services Programming: Assembler Callable Services Reference. This value can be used to determine the name of the macro call.
P3 shows the Return Code that was returned by the macro call, as described in the relevant messages and codes guide.
P4 shows the Reason Code that was returned by the macro call, as described in the relevant messages and codes guide.
System Action:
The request fails.
User Action:
Locate the description of the macro call that failed, by using the value given for the System Control Offset. This gives an indication of what the system was trying to do at the time of the error. See IBM's UNIX System Services Messages and Codes guide for more information about the error using the Return Code and Reason Code. If you are unable to determine the nature of the error using this information, contact Technical Support.
Reason:
An attempt has been made to initialize the z/OS UNIX System Sercices Shell. Module NM077 is attached as a subtask and it than attaches the Shell module. The attach of module NM077 has failed.
System Action:
The request fails.
User Action:
Investigate why the load of module NM077 failed. There should be messages in the system log which indicate the reason for the failure.
Reason:
An attempt was made to initialize the z/OS UNIX System Services Shell. The request failed for the reason shown.
P1 shows the specific macro call that failed. This value is the system control offset of the macro call made, as described in IBM's UNIX System Services Programming: Assembler Callable Services Reference. This value can be used to determine the name of the macro call.
P2 shows the Return Code that was returned by the macro call, as described in the relevant Messages and Codes manual.
P3 shows the Reason Code that was returned by the macro call, as described in the relevant Messages and Codes manual.
System Action:
The request fails.
User Action:
Locate the description of the macro call that failed, by using the value given for the System Control Offset. This gives an indication of what the system was trying to do at the time of the error. See IBM's UNIX System Services Messages and Codes guide for more information about the error using the Return Code and Reason Code. If you are unable to determine the nature of the error using this information, contact Technical Support.
Reason:
The TCP/IP NETSTAT server procedure has terminated due to error. This message is sent to the originator of any NETSTAT requests which were queued to the server at the time it had the error.
System Action:
The server procedure terminates.
User Action:
Check the log for additional error messages and correct any problems. Reissue the request. A new server procedure will be started to process the new request.
Reason:
This is a message used internally to indicate that a NETSTAT request has been received by the NETSTAT server procedure.
System Action:
None.
User Action:
None.
Reason:
This message indicates that an error has occurred during processing of a NETSTAT request. No specific error information is available. P1 contains the return code value which was set by the NETSTAT server task.
System Action:
Control is returned to the calling procedure.
User Action:
Refer the error to your Systems Administrator.
Reason:
The message is for information only. It indicates the end of output from a NETSTAT request.
System Action:
None.
User Action:
None.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack field to display a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
An attempt to use the EZBNMIFR API for the indicated stack ( P1 ) has failed. The API requires the procedure (job) step name ( P2 ). The request failed due to one of the following reasons:
- The stack is not active
- The procedure name of the stack is incorrectly defined
System Action:
The request is rejected.
User Action:
Check that the stack is correctly defined to ResourceView. To do this, follow these steps:
1. Enter /RADMIN.R, select STACK resources, and then select the indicated stack.
2. Select the TCP/IP Stack General Description panel.
3. Ensure that the TCP/IP Stack Step Name field is correct. This field is the procname. If this is incorrect, update the resource and retry.
If the resource definition is correct, check if the stack is active. To do this, follow these steps:
1. Enter /IPMON. The Status Monitor : IP Resources dialog appears.
2. If STACK resources are not displayed, use the FILTER command to select a filter that includes stack resources.
3. Check the status using the CHK command.
4. Browse the transient log for the resource using the L command.
5. Review the latest messages and action accordingly.
Reason:
An attempt to retrieve connection details from IBM's EZBNMIFR API has failed. The type of request is shown in P1 . P3 is the return code (errno) and P4 is the reason code (errnojr)
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt to retrieve connection details has failed. The type of operation is shown in P1 . P2 is the return code and P3 is the feedback code.
Some possible return codes and feedback values are:
RC FDBK Explanation
-- ---- -------- ---
12 1 NEXT request rejected, no outstanding GET request
12 2 Prepare MDO failure
12 3 Assign MDO failure
12 4 Connect map failure
12 5 Subtask abend processing this request
12 6 NetMaster region not authorized
12 7 API module EZBNMIFR load failed during initialization
12 8 Interface disabled due to excessive number of abends
12 10 Region shutdown in progress
System Action:
The request is rejected.
User Action:
This is an internal failure. Contact CA Technical Support.
Reason:
The requested maximum number of connections ( P1 ) has been reached but more connections satisfy the criteria. The remaining connections are ignored.
System Action:
None.
User Action:
If more connections are required, increase the Maximum Connections option and retry.
Reason:
You request the result of an NMIFR call by setting &GLBL$NMIFRTRC to YES.
P1 identifies the type of request.
P2 is the ID of the user issuing the call.
P3 and P4 are the return and feedback codes.
System Action:
If any filters are specified, message IPNS1199 follows. A dump of the NMIFR MDO follows.
User Action:
Typically, only CA Support requests this display. To suppress the display, set &GLBL$NMIFRTRC to NO.
Reason:
This message follows IPNS1198 if filters have been passed to the NMIFR verb. P1 identifies the filters.
System Action:
A dump of the NMIFR MDO follows.
User Action:
Typically, only CA Support requests this display. To suppress the display, set &GLBL$NMIFRTRC to NO.
Reason:
While processing the results returned by NetSpy, the size of the data exceeded the MDO size. The display contains incomplete NetSpy data.
System Action:
None.
User Action:
Modify your request by refining your selection criteria.
Reason:
The TCP/IP NETSTAT command handler procedure $IPNS01H failed during request processing because it was passed non-keyword parameters.
System Action:
The request is rejected and procedure $IPNS01H terminates. Control is returned to the NCL procedure which executed $IPNS01H.
User Action:
Contact your System Administrator.
Reason:
The dataset identified by P1 was submitted by the user identified by
P2 for OBEYFILE processing.
System Action:
None
User Action:
None
Reason:
This message identifies the start of the dataset identified by P1 which has been submitted for processing by the OBEYFILE subsystem.
System Action:
None
User Action:
None
Reason:
This message identifies lines submitted for processing by the OBEYFILE subsystem. The message text is identified by P1 .
System Action:
None
User Action:
None
Reason:
This message indicates the end of data lines from the dataset identified by P1 which was submitted to the OBEYFILE subsystem for processing.
System Action:
None
User Action:
None
Reason:
The dataset specified by P1 includes a member name but the dataset is not partitioned.
System Action:
The procedure terminates.
User Action:
Specify the correct dataset or member name.
Reason:
The dataset specified by P2 does not contain the member P1 .
System Action:
The procedure terminates.
User Action:
Specify the correct member or dataset name.
Reason:
The dataset specified by P1 cannot be opened for read access.
System Action:
The procedure terminates.
User Action:
Obtain authority for the SOLVE system to access the dataset.
Reason:
A Packet Trace Clear request has been issued using the OBEYFILE subsystem. The specific IP address P1 is one of the nodes currently being traced.
System Action:
Packet Tracing is stopped - this affects all nodes.
User Action:
Use the Packet Trace menu option from the IP Network Diagnostics menu to perform the following:
- Stop GTF or CTRACE
- Load the trace data
- View traces
Reason:
An OBEYFILE has been processed by TCPIP. The messages returned by TCPIP indicate that an error was detected.
System Action:
The messages returned by TCPIP OBEYFILE command are written to the activity log.
User Action:
Refer to the activity log for the messages returned by OBEYFILE processing.
Reason:
An OBEYFILE has been successfully processed by TCP/IP stack.
System Action:
The OBEYFILE messages are written to the activity log.
User Action:
None
Reason:
The call to the procedure failed because the Keyword identified by P1 had a null value.
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
The result of the P1 action for P2 P3 could not be determined and is deemed to have failed because the process timed out while waiting for a response to the action.
System Action:
The command is not processed.
User Action:
Determine if the action is still valid and retry the command.
Reason:
The P1 action for P2 P3 could not be performed because the TCPaccess job
P4 specified in the TCP/IP Management Interface is not active.
System Action:
The command is not processed.
User Action:
Check that the jobname specified is correct. Restart the job and retry the operation if still appropriate.
Reason:
A request to activate P2 of interface type P1 has been actioned and the activation is now in progress.
System Action:
None.
User Action:
None.
Reason:
A request to activate P2 of interface type P1 has been successfully processed.
System Action:
None.
User Action:
None.
Reason:
The P1 action for P2 P3 failed because the resource does not exist.
System Action:
The command is not processed.
User Action:
Check that the resource specified is correct. Retry the operation if still appropriate.
Reason:
A request to inactivate P2 of interface type P1 has been actioned and the shutdown is now in progress.
System Action:
None.
User Action:
None.
Reason:
A request to inactivate P2 of interface type P1 has been successfully processed.
System Action:
None.
User Action:
None.
Reason:
The requested action for P2 could not be performed because the P1 command was not processed by the operating system. Message P3 provides more information about the failure.
System Action:
None.
User Action:
Determine the cause for failure, correct the problem and retry the operation.
Reason:
The selection list service procedure for the $DSCALL PDS member list displays failed because it received an invalid value for a shared variable. The variable name was P1 and its value was P2 .
System Action:
The selection list service procedure terminates.
User Action:
Contact the System Administrator.
Reason:
An invalid command was entered in the Command field on the panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 pressed on the new member name data entry panel has an invalid command assigned to it.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request was received to rename a dataset or a member of a Partitioned dataset (PDS). When the new name was requested, the user cancelled the function.
System Action:
None
User Action:
None
Reason:
The Selection List service procedure $IPPD38L does not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your System Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPTN30S failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPTN30S terminates.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter ( P2 ) for P1 was omitted from the call to $IPCALL. One of either ADDRESS, HOSTNAME or HOST must be specified.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
An MDO error occurred. The MDO is identified by P1 the map name by P2 the MDO return code by P3 and the feedback code is P4 .
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
A non-numeric value was entered for the field identified by P| .
System Action:
The field is highlighted in error.
User Action:
Correct the field value and repeat the operation.
Reason:
A value was entered for the field identified by P1 which was not in the range specified by P2 and P3 .
System Action:
The field in error is highlighted.
User Action:
Correct the field value and repeat the operation.
Reason:
No entries were returned for display.
System Action:
Control returns to the Primary Menu and the error message is displayed.
User Action:
Correct the entry in the Host name field and retry.
Reason:
An invalid keyword parameter value was passed. The keyword was P1 and the invalid value was P2.
System Action:
Processing terminates.
User Action:
Contact your local technical support representative.
Reason:
An MDO assignment failed with Return Code 16 and Feedback Code 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated during the installation and/or maintenance of this product.
Reason:
An MDO assignment failed. The Return Code was P1 and the Feedback Code was P2. The map and component for which the error occurred was P3.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference manual for details of the codes.
Reason:
An encode or decode request failed. The request was P1, the Return Code was P2 and the Feedback Code was P3. There may be a related message in the log - if so, p4 shows the message ID.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
The field Net Address Mask does not contain a valid IP Address mask. Valid values are:
System Action:
None.
User Action:
Correct the value and retry.
Reason:
An attempt to extract the Channel Path ID for device P1 has failed. The reason is provided in P2. Possible reasons for failure are: DEVINFO RC=aa bb aa is the DEVINFO verb return code, bb is the FDBK. DEVINFO returned multiple CHPIDs more than one CHPID value was returned for the device.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
You are not authorized to perform the action which you attempted. To perform this action you need access (via NPF - the Network Partitioning Facility) to resource P2.P3 in resource group P1
P1 (Table) identifies the type of call that was rejected, either:
- $IPCMD: indicates you are not authorized to use that function
- $IPRES: indicates you can use the function, but not on that resource
P2 (Location) identifies the entity affected by the change, either:
- a domain ID, for changes which affect a NetMaster region
- a stack name or address, for changes which affect a TCP/IP stack
P3 (Resource) identifies the specific resource required
System Action:
The action terminates.
User Action:
Contact your administrator to request the authority required to perform this action.
Reason:
The Application name mapping process was unable to load the data required. P1 was the reason.
System Action:
The action terminates.
User Action:
Correct the indicated problem or look for related log message for more information.
Reason:
This is the last message returned from an SNMP MIB walk request. It indicates that the walk limit has been reached and no more object will be retrieved.
System Action:
None.
User Action:
None.
Reason:
A message was expected from the OS/390 UNIX System Services Shell. The receive request which was waiting for the message has timed out.
System Action:
None
User Action:
None
Reason:
An attempt has been made to communicate with the OS/390 UNIX System Services Shell. The request has failed for the reason shown.
P1 shows the request which failed (OPEN, SEND or RECEIVE).
P2 shows the reason for the failure. It could be one of the following values:
STORAGE SHORTAGE - A storage shortage has occurred
DUPLICATE ID - The ID specified on OPEN is already in use (internal error)
UNKNOWN ID - The ID specified is invalid (internal error)
SHELL SUBTASK TERMINATION - The shell subtask has terminated unexpectedly
BUFFER OVERFLOW - A buffer overflow has occurred
SERVICE NOT AVAILABLE - Probably caused by the SSI not being available
System Action:
The request fails.
User Action:
Contact your system administrator.
Reason:
An attempt has been made to initialize the OS/390 UNIX System Services Shell. The request has failed for the reason shown.
P1 shows the specific macro call which failed. This value is the 'system control offset' of the macro call which was made, as described in the Assembler Callable Services manual for OS/390. This value can be used to determine the name of the macro call.
P2 shows the Return Code which was returned by the macro call, as described in the relevant Messages and Codes manual.
P3 shows the Reason Code which was returned by the macro call, as described in the relevant Messages and Codes manual.
System Action:
The request fails
User Action:
Locate the description of the macro call which failed, using the value given for the System Control Offset. This gives an indication of what was occurring at the time of the error. Refer to the Unix System Services Messages and Codes manual to obtain a description of the error using the Return Code and Reson Code. If you are unable to determine the nature of the error using this information, contact your Support representative.
Reason:
A attempt has been made to communicate with the OS/390 UNIX System Services Shell. The request has failed for the reason shown.
P1 shows the request which was made (OPEN, SEND or RECEIVE).
P2 shows the specific macro call which failed. This value is the 'system control offset' of the macro call which was made, as described in the Assembler Callable Services manual for OS/390. This value can be used to determine the name of the macro call.
P3 shows the Return Code which was returned by the macro call, as described in the relevant Messages and Codes manual.
P4 shows the Reason Code which was returned by the macro call, as described in the relevant Messages and Codes manual.
System Action:
The request fails.
User Action:
Locate the description of the macro call which failed, by using the value given for the System Control Offset. This gives an indication of what the SOLVE system was trying to do at the time of the error. Refer to the Messages and Codes manual to obtain a description of the error using the Return Code and Reason Code. If you are unable to determine the nature of the error using this information, contact your technical support representative.
Reason:
An attempt to locate a TRLE corresponding to chpid P1 has failed.
System Action:
The request is rejected.
User Action:
No TRLE will be found if chpid P1 is not currently in use by this LPAR. If the chpid is in use and this message occurs, contact your systems administrator.
Reason:
The field P1 does not contain a valid home address for the stack shown in P2 .
System Action:
The request is rejected.
User Action:
Correct the value and retry.
Reason:
The field P1 does not contain a valid IP Address.
System Action:
None.
User Action:
Correct the value and retry.
Reason:
A prompt list cannot be displayed for field P1 because no suitable addresses can be found.
System Action:
Field P1 is highlighted in error.
User Action:
Clear field P1 and retry.
Reason:
A prompt list of valid values for field P1 was displayed; however, you did not select a valid value from the list.
System Action:
Field P1 is highlighted in error.
User Action:
Retry the operation or clear field P1.
Reason:
The field P1 contains a valid IP address; however, the IP version (P2) is not acceptable here. Either the sockets API does not support this IP version or there is a mismatch with another IP address specified.
System Action:
The field is highlighted in error.
User Action:
Correct the value and retry.
Reason:
The p1 field has specified invalid TCP ports. p2 gives a more specific reason for the error.
System Action:
The field is set in error.
User Action:
Specify a valid TCP port. This value can be one or more port numbers, or port range specifications separated by a blank or comma. Each port number must be between 1 and 65535. A port range specification is two port numbers separated by a - (dash) or : (colon). The low number must be specified first.
Reason:
The TCP port associations are ambiguous. Protocols P1 and P2 specify the same port numbers or there is an overlap in port ranges. The port specification in error is P3.
System Action:
Field set in error.
User Action:
Specify TCP port to protocol associations that are unambiguous, with no ports associated to more than one protocol.
Reason:
The TCP port associations are ambiguous. Protocol P1 specifies the same port numbers or there is an overlap in port ranges. The port specification in error is P2.
System Action:
Field set in error.
User Action:
Specify a TCP port to protocol association that is unambiguous, with no ports specified more than once.
Reason:
The specified TCP ports are ambiguous. The same port numbers are specified, or there is an overlap in port ranges.
p1 identifies the incorrect port specification.
System Action:
The field set in error.
User Action:
Specify TCP ports that are unambiguous, with no ports specified more than once and no ranges that cover ports specified individually or in another range.
Reason:
The field P3 either does not contain a valid interface name for the IP version P2 or is not an interface for the stack shown in P4.
System Action:
The request is rejected.
User Action:
Correct the value and retry.
Reason:
The socket operation failed because the sockets interface does not support an interface name specification.
Use of the interface name requires running the USS sockets interface.
System Action:
None.
User Action:
Blank out the interface name specification, and retry the operation.
If you want to use the interface name, contact your region administrator to specify USS as the type in the SOCKETS parameter group.
Reason:
You entered an address that is either a Loopback or a Link_Local address. These addresses are not supported as source IP addresses.
System Action:
The operation is not performed.
User Action:
At the Command ===> prompt, enter /PING and enter a ? in the Source Address field. Use one of the listed values.
Reason:
The TCP/IP Services Proactive Monitor was called to edit an alert rule for an unsupported detector type. P1 is the detector type.
System Action:
The add or update request is cancelled.
User Action:
This message should not occur - contact your Systems Administrator.
Reason:
An invalid value was entered.
System Action:
The invalid field is highlighted.
User Action:
Enter active or inactive in the indicated field.
Reason:
The indicated field must be completed.
System Action:
The required field is highlighted.
User Action:
Specify a value in the indicated field.
Reason:
The highlighted field must contain a positive number, with an optional suffix of K (kilobytes), M (megabytes), or G (gigabytes).
System Action:
The field is highlighted.
User Action:
Specify a correct value in the highlighted field.
Reason:
The indicated field must be a time in the form hh:mm
System Action:
The field is highlighted.
User Action:
Specify a time value (hh:mm) in the indicated field.
Reason:
An internal error occurred because the map P1 was not found in the map dataset.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
An internal error occurred. The map P1 experienced the error described by MDORC= P2 and MDOFDBK= P3 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
The conditions for the triggering of the alert must be specified.
System Action:
None.
User Action:
Press F4 and complete the panel to specify criteria.
Reason:
The alert you want to trigger must be specified.
System Action:
None.
User Action:
Press F5 and complete the panel to specify alert details.
Reason:
No link was selected from the displayed list.
System Action:
None.
User Action:
None.
Reason:
The indicated field must contain an IP address mask or an IP address. It can contain an * character at the end to indicate a generic value; otherwise, it must be a valid IP address in the form a.b.c.d.
System Action:
The field is highlighted.
User Action:
Specify a correct IP address value in the indicated field.
Reason:
An invalid value was entered.
System Action:
The invalid field is highlighted.
User Action:
Enter TCP or UDP in the indicated field.
Reason:
P1 is a task or job name. You entered an invalid value. Valid values are:
System Action:
The invalid field is highlighted.
User Action:
Enter a valid value in the indicated field.
Reason:
An invalid value was entered. All channel card log messages begin with IPCP15
System Action:
The invalid field is highlighted.
User Action:
Enter a valid value in the indicated field, or enter a ? to see a prompt list of valid messages.
Reason:
The indicated field must be one of the following:
- a valid FTP command
- an abbreviation, providing the command is uniquely identified
- an asterisk (*) to denote all commands
The following table shows valid values, including the permitted abbreviations:
Command Abbreviations * RETR RET STOR S, ST, STO APPE A, AP, APP DELETE D, DE, DEL, DELE, DELET RENAME REN, RENAM
Note that if an abbreviation is entered it will be saved and displayed as the full command value.
System Action:
The field is highlighted.
User Action:
Specify a correct FTP command value in the indicated field.
Reason:
The indicated field must be either:
- a full dataset name, optionally including a member name in parenthesis for example PROD.FTP.FILE(MEMBER)
- a dataset name prefix followed by an asterisk for example PROD.FTP.FI* or PROD.FTP.*
System Action:
The field is highlighted.
User Action:
Specify a correct dataset name value in the indicated field.
Reason:
P1 must be specified for a valid test condition.
System Action:
None.
User Action:
Enter a valid P1 to create a valid test condition.
Reason:
Either the criteria number P1 is not in the range 1 to 5, or criteria number P1 is not set.
System Action:
None.
User Action:
Correct the expression so that it refers to all used criteria.
Reason:
All used critiera numbers (1 to 5) must be included in the expression.
System Action:
None.
User Action:
Correct the expression so that it refers to all used criteria.
Reason:
The expression is not a valid boolean expression. P1 may contain an error message returned by the boolean expression evaluator.
System Action:
None.
User Action:
Correct the expression.
Reason:
There is a conflict between the extended filter and the message text.
System Action:
The scan text is highlighted in error.
User Action:
Correct message text or extended filter.
Reason:
The indicated field must contain an IPv4 address in the form a.b.c.d.
System Action:
The field is highlighted.
User Action:
Specify a correct IP address value in the indicated field.
Reason:
The indicated field must specify an APPN Partner CP value. Valid formats for this value are:
NWIDxxxx.CPNAMExx
NWIDxxxx.*
NWIDxxxx is the network ID of the APPN partner CP.
CPNAMExx is the CP Name of the APPN partner CP.
NWIDxxxx.* specifies any CP Name on the network.
Alternatively, you can specify a value of all . This event detector then applies to RTP Pipes on all APPN connections, but may result in many alerts. It is recommended to specify these events only for the most critical individual APPN connections.
System Action:
The field is highlighted.
User Action:
Specify a correct APPN Partner CP value in the indicated field or type ? to select from a list of current APPN CPs.
Reason:
The value for the p1 field must be a valid IP network address, not just any IP address. The network address must be one of the standard network classes (a, b, or c) with the host portion zero.
System Action:
The field in error is highlighted.
User Action:
Specify a valid IP network address.
Reason:
The value for the field must contain only alphanumeric characters, or the special characters @, # or $. The first characters cannot be numeric. Additionally, you can specify the mask characters * (representing zero or more unknown characters) or ? (representing exactly one unknown character).
System Action:
The field in error is highlighted.
User Action:
Specify a valid name.
Reason:
The value p1 is not a recognized TCP connection end reason code as defined in the z/OS Communications Server IP Configuration Guide.
System Action:
A prompt list of valid reason codes is presented.
User Action:
Select a valid reason code from the list provided.
Reason:
A prompt list of Interface Names was requested but the Stack Name field did not contain a specific stack name from which the list of interfaces could be obtained.
System Action:
A prompt list of valid reason codes is presented.
User Action:
Specify a specific stack name and retry the prompt list.
Reason:
The criteria for the condition is too broad and could potentially flood the system with alerts. You need to be more specific about which conditions are important.
You must specify at least the indicated number of the filter criteria fields to ensure that the criteria do not capture too many conditions and cause excessive alerts to be created.
System Action:
The filter criteria fields are highlighted in error.
User Action:
Specify at least p1 of the criteria fields highlighted.
Reason:
Stack name p1 is invalid. No stack with this name is defined in this region.
System Action:
The field in error is highlighted.
User Action:
Enter ? in the Stack field to list the defined stacks.
Reason:
A generic value was specified in the Server Host field, which is not allowed.
System Action:
The field is set in error.
User Action:
Specify a specific TCP server host address or name.
Reason:
An ACTIONONLY alert type (Severity 0) has been specified, and there are no defined actions.
System Action:
The event detector is not saved.
User Action:
Modify the event detector to have actions, or set an alert severity of 1 to 4.
Reason:
The TCP/IP Services Proactive Monitor was called to edit an alert rule for an unavailable detector type. p1 is the detector type. To add or update a LINUX, VMEVENT, or VMMSG detector type, the region must have feature LINUXMGMT enabled.
System Action:
The add or update request is canceled.
User Action:
Only add or update available detector types.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
A vartable error occurred. The vartable action was P1 , the feedback code was P2 . If relevant, P3 contains the key value which experienced the problem.
System Action:
The action fails.
User Action:
Determine the cause of the error, based on the feedback code.
Reason:
A vartable add failed because the requested key value already exists.
P1 is the key value.
System Action:
The action fails.
User Action:
Contact your Systems Administrator.
Reason:
An error occurred while connecting to the SSI using EPS. The return code was p1 and the error number was p2.
System Action:
Packet analyzer events are not monitored. The process will retry the connection after a short interval.
User Action:
Check that the SSI is available and connected to this region (see the SSI parameter group). Ensure that the SSI has the correct parameter settings to enable events.
Reason:
An error occurred while trying to receive data from the SSI using EPS. The return code was p1 and the error number was p2.
System Action:
Packet analyzer events are not monitored. The process will retry the connection after a short interval.
User Action:
Check that the SSI is available and connected to this region (see the SSI parameter group). Ensure that the SSI has the correct parameter settings to enable events.
Reason:
An attempt was made to start the monitor but it was already running.
P1 is the detector type.
System Action:
The existing monitor continues.
User Action:
None.
Reason:
The monitor process has been asked to stop.
P1 is the type of detector which is being shut down.
System Action:
The monitor terminates.
User Action:
None.
Reason:
The monitor has started.
P1 is the type of detector.
System Action:
The monitor initializes and begins monitoring.
User Action:
None.
Reason:
An attempt to create an alert failed. The reason is explained in the previous message.
System Action:
Monitoring continues.
User Action:
Refer to the previous message.
Reason:
An attempt to clear an alert failed. The reason is explained in the previous message.
System Action:
Monitoring continues.
User Action:
Refer to the previous message.
Reason:
A socket error occurred. The socket action was P1 , the return code was
P2 , the feedback code was P3 , the error number was P4 - P5 is the name of the error, and the TCPIP vendor specific error code is P6 .
System Action:
The action fails. But recovery is attempted.
User Action:
If the problem persists determine the cause from the error codes and correct the problem.
Reason:
A message was received by the ICMP message processor which is not an IP version 4 packet. This packet is ignored. The first part of the packet is shown in P1 .
System Action:
The message is discarded and processing continues.
User Action:
None.
Reason:
An SNMP GET response message contained an unexpected error indication.
P1 is the error code; possible values are:
1 - too big
3 - bad value
4 - read only
5 - general error.
P2 was the OID requested by the GET opeartion.
P3 was the OID returned in the response.
System Action:
The current test is not performed.
User Action:
Determine and correct the cause of the error.
Reason:
A socket operation has failed because the TCP/IP interface is down.
System Action:
ICMP event detectors wait for the TCP/IP interface to be restarted.
User Action:
The TCP/IP interface is started by the SOCKETS parameter group. Check the parameter group for error messages.
To restart the TCP/IP interface, action the SOCKETS parameter group.
Reason:
Console event detectors cannot operate because the AOM interface has been stopped. AOM is used to intercept console messages.
System Action:
Console event detectors wait for AOM to be restarted.
User Action:
Investigate why AOM is inactive.
To restart AOM, action the OPSYSIDS parameter group.
Reason:
An ARB mode of RED indicates critical flow congestion on an RTP Pipe.
System Action:
The receiver reduces its send rate by 50%.
User Action:
To view information about this RTP pipe, enter the A (Analyze) command next to this alert. From the resulting RTP display, many diagnostic actions are available including the following:
If you have linked CA NetMaster regions, F5 (Remote/Local) toggles between this and the remote end of the pipe.
If you have CA NetMaster NM for SNA running in this region, F10 (Sessions) shows the SNA LU-LU sessions that use this pipe.
To run the RTP Health Check, enter the CH (Check) command next to this alert.
Use the RTP Pipe List (shortcut /RTP) to examine all RTP Pipes.
See all APPN/HPR : RTP Management functions from shortcut /APPNHPR.
If you are only interested in RTP Pipes that use Enterprise Extender, use the EE-specific RTP Pipe List and Health Check (shortcut /EE).
Reason:
The number of current TCP connections between the specified partners has dropped to below the required minimum number, which is p5.
At least p5 TCP connections must exist at all times between these connection endpoints:
The Packet Analyzer has detected one of these connections ending, which has left the number of remaining connections too low.
Connections in any TCP status (not just ESTABLISHED) are counted.
For a minimum connection count of 1, this alert indicates that there are currently no TCP connections between the specified partners.
This alert is raised by a CONNSTAT Packet Analyzer event detector.
System Action:
Business functions that depend on these TCP connections are negatively impacted.
If there are no TCP connections between these end points, then the remote partner has no connectivity or access to the z/OS application.
If there are too few TCP connections between these end points, then application throughput, volume, or other functions can be impaired.
User Action:
Investigate why the TCP connections between these partners ended, were not started, or could not be started. Try and restart the connections.
If there are repeated connection problems, some of these steps can help:
Reason:
Setup of an SSL/TLS connection between the specified partners below has failed in the SSL handshake phase.
This alert is raised by a SSLHFAIL Packet Analyzer event detector.
System Action:
None. The SSL/TLS connection is not established.
User Action:
Ensure that each endpoint supports SSL/TLS.
Some causes of SSL handshake failure include:
Use the /SECURE options to see if there are currently any other successful SSL/TLS connections involving either endpoint.
You can repeat the failing connection attempt while using SmartTrace. This will show the full SSL handshake packet flow, requests and responses.
Reason:
A TCP Reset (RST packet) was sent by TCP server p2:p3 to client p4.
This alert is raised by a SVRRESET Packet Analyzer event detector.
System Action:
None. The TCP connection is terminated.
User Action:
Generally, TCP Server Reset is sent when the TCP server does not like the data it received from the client, such as when there are problems with the handshake or with the application-level protocol.
Use a Connection List to see whether this TCP Server currently has successful connections with any other clients.
Check the TCP Server address space job log, application logs, and system log for any application problems.
If server resets happen repeatedly on a connection, use SmartTrace to see the exact packet flow.
Reason:
A TCP connection between the following partners has ended:
This alert is raised by a TCPEND Packet Analyzer event detector.
System Action:
None.
User Action:
Bring the connection end to the attention of the appropriate group to investigate the area of the specific TCP Connection End reason code.
If the connection should be up all the time, attempt to reconnect.
The reason code can indicate the following conditions:
Reason:
A restricted TCP connection has started, between these partners:
This alert is raised by a TCPSTART Packet Analyzer event detector.
System Action:
None.
User Action:
User action depends on why this connection is significant and why it was specified as being restricted.
It may indicate unexpected activity, or a possible security breach.
Use Connection Lists to see what other connections currently involve either of the connection partners. From this list, you can also drop connections.
Use SmartTrace to view the packet flow and packet content (if not encrypted) on the connection.
Reason:
Network interface p2 on stack p1 is inactive.
This alert is raised by a IFSTATUS Packet Analyzer event detector.
System Action:
None. Connections flowing over the interface are interrupted.
User Action:
Use the diagnostic options at /DEVLINK to investigate the interface failure.
Reason:
The IP packet fragmentation rate for type p3 packets exceeded the specified threshold rate, which is p4 fragmented packets within p5 seconds.
The Packet Analyzer detected this fragmentation on conversations between stack p1 and remote network p2.
High fragmentation can contribute to increased packet loss or packet retransmissions. These conditions in turn can result in increased response times and higher processing load as the end point must reassemble the packets.
System Action:
None.
User Action:
Fragmentation is needed when a datagram is bigger than the physical frame size of the network. The condition can be caused by incorrect sizing of the maximum transmission unit (MTU).
Locate the remote hops for which most datagrams are being fragmented. Frame size is determined by the MTU size. TCP/IP uses the MTU to see if fragmentation is needed.
Consider Implementing Path MTU Discovery
On z/OS, the MTU used for a particular outbound send can vary, depending on the configuration.
If IP traffic from this z/OS stack crosses multiple hops with different MTU sizes, you should enable path MTU discovery (IPCONFIG PATHMTUDISCOVERY). This statement discovers and uses an MTU size that will reach the final hop without needing fragmentation.
(Without path MTU discovery, the send uses the smaller of the interface MTU (from the stack interface physical device links) or the configured route MTU.) Path MTU discovery is usually off by default.
For discussions of MTU considerations and fragmentation considerations, see the IBM z/OS Communications Server IP Configuration Guide.
To see how to use the PING command with the PMTU parameter and large outbound packet lengths to determine the path MTU size to a host, see the IBM z/OS Communications Server IP Diagnosis Guide.
Other Fragmentation Information
The Advanced Connection List (/CONNCF) can list all TCP connections where local or remote fragmentation has been observed.
Stack Performance History (/STKPERF.IP) includes stack-wide performance attributes ipFrag%, ipFragFailed, ipFragFailed%, and ipFragOk.
(This alert is raised by a FRAGMENT Packet Analyzer event detector.)
Reason:
An attempt to connect to the SSI address space to the PAEVENT feature EPS server failed with the return code p1 and optionally, key code p2.
System Action:
Packet Analyzer supported event detectors are not operative. The system will retry the connection after a delay.
User Action:
Ensure that the SSI is running and configured with the Packet Analyzer.
Issue the OCS command SSI STATUS.
The response should contain these messages:
NFST01 PACKET ANALYZER FEATURE IS ACTIVE
NF1003 PACKET ANALYZER VERSION IS 120.01
The Packet Analyzer version must be 120.01 or later. Earlier versions do not support event detectors.
If the SSI is running and configured correctly, then contact Technical Support.
Reason:
The event detectors that rely on the Packet Analyzer (PA) for real-time input are inoperative. The SOLVE SSI cannot be contacted, or there was an error while trying to access the PA event server.
The following event detectors are affected by this condition:
CONNSTAT - TCP Connection Status
FRAGMENT - IP Packet Fragmentation
NOLISTEN - TCP Conn Attempt Fail No Listener Port
SSLHFAIL - SSL Handshake Failure
SVRRESET - TCP Server Connection RESET
TCPEND - TCP Connection Ended
TCPSTART - TCP Connection Started
All existing alerts for these detectors are closed, and no new alerts are raised until the SSI connection has been re-established.
System Action:
Packet Analyzer supported event detectors are not operative. The region keeps retrying the connection at regular intervals.
User Action:
If there is an additional specific message associated with this alert, check the help for that message. This alert is raised if the SSI is shutting down or terminates. The alert automatically closes when the SSI connection is re-established successfully.
Ensure that the SSI is running and configured with the Packet Analyzer. Check the associated text for this alert for indicators of the SSI's status and version, and the Packet Analyzer's processing level.
Issue the OCS command, SSI STATUS, to determine whether the SSI is running and its version. The response contains these messages:
NFST01 PACKET ANALYZER FEATURE IS ACTIVE
NF1003 PACKET ANALYZER VERSION IS 120.01
The Packet Analyzer version must be at least 120.01. Earlier versions do not support event detectors.
The Packet Analyzer level must be at NOSTATS or higher. If the level is not at the maximum, then the SSI STATUS command output contains the following additional messages indicating the current level:
NF1011 PACKET ANALYZER EXECUTION LEVEL IS: NOSTATS
NF1012... PROCESSING. EVENTS: YES PACKETS: YES TRACE: YES STATS: NO P-EVENTS: YES
The NF1012 message must indicate "P-EVENTS: YES" for event detectors to be operative. If this is not the case, change the Packet Analyzer level using one of the following methods. The required minimum level is NOSTATS. Level=FULL is highly recommended.
SSISEND PACTL LEVEL=pa_level
If the SSI is running and configured correctly, then contact Technical Support.
Reason:
An error occurred while attempting to define an event detector to the Packet Analyzer (PA). The specific event detector is inoperative; other detectors are not affected.
p1 identifies the inoperative detector.
All existing alerts for this detector are closed, and no new alerts are raised until the error is resolved.
System Action:
The identified event detector is inoperative and will not detect the desired events.
Error messages describing the error in more detail are written to the activity log.
User Action:
Gather the messages from the activity log, and contact Technical Support.
Reason:
A TCP Reset (RST packet) was sent by stack p1 in response to a SYN request from client p4 because there was no TCP server task listening on p2 port number p3.
This alert is raised by a NOLISTEN Packet Analyzer event detector.
System Action:
None.
The TCP connection fails to establish.
User Action:
When a TCP listener port is not active and clients attempt to connect to that port, the stack automatically sends a reset back to the client, failing the connection attempt.
Continual or multiple occurrences of this failure commonly indicate a misconfigured client, whose server port setting is incorrect.
Check if this server port should be active and in use. If so, start the application task that enables the port listener.
If this server port is deliberately unassigned, check if the client task is misconfigured.
Another possibility is that a client may be deliberately scanning many ports, searching for a server that can be compromised.
If you think this may be happening, alert your network security group to the suspected violation and provide them with details of the client. SmartTrace can be used to trace that client's activity with this LPAR or IP host.
Reason:
Too many SSL Handshake Failure alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has now been disabled.
The number of alerts indicates that excessive numbers of SSL/TLS connections failed during the security negotiation stage.
This alert is raised by alert limit processing for an SSLHFAIL Packet Analyzer event detector.
System Action:
The SSL/TLS connection is not established.
The event detector has been set to INACTIVE, to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the end points of each reported SSL handshake failure.
The Alert Text section of this alert shows the details of the last SSL handshake failure reported by this event detector before it was deactivated.
To see the other failures, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Look for a common cause of the SSL Handshake Failures
Ensure that each end point supports SSL/TLS.
Some causes of SSL handshake failure include:
Use the /SECURE options to see if there are currently any other successful SSL/TLS connections involving either endpoint.
You can repeat the failing connection attempt while using SmartTrace. This will show the full SSL handshake packet flow, requests and responses.
Reason:
Too many TCP server connection RESET alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has been disabled.
The number of alerts indicates that excessive numbers of TCP connections are being reset by the server side of the connection.
This alert is raised by alert limit processing for a SVRRESET Packet Analyzer event detector.
System Action:
The TCP connection is reset.
The event detector has been set to INACTIVE, to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the end points of each reported TCP server connection RESET.
The Alert Text section of this alert shows the details of the last TCP server RESET reported by this event detector before it was deactivated.
To see the other RESETs, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Look for a common cause of the TCP server connection RESETs
Generally, TCP server RESET is sent when the TCP server does not like the data it received from the client, such as when there are problems with the handshake or with the application-level protocol.
Use a connection list to see whether this TCP server currently has successful connections with any other clients.
Check the TCP server address space job log, application logs, and system log for any application problems.
If server resets happen repeatedly on a connection, use SmartTrace to see the exact packet flow.
Reason:
Too many TCP Connection Ended alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has now been disabled.
The number of alerts indicates that excessive numbers of monitored TCP connections have ended.
This alert is raised by alert limit processing for an TCPEND Packet Analyzer event detector.
System Action:
The TCP/IP connection ends.
The event detector has been set to INACTIVE, to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the end points of each reported TCP Connection End.
The Alert Text section of this alert shows the details of the last TCP Connection End reported by this event detector before it was deactivated.
To see the other ended connections, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Look for a reason for the connections ending
Bring the connections ended to the attention of the appropriate group to investigate the area of the specific TCP Connection End reason code (if relevant).
If the connection should be up all the time, attempt to reconnect.
The reason code can indicate the following conditions:
Reason:
Too many restricted TCP Connection alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has now been disabled.
The number of alerts indicates that excessive numbers of restricted TCP/IP connections have been started.
This alert is raised by alert limit processing for a TCPSTART Packet Analyzer event detector.
System Action:
The restricted SSL/TLS connection is started.
The event detector has been set to INACTIVE, to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the end points of each reported TCP Connection Start.
The Alert Text section of this alert shows the details of the last TCP Connection Start reported by this event detector before it was deactivated.
To see the other failures, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Investigate the need for the restricted TCP Connections
This step depends on why these connections are significant and why they were specified as being restricted.
It may indicate unexpected activity, or a possible security breach.
Use Connection Lists to see what other connections currently involve either of the connection partners. From this list, you can also drop connections.
Use SmartTrace to view the packet flow and packet content (if not encrypted) on the connection.
Reason:
Too many Connect attempt rejected alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has been disabled.
The number of alerts indicates that excessive numbers of TCP connection attempts are being reset by the stack due to no listener on the server port.
This alert is raised by alert limit processing for a NOLISTEN Packet Analyzer event detector.
System Action:
The TCP connection fails to establish.
The event detector has been set to INACTIVE, to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the client of each reported TCP connection attempt that was rejected.
The Alert Text section of this alert shows the details of the last TCP connection attempt reported by this event detector before it was deactivated.
To see the other alerts, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Look for a common cause of the TCP connection attempt rejections
When a TCP listener port is not active and clients attempt to connect to that port, the stack automatically sends a reset back to the client, failing the connection attempt.
Continual or multiple occurrences of this failure commonly indicate a misconfigured client, whose server port setting is incorrect.
Check if this server port should be active and in use. If so, start the application task that enables the port listener.
If this server port is deliberately unassigned, check if the client task is misconfigured.
Another possibility is that a client may be deliberately scanning many ports, searching for a server that can be compromised.
If you think this may be happening, alert your network security group to the suspected violation and provide them with details of the client. SmartTrace can be used to trace that client's activity with this LPAR or IP host.
Reason:
Too many IP Packet Fragmentation alerts were opened at once by the p1 event detector p2.
Its Active Alert Limit is p3.
As a safety measure, this event detector has now been disabled.
The number of alerts indicates that an excessive and/or prolonged rate of packet fragmentation is occurring.
High fragmentation can contribute to increased packet loss or packet retransmissions. These conditions in turn can result in increased response times and higher processing load as the end point must reassemble the packets.
This alert is raised by alert limit processing for an FRAGMENT Packet Analyzer event detector.
System Action:
The event detector has been set to INACTIVE to prevent additional alerts from flooding the Alert Monitor.
All the previous alerts opened by this event detector have been closed. They can be viewed using the Alert History.
User Action:
Step 1. Review all the alerts that were reported by this event detector
These alerts show the details of reported packet fragmentation.
The Alert Text section of this alert shows the details of the last fragmentation event reported by this event detector before it was deactivated.
To see the other fragmentation events, use the Alert History.
To review the exact criteria for this event detector, use /EDETECT.
Step 2. Look for a common cause of the packet fragmentation
Fragmentation is needed when a datagram is bigger than the physical frame size of the network. The condition can be caused by incorrect sizing of the maximum transmission unit (MTU).
Locate the remote hops for which most datagrams are being fragmented. Frame size is determined by the MTU size. TCP/IP uses the MTU to see if fragmentation is needed.
Consider Implementing Path MTU Discovery
On z/OS, the MTU used for a particular outbound send can vary, depending on the configuration.
If IP traffic from this z/OS stack crosses multiple hops with different MTU sizes, you should enable path MTU discovery (IPCONFIG PATHMTUDISCOVERY). This statement discovers and uses an MTU size that will reach the final hop without needing fragmentation.
(Without path MTU discovery, the send uses the smaller of the interface MTU (from the stack interface physical device links) or the configured route MTU.) Path MTU discovery is usually off by default.
For discussions of MTU considerations and fragmentation considerations, see the IBM z/OS Communications Server IP Configuration Guide.
To see how to use the PING command with the PMTU parameter and large outbound packet lengths to determine the path MTU size to a host, see the IBM z/OS Communications Server IP Diagnosis Guide.
Other Fragmentation Information
The Advanced Connection List (/CONNCF) can list all TCP connections where local or remote fragmentation has been observed.
Stack Performance History (/STKPERF.IP) includes stack-wide performance attributes ipFrag%, ipFragFailed, ipFragFailed%, and ipFragOk.
Reason:
This general diagnostic message contains variable information.
System Action:
None.
User Action:
Gather all related messages, and send them to Technical Support.
Reason:
You have selected the P1 action for an alert, but the resource associated with the alert is not part of an active system image, so the P1 action is not available.
System Action:
The action terminates.
User Action:
Select another action.
Reason:
The Alert ClassId < P1 > cannot be matched during AlertRule_Get processing of the Alert Monitor Callback package.
System Action:
Processing terminates.
User Action:
Contact Technical Support.
Reason:
The SmartTrace definition P1 had the action P2 issued against it by user P3. If the action was invoked using a line command from a connection list or resource monitor, P4 shows the internal SmartTrace definition name.
The message provides an audit trail of SmartTrace activity.
System Action:
None.
User Action:
None.
Reason:
An attempt to read saved SmartTraces from IPFILE failed. P1 is the error message received on the READ.
System Action:
Processing continues. Saved traces are not available.
User Action:
For more information, see the explanation for message P1. If the condition continues, contact Technical Support.
Reason:
An attempt to save a SmartTraces to IPFILE failed. P1 is the error message received from the WRITE.
System Action:
The save fails.
User Action:
For more information, see the explanation for message P1.
Reason:
An unexpected error has occurred in VARTABLE processing.
P1 is the VARTABLE name
P2 is the VARTABLE request type
P3 is the key for the entry
P4 is the feedback value for the operation
System Action:
The previous display ends.
User Action:
Retry the operation. If the problem continues, contact Technical Support.
Reason:
An attempt to read a saved trace record from IPFILE failed. P1 is the trace name.
System Action:
The procedure fails.
User Action:
If this condition continues, contact Technical Support.
Reason:
An attempt to perform an action on a saved trace failed. P1 is the action. This action does not apply to a saved trace.
System Action:
The action fails.
User Action:
Select another action or another trace.
Reason:
An attempt to view packets for an active trace has failed. The trace currently contains no packets.
System Action:
The action fails.
User Action:
Wait until some packets have been traced.
Reason:
An attempt to decode a packet for viewing has failed. P1 contains the error message from the decode process.
System Action:
The action fails.
User Action:
For more information, see the P1 message.
Reason:
An attempt to read a set of packets failed because the starting or ending sequence number P2 provided with the request is invalid. The sequence numbers must both exist in the same buffer (initial or main buffer) and the ending sequence number must be greater than the starting sequence number.
System Action:
The action fails.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An attempt to inactivate or delete a trace has failed. Either the trace does not exist or it is inactive.
System Action:
The action fails.
User Action:
None.
Reason:
An attempt to activate a trace has failed. The trace is already active.
System Action:
The action fails.
User Action:
None.
Reason:
This message confirms the activation or inactivation of a trace.
System Action:
None.
User Action:
None.
Reason:
Packet Tracing is unavailable for one of the following reasons:
System Action:
None.
User Action:
Check the status of the SSI region.
If the SSI is active, check why it is not running with the SSI parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, we recommend that you always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by CA Support.
Reason:
An attempt to activate a trace failed. The current utilization of the trace database in the SSI is above 80%, at which point any new trace requests are rejected.
System Action:
The action fails.
User Action:
To see the current SSI trace database size, use /IPTEST.
To free space in the trace database, delete any ACTIVE or ENDED trace that is no longer required.
If this condition occurs frequently, consider increasing the database size on the next restart of the SOLVE SSI region. The database size is set by SSI startup parameter, PTRCDBSIZE.
Reason:
An action against SmartTrace definition P1 has been rejected because the definition is not owned by this region.
System Action:
The action fails.
User Action:
None.
Reason:
An action against SmartTrace definition P1 has failed because the definition does not exist.
System Action:
The action fails.
User Action:
None.
Reason:
An attempt to activate SmartTrace definition P1 failed because the trace definition specifies invalid criteria. P1 shows details of the criteria in error.
System Action:
The action fails.
User Action:
Review the criteria and modify as required.
Reason:
The definition for a selected trace was not available for viewing because of one of the following reasons:
System Action:
For a selected trace that has just expired, the list is refreshed.
User Action:
None.
Reason:
An internal request to retrieve the related action record for trace definition P1 failed because the record does not exist in IPFILE.
System Action:
Processing continues. The trace definition is activated with no possibility of the related actions being executed.
User Action:
Review the activity log for earlier messages with a prefix of IPPT63* that may indicate some VSAM file error processing. If none are found, either redefine the actions for this trace, or update and save the definition with no actions defined.
Reason:
An unrecoverable error for an internal request to retrieve SmartTrace action records for trace definition P1 has occurred.
System Action:
Processing terminates.
User Action:
Review the activity log for messages with a prefix of IPPT63* that may indicate some VSAM error processing and take appropriate action. If none are found, either redefine the actions for this trace, or update and save the definition with no actions defined.
Reason:
You activated a SmartTrace; however, the stack you want to trace is inactive. Packet tracing will commence when the stack starts.
System Action:
None.
User Action:
None.
Reason:
You activated a SmartTrace; however, the stack you want to trace is not being processed by the packet analyzer. Tracing will start when the stack is enabled to the packet analyzer.
System Action:
None.
User Action:
Investigate why the stack is not being processed by the packet analyzer. Possibly it was disabled using a STACK UNHOOK command to the SSI. Alternatively, there may have been a failure in the packet analyzer. Look for error messages in the JESMSG log in the SSI region.
Reason:
The export operation finished.
P1 is the total number of packets exported.
P2 is the number of packets truncated.
P3 is the number of packets not traced due to storage shortage.
P4 is the maximum length encountered for a physical packet.
Note: The truncation may be due to the following:
- The logical record length (LRECL) of the Physical Sequential (PS) data set is smaller than the saved packet length.
- The saved packet size is bigger than 64 KB. The part of the packet that fits is exported.
- The CTRACE trace includes packets already truncated by the CTRACE function.
- The user that performed the export does not have read authorization for SmartTrace. The data portion is stripped of TCP and UDP packets.
For details on packets not traced due to storage shortage, see the IPPT5019 message.
System Action:
None.
User Action:
None.
Reason:
The selected trace open failed. P1 is the reason.
For more information, check the Activity Log for message IPPT0429.
System Action:
None.
User Action:
Ensure that the trace instance exists. If the problem persists, contact Technical Support.
Reason:
Errors are detected in the panel input field; P1 is the explanation.
For the Dataset or HFS file field, P1 provides the following explanation:
Indicates that null text is specified in the field.
Indicates that the specified text is not an HFS file name.
Indicates that the specified text does not conform to HFS path-naming rules.
Indicates that the specified text does not conform to HFS file-naming rules.
Indicates that the specified text does not contain a qualified DSN.
Indicates that this is a copy of the Dataset Services messages generated when an I/O operation fails.
Indicates that the specified name points to a data set that is not of physical sequential organization.
Indicates that the specified name points to the member of a partitioned data set that is not supported for export operation.
Indicates that the specified name points to a data set that is not of variable (blocked or unblocked) format and the output is in libpcap format.
Indicates that the specified name points to a data set that is not of variable blocked format and the output is in CTRACE format.
Depending on the output format, it indicates that the output data set logical record length is less than required minimum:
27994 bytes for CTRACE
2056 bytes for LIBPCAP
Indicates that the CTRACE output points to a data set with a logical record length that is not at least four bytes less than the physical block length.
For the Target Time Zone field, P1 provides the following explanation:
Indicates that the specified sign is not blank, -, or +.
Indicates that the specified value is not of the format, hh:mm.
Indicates that the field specified an offset bigger than 12:00.
Indicates that the field specified a minutes offset that is not 00 or 30.
System Action:
None.
User Action:
Correct the indicated error and retry the operation.
Reason:
The trace export file failed to open. P1 is the reason.
Check the help for the message quoted in P1. If the reason quotes message N16C82 PATH NOT FOUND, it is most likely that the region does not have the level of security authorization required to access the File/Dataset in write mode.
System Action:
None.
User Action:
Check the MVS system log for Security System messages relating to the File/Dataset in question.
You may need to contact your Security Administrator. If the problem persists, contact Technical Support.
Reason:
The trace close failed; export finished. P1 is the reason.
For more information, check the Activity Log for message IPPT0429.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The export file close failed, it may be usable.
P1 is the reason. For more informatin, check the Activity Log for message IPPT0429.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The trace instance read failed. The export operation terminated. Some packets may have been exported.
P1 is the RC.
P2 is the feedback code.
P3 is the reason.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The trace export failed. The export operation terminated. Same packets may have been exported.
P1 is the reason. For more information, check the Activity Log for message IPPT0429.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
An attempt to read a saved trace record from IPFILE failed. P1 is the trace instance name.
System Action:
The procedure fails.
User Action:
If this condition persists, contact Technical Support.
Reason:
An attempt to read saved packets from IPFILE failed. P1 is the error message received on the READ. Some packets may have been exported.
System Action:
Processing terminates.
User Action:
For more information, see the explanation for message P1. If the condition persists, contact Technical Support.
Reason:
An attempt to read a set of packets failed because the starting or ending sequence number P2 provided with the request is invalid. The sequence numbers must both exist in the same buffer (initial or main buffer) and the ending sequence number must be greater than the starting sequence number. Some packets may have been exported.
System Action:
The action fails.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An attempt to decode a saved packet failed. P1 contains the error message from the decode process. Some packets may have been exported.
System Action:
The action fails.
User Action:
For more information, see the P1 message.
Reason:
An internal error was detected. P1 describes the error, P2 may contain additional information. Some packets may have been exported.
P1 - Error in UNIX time conversion, P2 -input time in hexadecimal.
System Action:
The export operation terminates. Some packets may be exported.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An attempt to read saved packets from CTRACE failed. P1 is the error message received. Some packets may have been exported. For more information, Check the Activity Log for message IPPT0429.
System Action:
Processing terminates.
User Action:
For more information, see the explanation for message P1. If the condition persists, contact Technical Support.
Reason:
Trace selected for export exceeds supported size of 32767 packets.
P1 is the number of packets in the selected Trace Instance.
System Action:
Processing terminates.
User Action:
Try to define a trace that produces less packets.
Reason:
There is a conflict between specified paramaters.
P1 is the first parameter.
P2 is the second parameter.
Possible reasons for conflict:
- Exporting Trace in CTRACE output format to HFS
- Exporting CTRACE Trace in CTRACE output format
- Specifying Time Zone Adjustement for CTRACE output format
System Action:
Processing terminates.
User Action:
Resolve the conflict and retry.
Reason:
User P1 is performing a trace export; however, they do not have sufficient authority.
SmartTrace authority provides partial export functionality and packet view authority provides full export functionality. TCP and UDP data portions are not exported for SmartTrace authority.
System Action:
Processing terminates.
User Action:
Contact your Security Administrator if you need a higher authority.
Reason:
The export operation terminated due to the input/output error.
P1 is the error
P2 is the error packet number
P3 is the message accompanying the error Check Activity Log for message IPPT0429, which contains full text of P2 .
Note: If the number of packets reported by message IPPT0429 is greater than 0, the output is most likely usable.
System Action:
None.
User Action:
None.
Reason:
This is a description of the trace exported:
P1 is the output dataset or HFS file name.
P2 is the trace name, if present.
P3 is the trace description, if present.
System Action:
None.
User Action:
None.
Reason:
Trace export received packets already truncated. P1 is the number of truncated packets received.
System Action:
None.
User Action:
Check why the trace contained truncated packets.
Reason:
Some packets may have been truncated due to the security limitations, that is, lack of packet-browsing authorization. TCP and UDP packets are exported without the data portion.
System Action:
None.
User Action:
Contact your Security Adminstrator for full SmartTrace authorization.
Reason:
The trace export received packets marked in error. P1 is the number of packets received in error.
System Action:
None.
User Action:
Check the input trace for more information about packets in error.
Reason:
This message gives more information following several panel-only message indicating errors. It indicates that the export operation terminated due to error P1.
P1 is the error description.
P2 is the error Return Code.
P3 is the error Feedback Code.
P4 is the message accompanying the error.
If any packets were exported, this message may be followed by messages IPPT0400 and IPPT0420.
System Action:
None.
User Action:
None.
Reason:
User P1 is generating trace reports; however, they do not have sufficient authority to generate TCP Data Flow Reports.
System Action:
Processing continues; however, trace reports do not contain any TCP Data Flow reports.
User Action:
Contact your Security Administrator if you need a higher authority.
Reason:
A Packet Analyzer request to the SOLVE SSI failed. The message includes the following details:
P1 is the EPS request type, for example Connect, Send, Receive.
P2 is the EPS error number.
P3 is an explanation of the EPS error number.
System Action:
The request fails.
User Action:
Use the EPS Error Number and Reason to determine the error:
This indicates that the connection between this region and the SSI region is not active. Use the $LOG command to check the activity log for related messages.
Use the $NM SSI Customizer parameter group to restart the SOLVE SSI.
For all other errors, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because of an invalid connection ID. The message includes the following:
P1 is the EPS verb name that was issued when the error was detected.
P2 is the EPS connection ID.
P3 is the SSID that identifies the SOLVE SSI region.
P4 is the system name where the region is running.
P5 is the NCLID of the process.
This message corresponds to an EPS error number 81.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because the SSI region cannot be contacted or does not include support for the packet analyzer. The SSID (P1) and system (P2) identify the SSI region where the request is issued. This can be the local SSI region or a remote region, possibly on another LPAR.
This message corresponds to EPS error numbers 39 and 70.
System Action:
The request fails.
User Action:
Check the following in the region running on P2:
Ensure that Packet Analyzer support is enabled by specifying PKTANALYZER=YES.
Also ensure that the parameters include PALEVEL=FULL.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Note: Only one SOLVE SSI region (per LPAR) can include support for the packet analyzer.
Reason:
A Packet Analyzer request to the SOLVE SSI did not complete in a reasonable time. The SSID (P1) and system (P2) identify the SSI region where the request is issued to obtain or store data. This can be the local SSI region, or a remote region, possibly on another LPAR.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
The import operation ended.
P1 is the total number of packets read.
P2 is the number of packets written.
System Action:
None.
User Action:
None.
Reason:
The output trace open failed.
P1 is the reason.
For more information, see the Activity Log for message IPPT0529.
System Action:
None.
User Action:
If the problem persists, contact Technical Support.
Reason:
Errors are detected in the panel input field; P1 is the explanation.
Indicates that null text is specified in the field.
For the Dataset or HFS file field, P1 provides the following explanation:
Indicates that null text is specified in the field.
Indicates that the specified text is not an HFS file name.
Indicates that the specified text does not conform to HFS path-naming rules.
Indicates that the specified text does not conform to HFS file-naming rules.
Indicates that the specified text does not contain a qualified DSN.
Indicates that this is a copy of the Dataset Services messages generated when an I/O operation fails.
Indicates that the specified name points to a data set that is not of physical sequential organization and is not HFS.
Indicates that the specified name points to the member of a partitioned data set that is not supported for import operation.
Indicates that the specified name points to a data set that is not of variable (blocked or unblocked) format.
System Action:
None.
User Action:
Correct the indicated error and retry.
Reason:
The trace import file failed to open. P1 is the reason.
Check the help for the message quoted in P1. If the reason quotes message N16C82 PATH NOT FOUND, it is most likely that the region does not have the level of security authorization required to access the file or data set in write mode.
System Action:
None.
User Action:
Check the MVS system log for Security System messages relating to the file or data set in question.
You may need to contact your Security Administrator. If the problem persists, contact Technical Support.
Reason:
The trace close failed; import ended.
P1 is the record number.
P2 is the return code.
P3 is the feedback code.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The import file close failed.
P1 is the reason.
For more information, see the Activity Log for message IPPT0529.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The trace read failed. The import operation terminated. Some packets may have been imported.
P1 is the RC, if applicable
P2 is the feedback code, if applicable.
P3 is the reason.
System Action:
None.
User Action:
If the situation persists, contact Technical Support.
Reason:
The import cannot proceed because the input file is not in the libpcap format. Libpcap files must have a header as the first record. The first four bytes of the header record must be X'A1B2C3D4' or X'D4C3B2A1'. This file does not contain either value.
System Action:
The import does not proceed.
User Action:
Verify that the file name correctly identifies a libpcap file. If the file is transferred using FTP, specify the binary option.
If you believe the file is in libpcap format, contact Technical Support.
Reason:
An attempt to read trace file failed.
P1 is the error message received on the READ.
Some packets may have been imported.
System Action:
Processing terminates.
User Action:
For more information, see the explanation for message P1.
If the condition persists, contact Technical Support.
Reason:
Writing trace record failed.
P1 is the record number.
P2 is the return code.
P3 is the feedback code.
System Action:
The action fails.
User Action:
Check the integrity of your trace list file.
If the problem persists, contact Technical Support.
Reason:
The import operation terminated due to error.
P1 is the error.
P2 is the error packet number.
P3 is the message accompanying the error.
Unless the error is INTERR, check the Activity Log for message IPPT0529, which contains the full text of P2.
Note: If the number of packets reported by message IPPT0529 is greater than 0, the output is most likely usable.
System Action:
None.
User Action:
Correct the situation using information provided in message IPPT0529. Contact Technical Support with log entries if the error is INTERR. You may be asked to provide the trace file you tried to import.
Reason:
The following is a description of the trace imported:
P1 is the input data set or HFS file name.
P2 is the trace name.
P3 is the trace description.
System Action:
None.
User Action:
None.
Reason:
Trace import received packets already truncated.
P1 is the number of truncated packets received.
System Action:
None.
User Action:
Examine why the trace contained truncated packets.
Reason:
This message gives more information following several panel-only message errors. It indicates that the import operation terminated due to error P1.
P1 is the error description.
P2 is the error Return Code.
P3 is the error Feedback Code.
P4 is the message accompanying the error.
If any packets were imported, this message may be followed by messages IPPT0500 and IPPT0520.
System Action:
None.
User Action:
None.
Reason:
No trace definitions are defined on the system.
System Action:
None.
User Action:
Press F4 (Add) to add a new trace definition.
Reason:
The trace definition P1 was deleted. All unsaved traces for this definition were also deleted.
System Action:
None.
User Action:
None.
Reason:
There are no traces for the trace definition. This may be due to the following:
- The definition is not active.
- The definition is active and it contains a specific filter for one or more stacks; however, none of the stacks are active.
- The definition is active, it contains a stop condition and all the traces for the stacks have hit the stop condition, and the resulting traces have subsequently expired. To restart the trace, inactivate and then activate the definition.
- The definition is inactive and all traces have been deleted or have expired.
- The definition is inactive and all traces have been deleted due to an SSI restart.
Note: Saved traces cannot be deleted by restarting the SSI.
System Action:
None.
User Action:
Do one of the following:
- If the trace definition is not active, no traces are created. Activate the trace definition using the A action.
- If the trace definition is active and it is a TCP connection trace, traces appear only when a connection matching the criteria is established.
- If the trace definition specifies specific stacks, a trace appears only when the stacks are active.
- If the definition has a stop condition and that condition has been met, restart the stacks or inactivate and re-activate the definition.
Reason:
The value entered is not a valid dataset name nor is it a valid HFS file path and name.
System Action:
Field is set in error.
User Action:
Specify a valid dataset name or a valid HFS file path and name.
Reason:
The value entered is not a valid time offset value.
System Action:
Field is set in error.
User Action:
Specify a valid time offset of the form + or -, followed by the number of hours and a colon (:), and then 30 or 0 minutes. You can specify equals (=) to use the system's local time offset.
Reason:
The value entered is not a valid dataset name or a valid HFS file path and name.
System Action:
Field is set in error.
User Action:
Specify a valid dataset name or a valid HFS file name.
Reason:
You cannot access the trace definition with the action P1. This action is reserved for trace definitions created manually using the A (Add SmartTrace Definition; shortcut TRADD ) menu option from the
TCP/IP : Packet Tracing Menu (shortcut /SMART ).
System Action:
Field is set in error.
User Action:
Choose a different action for the selected trace definition.
Reason:
There are no traces on stack P1 for definition P2.
System Action:
None.
User Action:
If the trace definition is not active, no traces are created. Activate the trace definition using the A action.
If the trace definition is active and it is a TCP connection trace, traces appear only when a connection matching the criteria is established.
Reason:
There are no traces for P1.
System Action:
None.
User Action:
Ensure that the PT command has been issued for P1. If it has, wait for packets that match the PT command's criteria to appear.
Reason:
The PT command has not been issued for P1; therefore, no traces are displayed.
System Action:
None.
User Action:
Ensure that the PT command has been issued for P1.
Reason:
There is no active tracing for P1, although saved traces do exist.
System Action:
None.
User Action:
None.
Reason:
The number of records to skip is invalid. P1 must be an integer and represent the number of records to skip forward or back.
System Action:
Field set in error.
User Action:
Specify a valid number or blank to get the default value of 1.
Reason:
You cannot skip the requested number of records because there are insuffficient records.
System Action:
The last record in the trace appears.
User Action:
None.
Reason:
You cannot skip back the requested number of records because there are insufficient records.
System Action:
The first record in the trace appears.
User Action:
None.
Reason:
To add a new SmartTrace definition, you can select this line or press F4 (Add).
System Action:
None.
User Action:
Select the message line or press F4 (Add) to add a new SmartTrace definition.
Reason:
No traces exist that match the criteria that you entered.
System Action:
The trace definition list is not presented.
User Action:
If a trace has been activated recently, ensure that the correct Link Name is specified. Enter ? to display the names of all linked systems.
Reason:
There are currently no EE traces to list.
System Action:
None.
User Action:
None.
Reason:
The value entered for the output format is invalid.
System Action:
Field is set in error.
User Action:
Specify a valid output format of LIBPCAP or CTRACE.
Reason:
When this trace was collected, a packet that should have been traced could not be captured because there was insufficient storage in the SSI's trace database.
System Action:
This packet is not traced.
User Action:
If the trace is active, delete some other ACTIVE or ENDED traces to free space in the trace database and reduce the risk of future packets being missed.
If this message occurs frequently, consider increasing the database size on the next restart of the SOLVE SSI region. The database size is set by SSI startup parameter, PTRCDBSIZE.
Reason:
The value entered is not a valid time offset value. The sign must be + or - (+ is assumed if a sign is omitted). The hours must be between 0 and 12. The minutes must be exactly 30 or 0.
System Action:
Field is set in error.
User Action:
Specify a valid time offset of the form + or -, followed by the number of hours and a colon (:), and then 30 or 0 minutes. You can specify equals (=) to use the system's local time offset.
Reason:
The value entered is out of range. The time offset must range from -12:00 to +12:00 in increments of 30 minutes.
System Action:
Field is set in error.
User Action:
Specify a valid time offset of the form + or -, followed by the number of hours and a colon (:), and then 30 or 0 minutes. You can specify equals (=) to use the system's local time offset.
Reason:
The print request was submitted to the background because it can take a while to print so many packets. When the print is complete, a notification is sent.
System Action:
None.
User Action:
None.
Reason:
The print request completed successfully and the output was sent to the printer.
System Action:
None.
User Action:
None.
Reason:
The print request for trace P1 failed. An accompanying message gives the reason.
System Action:
Print request aborted.
User Action:
Check the accompanying message for an action.
Reason:
When this trace was collected, all packets that should have been traced could not be captured because there was insufficient storage in the SSI's trace database.
System Action:
None.
User Action:
If the trace is active, delete some other ACTIVE or ENDED traces to free space in the trace database and reduce the risk of future packets being missed.
If this message occurs frequently, consider increasing the database size on the next restart of the SOLVE SSI region. The database size is set by SSI startup parameter, PTRCDBSIZE.
Reason:
The DECODE command prompting has terminated because the current list is filtered on Port P1 that is being decoded as P2. This occurs because of one of the following reasons:
System Action:
Processing terminated.
User Action:
If prompting terminated because of the first reason, issue the DECODE P2 CLEAR command to stop decoding so that Port P1 can be decoded using another protocol. Reissue the DECODE command.
The second reason indicates that Port P1 cannot be decoded with any other protocol. If required, you can refresh the display temporarily without the decoded information by issuing the TCPSUMM command.
Reason:
A command has failed because the target linked region is of an earlier version that does not support the command.
System Action:
The command is rejected.
User Action:
None.
Reason:
The TAGCLR command found no tags to clear.
System Action:
None.
User Action:
None.
Reason:
The TAGCLR ALL command has cleared all existing tags.
System Action:
None.
User Action:
None.
Reason:
The TAGCLR command has cleared tag P1.
System Action:
None.
User Action:
None.
Reason:
The TAGCLR command is rejected because an invalid tag number was specified.
System Action:
The command is rejected.
User Action:
Reissue the command with a valid tag number (1 to 9).
Reason:
The P1 command was terminated because you do not have authority to view packet data. Your viewing of packets are limited to the IP and protocol headers.
System Action:
The command is terminated.
User Action:
Contact your security administrator.
For information about SmartTrace security requirements, see the Security Guide.
Reason:
The DECODE command has been disabled as the required internal tables for port decoding is either corrupted or could not be located.
System Action:
Command processing is terminated.
User Action:
Contact Technical Support for assistance in restoring the internal table.
Reason:
A request to export a trace will be processed without the packet payload data because of insufficient authority.
SmartTrace security has two levels of authority. Full authority permits a user to define, delete, start and stop tracing, export, and view all contents of a traced packet. Partial authority has a similar scope, but the user cannot view the payload data of any traced packet. For TCP and UDP packets, any data that follows the TCP or UDP header is removed.
System Action:
None.
User Action:
If full authority is required, contact your security administrator.
Reason:
No traces exist that were created by a PT command against a resource for the selected system. If traces were previously activated, they are deleted if not referenced or saved after a certain period.
You can activate a trace using the PT command as follows:
System Action:
None.
User Action:
If a trace has been recently activated, check that the correct System is specified. Enter ? to display the names of all monitored system images.
Reason:
You issued the DECODE command; however, no packets were decoded on the current page for all protocols specified by the command. One or more of the following conditions exist:
System Action:
None.
User Action:
Ensure that the payload data matches the nominated protocol (for example, no decoding is possible for HTTP packets using the TELNET protocol). Review the packet list and identify packets that are decoded correctly by the command.
Reason:
You issued the TAG command; however, no packets were tagged on the current page for all target strings specified in the command. One or more of the following conditions exist:
System Action:
None.
User Action:
Issue a FIND TAG command to reposition the list on the next packet that contains a matching target string.
Reason:
You issued a command to display details of error sense data; however, it failed because it does not exist in the NETINFO database.
System Action:
None.
User Action:
For user sense data (first byte = x'00'), manually add the details to the NETINFO database. To do this:
1. Enter /NETINFO.
2. Select option 2.
3. Select Category 2 - SNA Sense Codes.
4. Enter the details of the user sense data.
5. Press F10 (Add).
For all other sense data categories (first byte ^= x'00'), contact Technical Support and provide the sense data that does not exist in the NETINFO database. The details of the sense data can also be obtained from IBM publication GA27-3136, Systems Network Architecture Formats.
Reason:
You issued a line command to display details of error sense data; however, the entry has no error sense data. The 4-byte sense data is shown in hexadecimal format and highlighted in red as part of the summary information.
System Action:
The command is rejected.
User Action:
None.
Reason:
The parameter passed to the VIEW command is invalid. The passed parameter is P1.
System Action:
Command rejected.
User Action:
Enter a valid parameter for the VIEW command. The syntax for the command is:
VIEW [ ACTIVE | ALL | CONNECTIONS | EE | RESOURCES | TRACES |
USER [user] | MATCH pattern ]
If no parameters are specified, ALL is assumed and all traces are shown. You can abbreviate the view keywords to as few as two characters.
The views have the following meanings:
ACTIVE displays the Active Traces list, which shows definitions that are currently active.
ALL or blank displays the All Trace Definitions
list, which shows definitions, and the saved traces that have no associated definition.
CONNECTIONS displays the TCP Connection Traces list which shows definitions created using the PT command
against a TCP connection.
EE displays the EE Active and Ended Traces list, which shows definitions created using the PT command
against an Enterprise Extender component.
RESOURCES displays the IP Resources Traces list, which shows definitions created using the PT command against
an IP resource.
TRACES displays the Active and Ended Traces list, which shows definitions that have traces, and the saved traces that have no associated definition.
USER [userid] displays the user Traces list, which shows definitions last updated by the specified user ID or list of user IDs. If no ID is specified, your user ID
is used.
MATCH pattern displays the Trace Matching Name pattern list, which shows definitions with names that match the specified pattern. The pattern can include the following special characters:
*`matches one or more characters.
?`matches a single character.
For example, a?b*c matches all definitions that start with A, followed by any character, followed by B, then
any characters, and finally ending with C.
Reason:
A request to change the view of IP traces completed successfully. The new view settings are P1.
System Action:
None.
User Action:
None.
Reason:
A request to change the IPv6 address format in the display completed successfully. The new setting for the IPv6 address format is p1.
The possible formats are:
SHOW the IPv6 addresses are shown in the full colon style format. HIDE the IPv6 addresses are shown in an abbreviated format with a maximum length of 15 characters (the least signifcant part of the address is removed and replaced with the >< symbol to denote the short format).
Note: Not every instance of an IPv6 address will always be affected by this setting. For example on a list of PT started connection list traces (TCP or EE UDP) the Trace Definition text will not be affected by this setting.
System Action:
None.
User Action:
None.
Reason:
The request to display a list of additional saved traces could not be completed because there are no traces that have been saved on the IPFILE which had their original definition deleted.
System Action:
None.
User Action:
None.
Reason:
No traces exist that were created by a PT command against a connection. Previously activated traces are deleted if not referenced or saved after certain period.
System Action:
None.
User Action:
None.
Reason:
You issued a command to display details of an SQL Code; however, it failed because it does not exist in the NETINFO database.
System Action:
None.
User Action:
For user sense data (first byte =x'00'), manually add the details to the NETINFO database. To do this:
For all other sense data categories (first byte ^=x'00'), contact Technical Support and provide the sense data that does not exist in the NETINFO database. The details of the sense data can also be obtained from IBM publication GA27-3136, Systems Network Architecture Formats.
Reason:
You issued a line command to display details of an SQL code; however, the entry has no valid SQL code. The SQL format is highlighted in either red or yellow and has the following format:
nnn(xxxxx)
Is a signed number.
Is in hexadecimal format.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SmartTrace request has been rejected because the current settings of the $IP SMARTTRACE parameter group are no longer valid because of changes to the SSI Packet Analyzer initialization parameters.
System Action:
The SmartTrace request is rejected.
User Action:
To reinitialize the parameter group:
Reason:
The TAG Command Prompt was actioned with a result P1:
Indicates the number of tags set.
Indicates that no tags were specified.
System Action:
None.
User Action:
None.
Reason:
When issuing the TAG command or specifying data for the input fields on a TAG Command Prompt panel, an invalid parameter was specified. P1 is one of the following error conditions:
Indicates that no data was provided to the command.
Indicates that the data contains characters other than hexadecimal characters (0 to 9, A to F, or a to f).
Indicates that the specified hexadecimal data results in binary data that is not byte aligned. The data should contain an even number of characters. For example, specify 02 instead of 2.
Indicates that the specified IP address is not a valid IPv4 address.
Indicates that the specified IP address is not a valid IPv6 address.
Indicates that the specified data format is not recognized or not supported by the command.
System Action:
On the TAG Command Prompt panel, the fields in error are highlighted. If the TAG search_string search_format command is issued, it is rejected.
User Action:
Retry the command with valid values.
If a null is required as a tag data, specify the low value 00 with a format of HEX. Hexadecimal data should be byte aligned (for example, 02 is binary 00000010).
On the TAG Command P panel, you can specify ? in the Format column to list the valid data formats.
Reason:
A TAG command has tagged the packets that contain data specified by tag P1.
System Action:
None.
User Action:
None.
Reason:
A request to define a new tag has failed because the maximum number of P1 tags are already defined.
System Action:
The command is rejected.
User Action:
Issue the TAGCLR command to either remove all tags or specific tags.
Alternatively, you can replace an existing tag that is no longer required. Enter TAG to list the currently defined tags, and update as required.
Reason:
The DECODE Command Prompt was actioned with result P1:
Indicates that all port assignments were completed without errors.
Indicates that no ports were defined to be decoded by the command prompt.
System Action:
None.
User Action:
None.
Reason:
The maximum allowable entries has been exceeded.
System Action:
The DECODE command prompt is displayed and the field in error is highlighted. The additional port is truncated and appended at the end of the field.
User Action:
Remove entries that are not required for decoding and respecify the additional port to be decoded.
Reason:
When issuing the DECODE command or specifying data on the DECODE Command Prompt panel, an invalid value was specified. P1 is one of the following error conditions:
Indicates that the specified protocol P2 is not currently supported for decoding.
Indicates that for a packet list that is filtered on a local port, specifying a port number is optional. If specified, it must be the same as the local port number.
Indicates that a port number is required for a packet list that is not filtered on a local port.
System Action:
On the DECODE Command Prompt panel, the fields in error are highlighted. If the DECODE server_port_type port_number command is issued, the DECODE Command Prompt is displayed.
User Action:
Retry the command with the valid values.
Reason:
A request to define a new port for decoding has failed because the maximum number of P1 ports for the same protocol are already defined.
System Action:
The command is rejected.
User Action:
Issue the DECODE protocol OFF command to remove all defined ports for the specified protocol.
Alternatively, you can replace a port that is no longer required for the protocol. Enter DECODE to list the currently defined ports, and update as required.
Reason:
The DECODE P1 OFF command has disabled decoding for all ports that were defined for decoding with the P1 protocol.
System Action:
None.
User Action:
None.
Reason:
The DECODE P1 OFF command ended, but no P1 ports were found.
System Action:
None.
User Action:
None.
Reason:
An attempt to decode Port P1 has failed because it is already defined for decoding with another protocol.
System Action:
The request is rejected.
User Action:
Enter DECODE to display the list of ports and associated protocol assignments.
Reason:
The TCP/IP procedure $IPPT61PL failed during processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An invalid dataset name P1 was specified in the Trace Dataset Name field.
System Action:
None.
User Action:
Correct the Dataset Name and retry. The dataset must be a sequential dataset.
Reason:
The component trace command that starts the external writer must be in the format:
TRACE CT,WTRSTART=member
The only parts of the command that you should change to suit your installation is the member name specified on the WTRSTART= keyword parameter in the command or the option 'NOWRAP' (Default:WRAP) can be specified.
The member name must be between 1 and 7 characters in length.
System Action:
None.
User Action:
Correct the command field so that its contents are valid.
Reason:
TCPaccess trace jobname for your installation must be specified even if it is currently running. The jobname specified will be used to check if the TCPaccess trace is running. If it is not running, the job will be started.
System Action:
None.
User Action:
Add the TCPaccess trace jobname.
Reason:
The primary stack for the system selected is either an old version, or is not currently available.
System Action:
Action terminates.
User Action:
None.
Reason:
The SSI DD SUBSYS facility was determined to be currently unavailable. This could be caused by any of the following conditions:
- The SOLVE SSI region is not active.
- This region is not connected to a SOLVE SSI region.
- The DDSUBSYS facility is not enabled in the SOLVE SSI region.
System Action:
The requested action terminates.
User Action:
For information about administering the SOLVE Subsystem Interface and SSI DD SUBSYS support, see the Reference Guide.
Reason:
Whilst reading the trace file, is was detected that P1 trace records are missing. P2 indicates the position in the trace where the records were missing.
Records could be missed due to an error or an overflow of the trace buffer. Therefore you may get unexpected results when browsing the packet trace.
System Action:
A warning message is issued.
User Action:
Try to reduce the amount of traffic that you are tracing so that the trace processing can keep up with the amount of data it is receiving. To limit the traffic you are tracing, specify a specific IP address to trace instead of tracing everything.
Reason:
While reading the trace file, a TCP/IP trace record was found that had a length in the packet header that did not match the actual length of the IP datagram.
P1 is the actual length of packet.
P2 is the expected length of packet.
System Action:
Processsing continues.
User Action:
Determine why the length in the packet header does not match the actual length of the packet.
Reason:
TCP/IP Services has completed saving IP packets that were in the trace file. P1 is the number of IP packets that were saved. P2 is the number of IP packets in error.
System Action:
None.
User Action:
You can now access the trace information that has been loaded.
Reason:
Errors or warnings were encountered whilst saving IP packets in trace file records.
System Action:
None.
User Action:
You can now access the trace information that has been saved.
Reason:
Whilst reading the trace file an error was encountered and some diagnostic information was dumped. P1 is a description of the type of data that has been dumped. This message is at the top of a dump.
System Action:
None.
User Action:
Refer to the following messages that are associated with this message.
Reason:
Whilst reading the trace file an error was encountered and some diagnostic information was dumped. P1 is a line of the diagnostic data that has been dumped.
System Action:
None.
User Action:
None.
Reason:
A TCP/IP trace record has been found that has an IP version other than IPv4 or IPv6. The version of IP in the trace record was P1.
System Action:
A warning message is issued.
User Action:
Determine the source of the packet that has an invalid IP version.
Reason:
Whilst reading the trace file a TCP/IP trace record wa found that contained an Internet header length field which had a value less than 5. The value of the Internet header length field was P1 .
System Action:
A warning message is issued.
User Action:
Try to determine the source of the invalid packet.
Reason:
Whilst reading the trace file a TCP/IP trace record was found that contained an Internet header length field P1 which had a value greater than the length of the IP packet( P2 ).
System Action:
A warning message is issued.
User Action:
Try to determine the source of the invalid packet.
Reason:
No IP packet trace records were found in the trace file.
System Action:
None.
User Action:
Check that you have specified the correct trace file name. Also check that you specified the correct criteria during tracing. There may not be any IP records in the trace file, if no packets were transmitted or received within the criteria that you specified.
Reason:
Whilst reading the trace file a TCP/IP trace record was found that had a length in the packet header that did not match the length of the IP datagram in the trace data.
P1 is the length in the packet header.
P2 is the length that was expected.
System Action:
Save of trace data continues.
User Action:
Determine why the length in the packet header does not match the length of the data.
Reason:
When reading the trace file a TCP/IP trace record was found that had a length in the IP header that did not match the length of the IP datagram in the trace data.
System Action:
Save of trace data continues.
User Action:
Determine why the length in the IP header does not match the length of the data.
Reason:
An attempt to process a component trace data set failed because no valid packet entries were found. A valid packet trace entry would contain the name of its IPCS CTRACE formatting module ( EZBPTFM4 for IBM CS and T03PTIPM for SNS TCPACCESS ).
System Action:
Processing is terminated.
User Action:
Check the name of the trace data set.
Reason:
The events receiver failed when issuing an EPS request. The failure is identified by the following:
- Type of EPS REQ, P1 (for example, CONNECT)
- Return code, P2 (&RETCODE)
- Feedback code, P3 (&ERRNO)
- Reason, P4 (for example, EPS UNAVAILABLE)
System Action:
Processing is terminated.
User Action:
Use the feedback reason to determine why the Event Receiver failed:
70 NO SSI CONNECTION This normally indicates that you have not connected this region to the (correct) SSI.
Use the SHOW SYSPARM=SSID command to determine the SSID value. Ensure that the correct SSID is specified, and that the SOLVESSI started task is active. Use the SSI STATUS command to verify the status of the SSI started task.
81 SSI CONNECTION LOST This indicates that the connection to the SSI has been lost. This may occur if the SOLVESSI started task has terminated, or the region is disconnected from the SOLVESSI because the SSID parameter has been reset.
Use the SHOW SYSPARM=SSID command to determine the SSID value. Ensure that the correct SSID is specified, and that the SOLVESSI started task is active. Use the SSI STATUS command to verify the status of the SSI started task.
For all other feedback reasons, contact Technical Support.
Reason:
An EPS RECEIVE operation timed out for any of the following reasons:
- JOB P1 was not released for execution OR
- JOB P1 abnormally terminated OR - JOB P1 had a JCL error
System Action:
Processing is terminated.
User Action:
Check the system log to determine the cause of the error. It is recommended that the JOB CLASS assigned should be a non-held class or a class that will immediately execute upon submission. Also verify that the JOB card conforms to site standards. Review the corresponding Customizer Parameter Group for packet tracing.
Reason:
An EPS RECEIVE operation timed out because the CTRACE batch job failed to send an output message within the default wait period. The output from the JES JOB log messages follows this message.
System Action:
Processing is terminated.
User Action:
Determine the cause of the failure from the JES JOB log messages. The generated job should use:
1) a JOB CLASS that is a non-held class;
2) a JOB card that conforms to site specific standards.
Review the corresponding Customizer Parameter Group for packet tracing.
Reason:
This message signifies the end of the JES JOB log messages.
System Action:
None.
User Action:
None.
Reason:
The request to save trace records encountered errors during save processing. This may have caused the condition where no trace records are saved.
System Action:
None.
User Action:
Do the following:
1) Ensure that the correct trace file name is specified.
2) Check the activity log error messages for information about the cause of the failure. For error messages that indicate an internal error, contact Technical Support.
Reason:
The packet trace save trace data process has received P1 lines from the trace formatter.
System Action:
Processing continues.
User Action:
None.
Reason:
A request to open database FILEID P1 failed with return code P2 . The meaning of the return code is:
RC=12 File not accessible
RC=16 An unrecoverable error occured during OPEN.
For more information, see the next message, which is written to the activity log
System Action:
The request is rejected and procedure $IPPT62F terminates.
User Action:
Review the activity log for any additional messages. Use the SHOW ALLOC and the SHOW UDB commands to verify that the file is set up correctly, and then retry the request.
Reason:
An unexpected error condition has occurred because procedure P1 failed to respond in a preset time period.
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The procedure P1 terminated without notifying the main procedure. This may produce an incomplete set of packet trace data.
System Action:
The current process continues.
User Action:
Do the following:
1. Run a similar IPCS batch job against the trace dump file to ensure that all packet trace data is saved.
2. Check the activity log for information about the cause of the failure. This is an internal error. Contact Technical Support.
Reason:
TCP/IP services has saved the IP packets in the tracefile. P1 is the number of IP packets saved. P2 is the number of IP packets in error. Processing errors were encountered when saving the packets; therefore, the packet trace data may be incomplete.
System Action:
None.
User Action:
Do the following:
1. Run a similar IPCS batch job against the trace dump file to ensure that all packet trace data is saved.
2. Check the activity log for information about the cause of the error.
Reason:
A database request of P1 for record category P2 has failed.
System Action:
The request is rejected and procedure $IPPT62F terminates.
User Action:
Do the following:
1. Review the activity log for any additional messages. Messages that start with IPPT63 describe the error in detail.
2. Ensure that there is enough space to hold all of the packet trace data.
3. Use the SHOW ALLOC and the SHOW UDB commands to ensure that the file is set up correctly, and then retry the request.
Reason:
A TCP/IP trace record has been found that contains an IPv6 header with a payload length of zero and a next header value of P1.
System Action:
A warning message is issued.
User Action:
None.
Reason:
A request to access a database failed because the procedure a file could not be opened. The file identifier of the file is P1 and the return code from the FILE OPEN statement was P2 .
System Action:
The request is rejected and procedure $IPPT63F terminates.
User Action:
Interpret the return code using the NCL Reference.
Reason:
A procedure failed because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2.
System Action:
Request fails and procedure $IPPT63F terminates.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A request to write data to a database failed because a procedure was unable to obtain a lock. The primary name of the lock was P3 , the minor name was P4 , the return code was P1 , and the feedback code was P2 .
System Action:
The request is rejected and procedure $IPPT63F terminates.
User Action:
Interpret the feedback code using the NCL Reference. The SHOW LOCKS command can be issued from an OCS window to determine the procedure and userid that is holding the lock.
Reason:
A request to access data on a database failed because a procedure was unable to access the file. The file identifier of the file is P1 . The file request that failed was P2 , the file return code was P3 , the VSAM feedback code was P4 , and the key of the record was P5 .
System Action:
The request is rejected and procedure $IPPT63F terminates.
User Action:
Interpret the file return code using the NCL Reference and the feedback code using the VSAM Programmer's Guide or the VSAM Administration: Macro Instruction Reference for installations with DFP.
Reason:
A request to access data on a database failed because a procedure was unable to access the file. The failing request was P1 of category
P2 . P3 was the failing record key.
System Action:
The request is rejected and procedure $IPPT63F terminates.
User Action:
Interpret the file return code using the NCL Reference and the feedback code using the VSAM Programmer's Guide or the VSAM Administration: Macro Instruction Reference for installations with DFP.
Reason:
A request to access the IPFILE database failed because the file is not allocated and open, or the file has been opened read-only.
System Action:
The request is rejected.
User Action:
Action the IPFILES Customizer parameter group to correctly allocate and open the IPFILE database.
Reason:
A internal request to get or delete a record from IPFILE has failed because the specified record does not exist or has been deleted.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The requested action is no longer available.
System Action:
The request is rejected.
User Action:
Change the calling procedure to use RAMDB.
Reason:
Request to create a new monitor group has been successfully completed.
System Action:
None.
User Action:
None.
Reason:
Request to update a monitor group has been successfully completed.
System Action:
None.
User Action:
Reason:
A request to get the list of packet entries has exceeded the internal limit of 32K.
System Action:
The records that have been retrieved are returned to the caller.
User Action:
Reason:
A Selection List service procedure did not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your Sustems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The List IP packets in error was issued for a saved packet trace but none were found. The following are the reasons for an IP packet to be in error:
1) Unsupported IP version (only version 4).
2) The IP Header length has a value less than 5.
3) The IP Header length exceeds the IP packet length.
4) The IP Header total length does not match the actual length of the datagram.
System Action:
No list is displayed.
User Action:
None.
Reason:
The selected packet trace entry is empty.
System Action:
None.
User Action:
None.
Reason:
You have entered a line command for an entry that is currently saving trace data.
System Action:
The request is rejected.
User Action:
Retry the command when the save completes. If the save process is in progress for an excessive amount of time, issue the D=Delete command and retry.
Reason:
A Selection List service procedure does not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
You have tried to scroll past the start or end of the packet trace. There are no more packet trace records available in the direction you are scrolling.
System Action:
You are positioned at the first trace record if a 'Prev' action was being processed or the last trace record if a 'Next' action was being processed.
User Action:
None.
Reason:
You have specified an invalid scroll amount. Valid scroll amounts are a number, or 'M' or 'MAX' for a maximum scroll.
System Action:
Request rejected.
User Action:
Correct the scroll amount and retry.
Reason:
A Selection List service procedure does not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The 'IP Address List' action was issued for a saved packet trace but no IP Address analysis has been performed for this trace.
System Action:
The IP Address List is not displayed.
User Action:
Select a different action for this trace as 'IP Address List' is not available.
Reason:
A Selection List service procedure does not support the selection option P1 that was specified on the selection list.
System Action:
The selection is rejected.
User Action:
Contact your system administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
The selection list terminates.
User Action:
Contact your system administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The 'Connection List' action was issued for either a saved packet trace or an IP Address within a saved packet trace, but no connection data exists for this object.
System Action:
The Connection List is not displayed.
User Action:
Select a different action as the 'Connection List' is not available.
Reason:
A SOLVE procedure failed because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and the procedure terminates.
User Action:
Contact your product supplier.
Reason:
You specified P1 as the sort field for the list on the SORT command but
P1 is not a valid sort field.
System Action:
The SORT command was rejected.
User Action:
Correct the sort field name (which is an operand on the SORT command) and retry.
Reason:
The value of the specified parameter passed is invalid.
System Action:
None
User Action:
Correct the parameter and retry.
Reason:
The specified parameter is required for this call but has been omitted.
System Action:
None
User Action:
Specify the parameter and retry.
Reason:
This message is returned in response to a $IPPT74Z ACTION=STATUS call.
P1 will be CTRACE, P2 will be set to ACTIVE or INACTIVE.
System Action:
None.
User Action:
None.
Reason:
A request has been received to start P1 , but P1 is already active.
System Action:
None.
User Action:
None.
Reason:
A request has been received to start P1 but the system messages did not indicate that P1 had been started. The messages received from the operating system have been written to the Activity Log following this message.
System Action:
None.
User Action:
View the messages and determine if P1 did start. If the messages indicated that P1 did start, contact Technical Support.
Reason:
A request has been received to start P1 but the system messages did not indicate that P1 had been started. The messages received from the operating system have been written to the Activity Log following message IPPT7405. This message (IPPT7406) signifies the end of the system messages.
System Action:
None.
User Action:
Refer to message IPPT7405 for a description of why these messages are written to the Activity Log.
Reason:
A request has been received to start P1 but the system messages did not indicate that P1 had been started. The messages received from the operating system have been written to the Activity Log following message IPPT7405.
System Action:
None.
User Action:
Review the messages in the Activity Log to determine why P1 failed to start.
Reason:
A request has been received to start P1 and the request has completed successfully.
System Action:
None.
User Action:
Perform your tracing.
Reason:
A request has been received to stop P1 but P1 is not active.
System Action:
None.
User Action:
None.
Reason:
A request has been received to stop P1 but the system messages did not indicate that P1 had been stopped. The messages received from the operating system have been written to the Activity Log following this message.
System Action:
None.
User Action:
View the messages and determine if P1 did actually stop. If the messages indicated that P1 did stop, contact Technical Support.
Reason:
A request has been received to stop P1 but the system messages did not indicate that P1 had been stopped. The messages received from the operating system have been written to the Activity Log following message IPPT7410. This message (IPPT7411) signifies the end of the system messages.
System Action:
None.
User Action:
Refer to message IPPT7410 for a description of why these messages are written to the Activity Log.
Reason:
A request has been received to stop P1 but the system messages did not indicate that P1 had been stopped. The messages received from the operating system have been written to the Activity Log following message IPPT7410.
System Action:
None.
User Action:
Review the messages in the Activity Log to determine why P1 failed to stop.
Reason:
A request has been received to stop P1 . The request has completed and the name of the trace output dataset was obtained, but it could not be stored. An error message with message number P1 was written to the Activity Log explaining why the operation failed.
System Action:
None.
User Action:
Review the messages in the Activity Log to determine why the operation failed.
Reason:
A request has been received to stop P1 . The request has completed. The name of the trace output dataset was obtained and is shown as P2 in this message. This message is also written to the log which will show the full dataset name if it is truncated on the panel.
System Action:
None.
User Action:
None.
Reason:
A request has been received to stop P1 . The request has completed but
P1 has indicated that no trace output is available.
System Action:
None.
User Action:
Check that you are tracing the correct IP resources, as there was no packets traced that matched the criteria you specified.
Reason:
A request has been received to obtain the status of P1 , but the response to the 'D J,jobname' command was not understood by the SOLVE system. The SOLVE system has not been able to determine the status of P1 .
System Action:
None.
User Action:
View the messages and determine what state P1 is in.
Reason:
A request has been received to obtain the status of P1 , but the region did not understand the display resulting from the 'D J,xxx' command issued. The display messages have been written to the Activity Log following message IPPT7416. This message (IPPT7417) signifies the end of the system messages.
System Action:
None.
User Action:
Refer to message IPPT7416 for a description of why these messages are written to the Activity Log.
Reason:
A request has been received to obtain the status of P1 , but the region did not understand the display produced by the 'D J,xxx' command. The display messages have been written to the Activity Log following message IPPT7416.
System Action:
None
User Action:
Review the messages in the Activity Log to determine what the status of P1 is
Reason:
An error occurred while attempting to retrieve the component name from the IFSPARM TRACENAME(xxxx) parameter in the IJTCFGxx configuration member which is in the TCPaccess PARM dataset. This dataset is defined to TCP/IP Services on the TCP/IP Management Interface panel which can be accessed from the TCP/IP Administration Menu.
System Action:
None.
User Action:
Check the log for details of the error and take appropriate corrective action.
Reason:
An attempt was made to retrieve the component name from the IJT configuration member but TRACENAME was missing from the IFSPARM.
System Action:
None.
User Action:
Update the IJT configuration member to the include the name in IFSPARM TRACENAME(xxx), where xxx is a valid component name.
Reason:
All packet traces have been cleared.
System Action:
None.
User Action:
None. Information only.
Reason:
A packet trace operation was attempted, but could not be performed because the TCP/IP interface is not ACTIVE.
System Action:
None.
User Action:
TCP/IP services should be initialized using the TCP/IP Administration Menu.
Reason:
A request has been received to load trace data. However, the trace collector has indicated that no trace output is available.
System Action:
None.
User Action:
Check that you are tracing the correct resources, as there was no trace data produced during the time the collector was active.
Reason:
A request has been received to load trace data. However, the trace collector was not stopped succesfully.
System Action:
None.
User Action:
Refer to the trace collector stop messages for problem determination.
Reason:
A packet trace clear is not necessary as the component trace function is not active.
System Action:
None.
User Action:
None. Information only.
Reason:
A packet trace clear is not necessary as the packet tracing component trace is not active.
System Action:
None.
User Action:
None. Information only.
Reason:
A system command has been issued by the trace control process and the expected responses have not been returned within a 2 minute period.
System Action:
The current action is terminated and messages received so far are logged along with this message.
User Action:
Refer to the earlier messages for an indication of why the system command failed. Report the error to your system administrator. If necessary provide activity log and system log for the period to your product support representative.
Reason:
Packet Tracing of Host Name/Addr P1 has been started successfully.
System Action:
None.
User Action:
Perform the activity you want to trace.
Reason:
The output from the MVS command D TRACE,WTR= follows this message. A list of component traces currently connected to the external writer is shown.
System Action:
None.
User Action:
Review the output and determine the components that are currently connected to the external writer. Either stop all the connected components or force the external writer to end by repeatedly issuing the MVS command TRACE CT,WTRSTOP= . See MVS System Messages(ITT121I) for more details.
Reason:
This message signifies the end of the system messages.
System Action:
None.
User Action:
Refer to message IPPT7431 for a description of why these messages are written to the Activity Log.
Reason:
A request has been received to stop CTRACE but one or more components were still connected to the external writer. The status of the external writer has been written to the Activity Log.
System Action:
None.
User Action:
Review the messages following IPPT7429 to determine the components currently connected to the external writer. Either stop all the connected components or force the external writer to end by repeatedly issuing the MVS command TRACE CT,WTRSTOP= . See MVS System Messages (ITT121I) for more details.
Reason:
A request to use the external writer P1 failed because it is in use by another component trace. The external writer can only be associated to one component trace at a time.
System Action:
The request is rejected.
User Action:
Perform the following steps:
SYSCMD D TRACE,WTR=external_writer_name
Reason:
The 'IP Address List' action was issued for a saved packet trace but no IP Address analysis has been performed for this trace.
System Action:
The IP Address List is not displayed.
User Action:
Select a different action for this trace as 'IP Address List' is not available.
Reason:
The 'Connection List' action was issued for either a saved packet trace or an IP Address within a saved packet trace, but no connection data exists for this object. P1 is the object type.
System Action:
The Connection List is not displayed.
User Action:
Select a different action as the 'Connection List' is not available.
Reason:
The List packets action was issued for a saved packet trace but no packets within the trace match the criteria specified.
System Action:
The packet list is not displayed.
User Action:
Select a different criteria and retry the operation.
Reason:
The List IP packets in error was issued for a saved packet trace but none were found. The following are the reasons for an IP packet to be in error:
1) Unsupported IP version (only version 4) 2) The IP Header length has a value less than 5. 3) The IP Header length exceeds the IP packet length. 4) The IP Header total length does not match the actual length of the datagram.
System Action:
No list is displayed.
User Action:
None
Reason:
The selected packet trace entry is empty.
System Action:
None
User Action:
None
Reason:
A Selection List service procedure does not support the selection option P1 that was specified on the selection list.
System Action:
Selection rejected.
User Action:
Contact your system administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A Selection List service procedure does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your system administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An error occured during initialization of CTAPI API. The meaning of the return and feebback code are as follows:
RC FDBK Description
12 1 API load module EZBCTAPI load failure
12 2 API load module EZBNMCTF load failure
12 3 API format table EZBPTFM4 load failure
16 2 Internal prepare MDO failure
16 3 Internal assign MDO failure
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An error occured during initialization of CTAPI API. The meaning of the return and feebback code are as follows:
RC FDBK Description
8 1 FORMAT rejected - Interface not initialized
8 2 Invalid FORMAT call - Empty input buffer
8 3 Invalid FORMAT call - Buffer not empty
8 4 Invalid FORMAT call - Incomplete CTE in buffer
12 1 API load module EZBCTAPI load failure
12 2 API load module EZBNMCTF load failure
12 3 API format table EZBPTFM4 load failure
16 2 Internal prepare MDO failure
16 3 Internal assign MDO failure
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An error occured in the EZBCTAPI Macro Interface. For more information about the meaning of the return and reason codes, see the z/OS Communication Server: IP Programmer's Reference manual.
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The value P1 is not a valid value for the keyword parameter P2 .
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The keyword-value pair of P1 is valid with ACTION=DEFINE only.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The procedure call contains keyword parameters that are mutually exclusive. One of the keywords can be specified only.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
Specify keyword NAME=, OBJID=, or LPORT.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A procedure call did not include the required keyword parameter P1 .
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The procedure call specifed the keyword parameter P1 with a non-numeric value P2 . The keyword accepts numeric values only.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The procedure call specifed the keyword parameter P1 with a numeric value outside the valid range of P2-P3.
System Action:
The field in error is highlighted.
User Action:
Specify a value in the range.
Reason:
An error was encountered when attempting to access the resource definition database.
System Action:
Process terminates.
User Action:
Review the activity log entry and determine the cause of the failure.
Reason:
Packet tracing is not available for the selected resource.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An internally-generated trace definition name P1 does not conform to naming conventions for trace type P2 .
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The input MDO definition provided as part of the function call uses an invalid map P1 .
System Action:
Procedure terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A trace definition was retrieved and has the indicated status.
P1 identifies the definition.
P2 indicates the status.
System Action:
None.
User Action:
None.
Reason:
A request to retrieve trace defintion P1 failed because it does not exist.
System Action:
None.
User Action:
None.
Reason:
Packet tracing is temporary unavailable for the selected entry. This condition usually occurs when the SSI region that implements the Packet Analyzer feature is initialized after the CA NetMaster region.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The selected entry does not contain packet data or a definition, although request to stop, clear, or view a trace was requested.
System Action:
Request rejected.
User Action:
Issue a PT command to define a trace for the selected entry.
Reason:
The process to set up a packet trace is canceled.
System Action:
None.
User Action:
None.
Reason:
The packet trace definition P1 is saved successfully in the database.
System Action:
None.
User Action:
None.
Reason:
The input MDO definition is not provided as part of the function call.
System Action:
Procedure terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An attempt to save a packet trace definition failed.
System Action:
Procedure terminates.
User Action:
Check the activity log for message FAPKG01 and the entries that follow.
Reason:
A request to activate a packet trace completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to activate a packet trace that is already active has been reactivated successfully. All existing trace entries are retained.
System Action:
None.
User Action:
None.
Reason:
A request to inactivate a packet trace completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to inactivate a packet trace determined that the trace is already inactive.
System Action:
None.
User Action:
None.
Reason:
A request to delete a packet trace completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to delete a packet trace completed successfully for an active trace.
System Action:
None.
User Action:
None.
Reason:
Packet tracing for an ASMON resource has been rejected because its monitoring definition does not specify any ports.
System Action:
Process terminates.
User Action:
Review the monitoring definition for the selected ASMON resource, and ensure TCP and/or UDP ports are specified.
Reason:
The selected action is unavailable for one of the following reasons:
System Action:
None.
User Action:
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
Packet tracing is disabled because the SOLVE SSI region is running with a PALEVEL value other than FULL.
System Action:
None.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, we recommend that you always set the PALEVEL parameter to FULL. If you run with a level other than FULL, tracing and other IP functions are not available.
Only use a PALEVEL other than FULL if instructed by CA Support.
Reason:
A request to activate a packet trace has failed because the trace is already active.
System Action:
The action fails.
User Action:
None.
Reason:
Packet trace P1 activation request was successfully completed.
System Action:
None.
User Action:
None.
Reason:
The requested function is not supported by the P1 remote region. The remote region is used because it is the managing region for the resource.
The remote region is currently linked to this region in Migration Mode. This type of linkage is used during the migration of the remote region to a new release level.
System Action:
Processing of the function terminates.
User Action:
After you upgrade the remote region to the same release level as this region, link them using normal region synchronization to get full functionality.
Reason:
A packet trace request has been rejected because the stack P1 is not known to Packet Analyzer. The stack is not defined as a monitored IP resource in the region.
System Action:
The packet trace request is terminated.
User Action:
Define the stack using the resource administration panels
The TCP/IP Stack List panel appears.
Press F4 (Add) to create a definition for the stack.
Reason:
An attempt to initiate SmartTrace has failed because the Packet Analyzer to be used for the trace is executing in an SSI region that is not at the latest product release level and does not support IPv6 addressing formats.
System Action:
Request is rejected.
User Action:
Consider upgrading. Contact your system administrator.
Reason:
You attempted to start a SmartTrace of an RTP pipe with PU name P1. The action failed because the RTP pipe is not an EE RTP pipe, and is not using IP.
System Action:
None.
User Action:
None. SmartTrace traces IP packets only.
Reason:
A Packet Analyzer request to the SOLVE SSI on LPAR P1 failed because the Packet Analyzer is not enabled for EE processing.
System Action:
The request fails.
User Action:
Investigate why EE analysis is disabled on P1.
1. Check the Packet Analyzer version using the SSI STATUS command.
EE analysis requires Packet Analyzer version 116.01.
2. Check if EE Analysis is disabled. To do this, display the SSIPARMS member in the SOLVE SSI region's JCL library. EE analysis is disabled by setting parameter PAEESTACK to NONE, or PAEEBASE to NO or 0.
Reason:
You attempted to start a SmartTrace of an RTP pipe with PU name P1. The action failed because the RTP pipe is not known to VTAM.
System Action:
None.
User Action:
The RTP may have terminated. Press F6 to refresh the list of RTP pipes.
Reason:
A SmartTrace request has been rejected because the current settings of the $IP SMARTTRACE parameter group are no longer valid because of changes to the SSI Packet Analyzer initialization parameters.
System Action:
The SmartTrace request is rejected.
User Action:
To reinitialize the parameter group:
Reason:
An internal function requires an input MDO definition that is not shared in as part of the procedure call.
System Action:
Procedure terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The input MDO definition provided as part of the function call uses an invalid map P1 .
System Action:
Procedure terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The selected entry has a trace definition with a current status of
P1 and was last updated by userid P2 .
System Action:
None.
User Action:
None.
Reason:
This prompt message appears when you press F3 (File) while updating a trace definition. The following options are available:
F3 (File) Saves the updated definition and exits the current panel. If a trace is active, it is restarted; otherwise, it remains inactive.
F6 (Action) Does the same as PF3, except that it unconditionally starts or restarts the trace.
Enter Resumes updating the currently-displayed trace definition.
System Action:
None.
User Action:
Select the appropriate option.
Reason:
You changed the IP or ICMP Version field while defining a new trace definition. The following options are available:
Retains the current version and preserves all existing field values.
Implements the new IP/ICMP version and clears all existing fields except for the Name, Definition, and IP/ICMP version fields.
System Action:
None.
User Action:
Select the appropriate option.
Reason:
You pressed F5 (Retain) and you changed the IP/ICMP Version field while defining a new trace definition.
System Action:
Current field values are retained.
User Action:
None.
Reason:
You pressed F6 (ChgVer) and changed the IP/ICMP Version field while defining a new trace definition.
System Action:
All fields are cleared except Name, Description, and IP/ICMP Version.
User Action:
None.
Reason:
When asked to select an action, no selection was made; or all existing actions were deleted manually.
System Action:
None.
User Action:
None.
Reason:
This is an informational message indicating that no changes were made to the current list of actions.
System Action:
None.
User Action:
None.
Reason:
A request to add or update a list of stop actions has been canceled.
System Action:
Current changes are abandoned.
User Action:
None.
Reason:
A request to update a list of actions has been completed.
System Action:
None.
User Action:
None.
Reason:
A request to view a list of actions has failed because none has been defined.
System Action:
None.
User Action:
None.
Reason:
A attempt to define an automated stop action has failed because no stop condition has been defined on Page 3 of the trace definition.
System Action:
Request is rejected.
User Action:
Define a stop condition on Page 3 of the trace definition before attempting to define a stop action.
Reason:
All defined stop actions have been cleared because the associated stop conditions on Page 3 of the trace definition has been cleared.
System Action:
None.
User Action:
None.
Reason:
The selected function is not supported because the linked region is running a back-level version of the product.
System Action:
Request is rejected.
User Action:
Consider upgrading. Contact your system administrator.
Reason:
The input MDO is using an invalid map P1 or is not assigned a map.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
A request to validate field P1 failed because there is no validation routine to handle the request.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
Validation is not possible because the input MDO contains null fields.
System Action:
None.
User Action:
None.
Reason:
The trace definition P1 already exists.
System Action:
The name is highlighed in error.
User Action:
Enter a different name and retry.
Reason:
The trace definition P1 already exists on region P2. SmartTrace definition names must be unique across all regions on an LPAR.
System Action:
The name is highlighted in error.
User Action:
Enter a different name, and retry.
Reason:
The field validation for the current SmartTrace definition has detected that the Packet Analyzer to be used for the trace is executing in an SSI region that is not at the latest product release level and does not support IPv6 addressing formats. P1 identifies the field in error.
System Action:
The field in error is highlighted.
User Action:
Consider upgrading. Contact your system administrator.
Reason:
The required field P1 was not provided.
System Action:
The field is highlighted in error.
User Action:
Enter a valid value for the field.
Reason:
Stack name P1 is invalid. No stack of this name is defined in region P2.
System Action:
The field in error is highlighted.
User Action:
Enter ? in the Stack field to obtain a list of stacks.
Reason:
The use of the character ? to display a selection list is not valid for the field P1 .
System Action:
The request is rejected.
User Action:
Do not specify ? for this field.
Reason:
The length of the specified value for P1 exceeds that allowed and has been truncated.
System Action:
The field in error is highlighted.
User Action:
Reformat the supplied value with the equivalent numeric codes for the ICMP Types and ICMP Codes fields.
Reason:
The TCP/IP Stack field is required when an Interface Name is specified.
System Action:
The field in error is highlighted.
User Action:
Select from the list of valid stacks.
Reason:
The Local Host or Foreign Host fields are mutually exclusive with the Special Address field.
System Action:
The field in error is highlighted.
User Action:
Either clear the Special Address field or the Local Host and/or Foreign Host fields.
Reason:
Local Ports or Foreign Ports was specified; however, the IP Protocol value was not TCP or UDP.
System Action:
The field in error is highlighted.
User Action:
Specify TCP or UDP in the IP Protocol field.
Reason:
The Create Multiple TCP Connection Trace? field is set to YES; however, the IP Protocol field is not set to TCP or 6.
System Action:
The fields in error are highlighted.
User Action:
Specify TCP in the IP Protocol field when creating a multiple TCP connection trace.
Reason:
A validation of the trace definition completed with P1 fields in error.
System Action:
A list of all associated error messages is returned.
User Action:
Review the next error messages and take the appropriate action.
Reason:
The P1 field value contains invalid characters or violates the coding rules for the field. A valid value consists of alphanumeric characters (A-Z and 0-9), national characters, and should begin with an alphabetic character.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
The specified interface name contains invalid characters or violates coding rules. P1 describes the reason for the error. The value in the Interface Name field must adhere to the following rules:
System Action:
The field in error is highlighted.
User Action:
Specify a valid interface name.
Reason:
The value specified must be numeric and be in the range specified.
System Action:
The field in error is highlighted.
User Action:
Specify a value in the range.
Reason:
You specified an invalid time format or range.
System Action:
The field in error is highlighted.
User Action:
Specify a value from 0:01 through p1 in the valid time format (hhh:mm).
Reason:
Valid values for this field are Yes or No or blank.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
Valid values for this field are In or Out or blank.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
This error condition is generated when an invalid IP Protocol name is specified. The assigned IP protocol name is regulated by the Internet Assigned Numbers Authority (IANA) and is always subject to change.
System Action:
The field in error is highlighted.
User Action:
Specify the assigned number (0-255) for the required IP protocol.
Reason:
Valid values for this field are Loopback, Multicast, Broadcast, or blank.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
A value other than =, ^=, <, <=, >, >= and its corresponding mnemonic ( Q, NE, LT, LE, GT, GE) was specified.
System Action:
The field in error is highlighted.
User Action:
Specify a valid operator or enter ? to select from a list.
Reason:
This error condition is generated by one of the following reasons:
- The specified ICMP message type is not valid. The ICMP type can be specified as a number from 0-255 or by selection from a list of valid name types.
- The Original Datagram Details section has non-blank fields, which limits the valid type to ICMP error messages. See message IPPT8856 for a list of valid ICMP error message types.
- The Redirect Gateway field is non-blank, which limits the valid type to REDIRECT Type(5) .
System Action:
The field in error is highlighted.
User Action:
Make a selection from the list of valid types or enter a blank where appropriate.
Reason:
The specified ICMP Codes is not valid for the selected ICMP Types, for example, the PARAMPROB ICMP message type uses codes 0-2.
System Action:
The field in error is highlighted.
User Action:
Select from the list of valid ICMP codes.
Reason:
ICMP Codes was specified but ICMP Types contains a list of types. ICMP code values can be associated with one ICMP type only.
System Action:
The field in error is highlighted.
User Action:
Modify the ICMP Types field to contain only one message type that is relevant to the specified ICMP code.
Reason:
An input list has P1 specified more than once.
System Action:
The field in error is highlighted.
User Action:
Review the input list and remove any duplicate values.
Reason:
A ICMP Message Type other than REDIRECT (Type 5) is specified together with a Redirect Gateway address.
System Action:
The field in error is highlighted.
User Action:
Specify REDIRECT, 5, or blank for the ICMP Types field.
Reason:
The expression is no longer valid because all of the simple expressions used to build the compound relational expression have been deleted.
System Action:
The field in error is highlighted.
User Action:
Clear the expression field.
Reason:
An invalid QOS value was specified.
System Action:
The field in error is highlighted.
User Action:
Select from the list of valid QOS values.
Reason:
An invalid expression was used to build the compound expression. This is caused by one of the following conditions:
- You included an unsupported operator or expression when building the compound expression.
- For packet data box entries, a simple expression was deleted but continues to be referenced as part of the compound expression.
System Action:
The fields in error are highlighted.
User Action:
Do one of the following:
- Select from the list of expressions available for building the compound expression.
- Clear the field to generate a default compound expression.
Reason:
A relational expression is invalid because a right parenthesis is missing to balance a corresponding left parenthesis.
System Action:
The field in error is highlighted.
User Action:
Review and modify the expression to balance an open left parenthesis.
Reason:
Data comparisons are done on the first 128 bytes of the target data. The combined values specified for Start Pos. and Length exceeds this limit. For example, a start position of 100 and length of 50 is an invalid combination.
System Action:
The fields in error are highlighted.
User Action:
Adjust the values for Start Pos. and Length to conform to the scope for comparing.
Reason:
An invalid data format P1 was specified.
System Action:
The field in error is highlighted.
User Action:
Select from the list of valid data formats.
Reason:
An invalid data operator P1 was specified.
System Action:
The field in error is highlighted.
User Action:
Select from the list of valid data operators.
Reason:
A Format value of HEX was specified; however, the data string contains non-hexadecimal characters.
System Action:
The field in error is highlighted.
User Action:
Modify the data string to contain hexadecimal characters only.
Reason:
When specified, the Length value must be equal to the actual length of the EQ/NE Data string.
System Action:
The field in error is highlighted.
User Action:
Adjust the length value so that it matches the length of the data string. Alternatively, leave the Length field blank when you use EQ/NE operators.
Reason:
An attempt to build a compound expression is rejected because no simple expression is defined.
System Action:
The field in error is highlighted.
User Action:
Specify at least one simple expression.
Reason:
An expression cannot end with a left parenthesis or relational operator.
System Action:
The field in error is highlighted.
User Action:
Complete the expression.
Reason:
The specified ICMP Type does not support embedding details of the original datagram as part of its message. ICMP error message types always contains the IP header and the first eight bytes of the IP datagram that caused the ICMP error message. The valid ICMP error messages types are as follows:
DESTUNREACH (type 3)-Destination Unreachable
SRCQUENCH (type 4)-Source Quench
REDIRECT (type 5)-Redirect
TIMEEXC (type 11)-Time exceeded
PARAMPROB (type 12)-Parameter problem
System Action:
The field in error is highlighted.
User Action:
Select a valid error message type from the list.
Reason:
A request to list known stack interfaces or an attempt to validate a given interface cannot be completed. This condition is caused by one of the following:
- The stack is inactive
- The SSI region is inactive
- The stack is not known to the SSI region
System Action:
The field is highlighted.
User Action:
Ensure that the interface name is valid for the selected stack.
Reason:
The specified interface does not exist for the selected stack.
System Action:
The field in error is highlighted.
User Action:
Select from the list of known stack interfaces.
Reason:
Interface P1 is accepted conditionally because an existence check cannot be done at this time. This condition is caused by one of the following reasons:
System Action:
If the SSI is active, trace activation is permitted and packets are collected when the specified interface becomes available.
User Action:
None.
Reason:
A hexadecimal data string that does not end on a byte boundary is rejected. For example, hexadecimal 12AED is invalid while hexadecimal 12AED6 is a valid data string.
System Action:
The field in error is highlighted
User Action:
Modify the hexadecimal string to end on a byte boundary.
Reason:
The supplied data pattern for the LIKE operator does not contain the required wildcard characters * or ?.
System Action:
The field in error is highlighted.
User Action:
Review the data pattern and determine the appropriate wildcard character. An asterisk (*) matches zero or more characters, while a question mark matches any character. If wildcard characters are not required, change the operation from LIKE to EQ .
Reason:
A simple expression is not referenced in the compound expression.
System Action:
The fields in error are highlighted.
User Action:
Remove the simple expression that is not referenced or clear the expression field to generate a default expression that contains all of the simple expressions.
Reason:
The minimum Length that can be specified must be equal to the length of the LIKE data pattern.
System Action:
The field in error is highlighted.
User Action:
Adjust the length value so that it is at least equal to the length of the LIKE data pattern but not exceeding 32 bytes.
Reason:
If the length is specified for a HEX type data string, it must be half the length of the displayed hexadecimal string.
System Action:
The field in error is highlighted.
User Action:
Adjust the length value accordingly. Alternatively, leave the Length field blank when you use EQ/NE operators.
Reason:
The LIKE operator cannot be used with P1 data format strings.
System Action:
The field in error is highlighted.
User Action:
Use an EQ or NE operator when you compare packet data with a P1 data format string.
Reason:
The specified Foreign/Local Host address combination cannot be traced. The following combinations are not valid:
System Action:
The fields in error are highlighted.
User Action:
Supply a correct combination of IP addresses. For combinations 1-3, validation is performed only when the stacks are known to the packet analyzer; otherwise, it is your responsibility to ensure that a valid combination is specified.
Reason:
A length value other than four was specified for an IP4ADDR data format. An IP4ADDR data format converts the test IP address character string to its equivalent four-byte binary format for an IP address. The binary format is then used for packet data comparisons.
System Action:
The field in error is highlighted.
User Action:
If a length is specified, only a value of four is allowed. Alternatively, the field can be left blank.
Reason:
A generic address notation is not valid for P1 data format.
System Action:
The field in error is highlighted.
User Action:
Specify a valid IP address format.
Reason:
Packets After Stop value equal or greater than the Trace Limit value is not allowed.
System Action:
The fields in error are highlighted.
User Action:
Decrease the Packets After Stop value to less than the current Trace Limit or increase the Trace Limit.
Reason:
Packet tracing is not possible for the selected entry for one of the following reasons:
- The Foreign and Local Host address have the same IP Address, and the IP address is not a LOOPBACK address.
- The Foreign and Local Host address are interfaces from the same TCP/IP stack.
- The Foreign and Local Host address are LOOPBACK addresses with different IP addresses.
System Action:
None.
User Action:
None.
Reason:
The specified Foreign Host address cannot be traced for one of the following reasons:
- The Foreign Host address is an interface from the specified TCP/IP stack.
- The Foreign Host address is the same as the Local Host address and the IP address is not a LOOPBACK address.
- The Foreign Host address is a LOOPBACK address and is different from the Local Host address.
System Action:
The field in error is highlighted.
User Action:
Supply a valid Foreign Host address. Validation is performed only when the stacks are known to the packet analyzer; otherwise, it is your responsibility to ensure that a valid address is specified.
Reason:
Packet tracing is not possible because the specified Local Host address cannot be found in any of the stacks known to the packet analyzer.
System Action:
The field in error is highlighted.
User Action:
Supply a valid Local Host address from a stack known to the packet analyzer.
Reason:
The specified local host address is accepted conditionally because an existence check cannot be done at this time. This condition is caused by one of the following reasons:
System Action:
If the SSI is active, trace activation is permitted and packets are collected when the specified local host address becomes available.
User Action:
None.
Reason:
The specified Local Host address cannot be traced for one of the following reasons:
- The Local Host address is the same as the IPNODE's address and is not a LOOPBACK address.
- The Local Host address and the IPNODE's address are interfaces from the same TCP/IP stack.
- The Local Host address and the IPNODE's address are LOOPBACK addresses but with different IP addresses.
System Action:
The field in error is highlighted.
User Action:
Supply a valid Local Host address. Validation is performed only when the stacks are known to the packet analyzer; otherwise, it is your responsibility to ensure that a valid address is specified.
Reason:
Character P1 is not valid for field P2.
System Action:
The request is rejected.
User Action:
Remove the invalid character.
Reason:
The specified host address uses a P1 address format that is not valid for this trace definition.
System Action:
The fields in error are highlighted.
User Action:
Enter the correct IP address format that matches the IP or ICMP version field.
Reason:
Valid values for this field are 4 or 6.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
Valid values for this field are Loopback, Multicast, or blank.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
An ICMP Message Type other than PKT-TOO-BIG (type 2) is specified with an MTU of Next Hop value.
System Action:
The field in error is highlighted.
User Action:
Specify PKT-TOO-BIG, 2, or blank for ICMP Types.
Reason:
This field accepts series of numbers between 0 and 1. For example, a valid combination is 01010101.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
This error condition is generated by one of the following reasons:
System Action:
The field in error is highlighted.
User Action:
Select a valid type from the list or enter a blank where appropriate.
Reason:
The specified ICMP Type does not support embedding details of the original datagram as part of its message. ICMP error message types always contain the packet that caused the ICMP error message. The valid ICMP error message types are as follows:
DESTUNREACH (type 1) - Destination Unreachable
PKT-TOO-BIG (type 2) - Packet Too Big
TIMEEXC (type 3) - Time Exceeded
PARAMPROB (type 4) - Parameter Problem
System Action:
The field in error is highlighted.
User Action:
Select a valid error message type from the list.
Reason:
The supplied IP network address is invalid for one of the following reasons:
System Action:
None.
User Action:
Correct the value and retry.
Reason:
You specified a length value other than 16 for an IP6ADDR data format. An IP6ADDR data format converts the test IP address character string to its equivalent 16 byte binary format for an IP address. The binary format is then used for packet data comparisons.
System Action:
The field in error is highlighted.
User Action:
If a length is specified, only a value of 16 is allowed. Alternatively, you can leave the field blank.
Reason:
The supplied data value is not compatible with the selected data format of P1.
System Action:
The field in error is highlighted.
User Action:
Specify the correct value for the selected data format.
Reason:
This field accepts a value of YES only.
System Action:
The field in error is highlighted.
User Action:
Specify YES to activate this criteria.
Reason:
The IP addressing format defined for this trace definition is not valid for the selected protocol.
System Action:
The fields in error are highlighted.
User Action:
Select a valid protocol for the current IP addressing format or specify the correct IP addressing format for the selected protocol.
Reason:
An error occurred during initialization of CTAPI API. The meaning of the return and feedback codes are as follows:
API load module EZBCTAPI load failure
API load module EZBNMCTF load failure
API format table EZBPTFM4 load failure
Internal prepare MDO failure
Internal assign MDO failure
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed. The message includes the following details:
P1 is the EPS request type, for example, Connect, Send, Receive.
P2 is the EPS error number.
P3 is an explanation of the EPS error number.
System Action:
The request fails.
User Action:
Use the EPS Error Number and Reason to determine the error:
This indicates that the connection between this region and the SSI region is not active. Use the $LOG command to check the activity log for related messages.
Use the $NM SSI Customizer parameter group to restart the SOLVE SSI.
For all other errors, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because of an invalid connection ID. The message includes the following:
P1 is the EPS verb name that was issued when the error was detected. P2 is the EPS connection ID.
P3 is the SSID that identifies the SOLVE SSI region.
P4 is the system name where the region is running.
P5 is the NCLID of the process.
This message corresponds to an EPS error number 81.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because the SSI region cannot be contacted or does not include support for the packet analyzer. The SSID (p1) and system (p2) identify the SSI region where the request is issued. This can be the local SSI region or a remote region, possibly on another LPAR.
This message corresponds to EPS error numbers 39 and 70.
System Action:
The request fails.
User Action:
Check the following in the region running on p2:
Ensure that Packet Analyzer support is enabled by specifying PKTANALYZER=YES. Also ensure that the parameters include PALEVEL=FULL.
Only use a PALEVEL other than FULL if instructed by CA Support.
Note: Only one SOLVE SSI region (per LPAR) can include support for the Packet Analyzer.
Reason:
A Packet Analyzer request to the SOLVE SSI did not complete in a reasonable time. The SSID (P1) and system (P2) identify the SSI region where the request is issued to obtain or store data. This can be the local SSI region, or a remote region, possibly on another LPAR.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
An error occurred during initialization of CTAPI API. The meaning of the return and feedback codes are as follows:
FORMAT rejected - Interface not initialized
Invalid FORMAT call - Empty input buffer
Invalid FORMAT call - Buffer not empty
Invalid FORMAT call - Incomplete CTE in buffer
API load module EZBCTAPI load failure
API load module EZBNMCTF load failure
API format table EZBPTFM4 load failure
Internal prepare MDO failure
Internal assign MDO failure
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An error occurred in the EZBCTAPI Macro Interface. For more information about the meaning of the return and reason codes, see the z/OS Communication Server: IP Programmer's Reference manual.
System Action:
The current process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
The print request completed successfully and the output was sent to the printer.
System Action:
None.
User Action:
None.
Reason:
The print request for a trace report failed. An accompanying message gives the reason.
System Action:
The print request is aborted.
User Action:
Check the accompanying message for an action.
Reason:
The generation of trace reports is in progress.
System Action:
Processing continues and the details of the status panel are refreshed.
User Action:
None.
Reason:
An unrecoverable error has occurred while generating the trace reports.
System Action:
Processing terminates.
User Action:
Regenerate the trace reports. If the condition persists, contact Technical Support. Provide the activity log from the time an attempt was made to generate trace reports till after this message is written to the log.
Reason:
Trace Report generation is canceled.
System Action:
Processing terminates.
User Action:
None.
Reason:
A request to generate trace reports ended with no errors but with no reports generated.
System Action:
None.
User Action:
Review the activity log for possible error messages; otherwise, contact Technical Support for assistance.
Reason:
Errors detected during trace report generation may be caused by having an incomplete or inaccurate set of reports.
System Action:
Processing ends with error messages written to the activity log.
User Action:
Review the activity log for the cause of the error and take appropriate action. If necessary, contact Technical Support for assistance.
Reason:
A request to generate trace reports ended with errors and with no reports generated.
System Action:
Processing ends with error messages written to the activity log.
User Action:
Review the activity log for the cause of the error and take appropriate action. If necessary, contact Technical Support for assistance.
Reason:
A request sent to the internal report data server detected that the server is no longer available.
System Action:
The current list display terminates.
User Action:
Contact Technical Support for assistance.
Reason:
A request sent to the internal report data server timed out.
System Action:
The current list display terminates.
User Action:
Contact Technical Support for assistance.
Reason:
A request to print a report failed because the selected printer uses a form that has less than P1 columns.
System Action:
Print request is rejected.
User Action:
Perform the following steps:
Reason:
The print request was submitted to the background. When the print is complete, a notification is sent.
System Action:
None.
User Action:
None.
Reason:
Print request failed with error messages written to the activity log.
System Action:
None.
User Action:
Review the activity log to determine the cause of the error and take appropriate action.
Reason:
Errors are detected in the panel input field; P1 is the explanation.
For the Dataset or HFS file field, P1 provides the following explanation:
Indicates that the specified text is not an HFS file name.
Indicates that the specified text does not have a PDS member name.
Indicates that the specified text does not conform to HFS path-naming rules.
Indicates that the specified HFS path either does not exist or is not available for processing the request.
Indicates that a relative HFS directory path was specified, which is not supported.
Indicates that the specified text does not conform to HFS file-naming rules.
Indicates that the specified HFS file is an existing HFS directory.
Indicates that the specified text does not conform to PDS member naming rules.
Indicates that the specified text does not contain a valid SYSOUT class.
Indicates that the specified text does not contain a qualified DSN.
Indicates that the specified name points to a data set that is not valid for this function.
Indicates that the specified name points to a data set that is not a partitioned data set.
Indicates that the target data set has a logical record length less than n bytes.
System Action:
None.
User Action:
Correct the indicated error, and retry the operation.
Reason:
The value entered is not a valid data set name or a valid HFS file path and name.
System Action:
Field is set in error.
User Action:
Specify a valid data set name or a valid HFS file name.
Reason:
The saving of trace reports is in progress.
System Action:
Processing continues and the details of the status panel are refreshed.
User Action:
None.
Reason:
The save request for the selected report ended without errors.
System Action:
None.
User Action:
None.
Reason:
The save request for the selected report ended without errors. You can retrieve it from the JES spool with DDNAME(P1) of this CA NetMaster region.
System Action:
None.
User Action:
None.
Reason:
The remote system is at a maintenance level that does not support the P1 function.
System Action:
the process terminates.
User Action:
Update the remote region to the same maintenance level as the local region.
Reason:
Access to the SmartTrace packet data has not been granted by your site's security system.
System Action:
Packet data is restricted to IP and protocol headers.
User Action:
Contact your security administrator.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
You are not authorized to use the SmartTrace facility.
System Action:
The SmartTrace function is not performed.
User Action:
Contact your security administrator.
To access SmartTrace, your User ID must be defined to UAMS with a TCP/IP Services value of 2.
For more information, see the Security Guide.
Reason:
Verification by your external security system has failed. A SAF VERIFY check on user ID P1 resulted in SAF RC=4 and security system RC=4. This probably indicates that resource NETMSTR.PKTTRACE.region of class FACILITY is not defined.
System Action:
SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
Contact your security administrator.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
Verification by your external security system has failed. A SAF VERIFY check on user ID P1 has resulted in SAF RC=8 and security system RC=28 (x'1C'), indicating that user access is revoked.
System Action:
User P1 is restricted to viewing IP and protocol headers.
User Action:
Contact your security administrator.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
A SAF call to verify access to the SmartTrace facility failed with an unexpected error. This message, together with messages IPPTPKG11 and IPPTPKG12, is written to the activity log, which contains information about the return code and reason code.
System Action:
SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
Review the messages in the activity log.
Contact your security administrator.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
This message is part of a message set that is written to the activity log when an unexpected SAF resource check error occurs. The message shows the paramater string that was passed to the SAF program, NM022.
System Action:
SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
See messages IPPTPKG10 and IPPTPKG12.
Reason:
This message is part of a message set that is written to the activity log when an unexpected SAF resource check error occurs. The message shows the response details returned by the SAF program, NM022.
REQ=P1 is the RACROUTE REQUEST=operand
SAFRC P2 is the SAF (RACROUTE) return code (R15)
SECRC P3 is the security system return code
SECREAS P4 is the security system reason code
For more information about the RACROUTE request macros, and the associated return codes and reason codes, see the (IBM) RACF System Macros manual. The most common SAFRC/SECRC combinations are:
04 PROGRAM ACTIVATION FAILURE
04 Program not APF-authorized
08 Invalid parameter
0C Missing parameter
10 Parameters inconsistent
08 SAF INTERFACE FAILURE
SAF/RACROUTE return codes:
04 Requested function was not processed
08 Requested function was processed, but failed
12 ACCESS VERIFICATION FAILURE
RACROUTE REQUEST=VERIFY return codes:
04 No security profile defined
08 Password invalid
0C Password expired
10 New password invalid
14 Group definition is missing
18 Security exit denied access
1C User temporarily revoked
20 Security system not active
24 Access to group is revoked
?? Others as per specific security subsystem
16 ACCESS AUTHORIZATION FAILURE
RACROUTE REQUEST=AUTH return codes:
04 Resource is not security protected
08 Resource access not allowed
99 NO ENTRY PARAMETERS
System Action:
SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
Contact your security administrator. Use the error codes and messages provided above to investigate the cause of the error. You also need:
Ensure that the region is running out of an authorized load library. Ensure that your external SAF security system is active.
Ensure that your security administrator has set up SAF security for use with this region correctly.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
An error has occurred calling the SAF program, NM022. P1 describes the error.
System Action:
The message, and for some errors message IPPTPKG11, is written to the activity log. SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
This is an internal error that should be reported to your product supplier.
Reason:
The internal connection ID cannot be obtained for a given connection. This temporary condition occurs when a connection existed before the SSI region was initialized.
System Action:
None.
User Action:
None.
Reason:
A request for a syntax check of expression P1 has ended with no errors.
System Action:
None.
User Action:
None.
Reason:
A request for a syntax check of expression P1 is not possible because nothing is specified.
System Action:
Request rejected.
User Action:
None.
Reason:
The connection cannot be found using the Packet Analyzer or NetStat. The most likely cause is because the connection has recently closed.
System Action:
None.
User Action:
None.
Reason:
The connection is not visible to the Packet Analyzer. This may be because the stack is not being processed by the Packet Analyzer, or the connection has recently closed, or the connection has been idle since before the SOLVE SSI region started.
System Action:
None.
User Action:
None. It is not possible to start a trace of this connection at this time.
Reason:
A multiple TCP connection trace has reached its specified maximum number of connections.
System Action:
No further traces are created for P1.
User Action:
None.
Reason:
A multiple TCP connection trace has attempted to trace a new connection, but the attempt failed because the trace database has insufficient storage.
System Action:
Trace creation does not occur. Packets from the connection are not traced.
User Action:
To see the current SSI trace database size, use /IPTEST.
To free space in the trace database, delete any ACTIVE or ENDED trace that is no longer required.
If this condition occurs frequently, consider increasing the database size on the next restart of the SOLVE SSI region. The database size is set by SSI startup parameter, PTRCDBSIZE.
Reason:
A SmartTrace trace has stopped or is in the process of stopping because the defined stop condition has been matched.
System Action:
If a numeric value other than 0 was defined for the Packets After Stop option, the trace waits for the specified number of extra packets to be collected; otherwise, the trace ends.
User Action:
Review the trace results.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because the SSI is running with an old version of the software.
System Action:
The request fails.
User Action:
Update the SSI to the latest version of the product.
Reason:
The payload data in the packet is not displayed because your user ID is not authorized to view packet data. To view packet data, your user ID must have read access to resource NETMSTR.PKTTRACE.region in your external security package.
System Action:
SmartTrace packet viewing is restricted to IP and protocol headers only.
User Action:
Contact your security administrator.
For more information about SmartTrace security requirements, see the Security Guide.
Reason:
An error occurred decoding an IP packet. P1 provides details about which part of the packet caused the error.
System Action:
The packet is not completely decoded.
User Action:
Contact Technical Support.
Reason:
A request to display recent traffic statistics could not be satisfied because the Packet Analyzer has seen no packets to or from address p1 in the last hour.
System Action:
The action is rejected.
User Action:
If traffic is expected, check the status of the remote address.
Reason:
A request for a list of remote addresses has been sent to the Packet Analyzer. The request failed because the Packet Analyzer has seen no activity from stack P1 to any remote address in network P2 (if shown), or else no activity to any remote address.
System Action:
The request fails.
User Action:
If the Packet Analyzer has been restarted recently, wait a while and reissue this command. If the Packet Analyzer has not been restarted recently, check the status of the network.
Reason:
The SSI is currently running with PALEVEL set to NOPACKETS or NOSTATS. Packet statistics are available only when PALEVEL is FULL.
System Action:
The RI command displays without packet statistics. The BI command is not displayed.
User Action:
Check why the SSI is not running with PALEVEL=FULL.
The PALEVEL setting can be altered using the SSI's PACTL command. SSI commands can be entered from a region using the SSISEND command, for example:
SSISEND PACTL PALEVEL=FULL
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
A request was received to retrieve the IBM 2216 router definition called
P1 but no such router definition exists.
System Action:
None.
User Action:
Check the name of the router definition requested. If it is correct, investigate why the definition has been deleted.
Reason:
A request was received to add or update multiple IBM 2216 router definitions in a single request. This is not supported.
System Action:
The request is rejected.
User Action:
Request only one update at a time.
Reason:
A request was received to add an IBM 2216 router definition called P1 but a router definition with that name already exists.
System Action:
The request is rejected.
User Action:
Choose a different name for the router definition, or update the definition that already exists.
Reason:
An MDO assignment failed with ZMDORC 16 and ZMDOFDBK 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated for TCP/IP Services.
Reason:
An MDO assignment failed. The MAP was P1 , the MDORC was P3 , the MDOFDBK value was P4 , and the MDO component involved in the last operation was P2.
System Action:
The action terminates.
User Action:
See the NCL Reference for details of the codes.
Reason:
When a router definition is updated, save processing issues a request to change the current monitoring status of the router to reflect the current settings. A request to start monitoring activity for router P1 has failed.
System Action:
None
User Action:
The message preceding this message indicates the cause of the failure.
Reason:
A request was received to perform an action on an IBM 2216 router, but during processing it was determined that the specified device is not a valid router.
System Action:
The action terminates.
User Action:
Correct the IP Address in the router definition and retry.
Reason:
The requested maximum number of connections ( P1 ) has been reached but more connections satisfy the criteria. The remaining connections are ignored.
System Action:
None.
User Action:
If more connections are required, increase the Max Connections option and retry.
Reason:
An unexpected error occurred when the Router TN3270 Server information procedure was allocating the vartable used to store the returned information.
System Action:
The action terminates.
User Action:
Contact your System Administrator.
Reason:
An action has been attempted for a TN3270 client connection through a router. The action required details about the connection to be passed in an MDO called $IPCONN. However, either this MDO has not been passed or it is not mapped correctly.
System Action:
The action terminates
User Action:
Contact your System Administrator.
Reason:
An action has been attempted for a TN3270 client connection through an IBM 2216 router. The action required details about the connection to be passed in an MDO called $IPCONN. However, some of the data which should be present in the MDO is not present.
System Action:
The action terminates
User Action:
Contact your System Administrator.
Reason:
A request was received to perform an action on a TN3270 client connection, but the request has failed because the specified connection has ended.
System Action:
The action terminates.
User Action:
Refresh the connection list display.
Reason:
A request was received to obtain monitor data for the IBM 2216 router
P1 but monitoring is not active for this router.
System Action:
The action terminates.
User Action:
None
Reason:
A request was received to obtain monitor data for IBM 2216 router P1 but all attributes requested had a monitoring status of 'inactive'.
System Action:
The action terminates.
User Action:
None
Reason:
Your request cannot be processed because the 2216 router at address P1 does not have an active TN3270 server.
System Action:
The request is not processed
User Action:
Determine why there is no active TN3270 server at that address, or re-issue the request using a different address.
Reason:
The TCP/IP Router Tn3270 Server procedure $IPRT17L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT17L terminates.
User Action:
Correct the NCL procedure which caused execution of $IPRT17L. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPRT17L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT17L terminates.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter was omitted from the call to $IPCALL. One of either ADDRESS, HOSTNAME or HOST must be specified.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPRT20L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT20L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPCP21L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT21L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPRT22L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT22L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPRT30L failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPRT30L terminates.
User Action:
Contact your System Administrator.
Reason:
The attempted action is not valid in the following places:
- On the selected LU or,
- On display lines that are not LUs.
System Action:
None.
User Action:
None.
Reason:
You entered an action on the routing table list that cannot be processed. For example, you entered the R option to view the routing table for a router, but the route selected is a direct one (that is, no router is used).
System Action:
None.
User Action:
Correct the action and retry.
Reason:
You entered an action on the routing table list that cannot be processed. For example, you entered the R action to view the routing table for a router, but the route selected is a direct one (that is, no router is used).
System Action:
None.
User Action:
Correct the action and retry.
Reason:
A request to enable management for a TCP/IP stack ( P1 ) was accepted.
System Action:
Packet analysis for the stack is enabled if not already enabled. It may be already enabled by a previous request by either this NetMaster region, or another NetMaster region in the same LPAR that has defined the stack resource.
User Action:
None.
Reason:
A request to disable management for a TCP/IP stack ( P1 ) was accepted.
System Action:
Packet analysis for the stack is disabled if there are no other NetMaster regions in the same LPAR that are managing this stack.
User Action:
None.
Reason:
Packet Analyzer cannot see the packets on the P1 stack.
A possible cause is that this is a CA TCPaccess stack that does not have the requisite level of maintenance for Packet Analyzer support.
System Action:
None.
User Action:
Do the following:
If the cause of the problem is not apparent, contact Technical Support.
Reason:
A request to enable or disable ( P1 ) management for a TCP/IP stack ( P2 ) failed.
System Action:
The packet analysis status for the stack is unchanged by this request. The stack may have been enabled by a previous request by either this NetMaster region, or another NetMaster region in the same LPAR that has defined the stack resource.
User Action:
This message is followed by another message stating the reason for the failure. If the message indicates that the SSI interface is inoperative, restart the SSI. For other errors, contact your product supplier.
Reason:
No performance history to display because the selected device is not being used by any stack interface.
System Action:
Request rejected.
User Action:
None.
Reason:
No devices were found for the selected resource P1 .
System Action:
Request rejected.
User Action:
Check the resource definition. Ensure the CHPID is valid and online.
Reason:
No details about the OAT table were returned from OSA/SF.
System Action:
None.
User Action:
None.
Reason:
A query call to OSA/SF returned in error, as shown in P1.
System Action:
The request for information from OSA/SF fails.
User Action:
See the Open Systems Adapter Support Facility User's Guide for more information on message P1.
Reason:
A request to sample attribute P2 failed because P3 did not return the data requested. This may be because the attribute specified is not applicable to the particular OSA, for example, Ethernet attributes specified for sampling on a token-ring OSA.
System Action:
No sample is available for this time period.
User Action:
Contact your local support representative.
Reason:
No devices were found for the OSA P1 .
System Action:
No sample is taken.
User Action:
Check the resource definition. Ensure the CHPID is valid and online.
Reason:
A request to determine the status of attribute P2 for OSA P1 failed.
System Action:
No sample is taken for this attribute but processing of other monitored attributes continues.
User Action:
Check the OSA definition for P1 . If the CHPID is that of a valid OSA device, contact Technical Support.
Reason:
An attempt to communicate with the OSA/SF task failed. P1 is the error message returned by the OSA/SF interface.
System Action:
Processing continues.
User Action:
Check the status of the OSA/SF task. If the condition persists, it may be necessary to stop and restart the OSA/SF task.
Reason:
An attempt to check the utilization of an OSA failed. P1 is the error message returned by the utilization routines.
System Action:
Processing continues.
User Action:
Ensure the CHPID value is correct.
Reason:
An attempt to check an attribute of OSA P1 has failed. The attribute P2 requires OSA/SF, but the OSA resource definition for P1 specifies that OSA/SF should not be used.
System Action:
The attribute sample is not taken.
User Action:
Change the resource definition: either specify 'Use OSA/SF', or inactivate monitoring of attibute P2.
Reason:
An attempt to check an attribute of OSA P1 has failed. The attribute P2 applies to OSA- Express and this OSA is an OSA-2, or vice versa.
System Action:
The attribute sample is not taken.
User Action:
Change the resource definition in inactivate monitoring of attibute P2.
Reason:
As a result of your change to the 'Open System Adaptor Type' or the 'Use OSA/SF?' or 'Use SNMP?' field, some previously active monitoring attributes are no longer applicable. P1 attributes have been removed.
System Action:
None.
User Action:
Press F8 and review the monitoring attribute settings.
Alternatively, you may apply a new template to the resource definition. In the Template selection area, enter 'R' (Reset) and enter a '?' in the TemplateName field to display a list of templates suitable for the changed definition.
Reason:
An attempt to extract QDIO information for an OSA has failed. P1 is the error message returned by the QDIO routine.
System Action:
Processing continues.
User Action:
Ensure the CHPID value is correct.
Reason:
An attempt to extract QDIO information for OSA P1 has returned no data.
System Action:
Processing continues.
User Action:
Contact your systems administrator.
Reason:
An attempt to monitor an attribute of OSA P1 has failed. Monitoring of attribute P2 is only supported on z/OS version P3 or later.
System Action:
The attribute sample is not taken.
User Action:
Change the resource definition to inactivate monitoring of attibute P2.
Reason:
A request was received to retrieve the OSA definition called P1 but no such definition exists.
System Action:
None.
User Action:
Check the name of the OSA definition requested. If it is correct, investigate why the definition has been deleted.
Reason:
A request to produce an OSA utilization analysis failed because there were no stacks registered as running on the same processor on which the OSA is installed. The processor ID on which the OSA is installed is P1.
System Action:
No OSA utilization analysis is generated.
User Action:
Ensure that this SOLVE region is linked to all SOLVE regions that are running on processor P1 and that these SOLVE regions are monitoring the stack interfaces of all stacks that are using the OSA being analysed.
Reason:
A request to view the performance data for an OSA card could not be processed because the OSA specified does not have performance monitoring defined.
System Action:
None.
User Action:
Select an OSA that has performance monitoring specifications defined or define performance monitoring for the OSA.
Reason:
A command was received to display information about resource P1. The display could not proceed because the resource definition contains a chpid value P2 which is not an OSA chpid.
System Action:
The command is rejected.
User Action:
Update the resource definition and correct the chpid value.
Reason:
The requested function is not available. It is not supported by this release of the product.
System Action:
The request is rejected.
User Action:
This message generally occurs when a function is requested of a remote system which is running a later version than the local system. To perform this function on the remote system you will need to log on to that system.
Reason:
An attempt to extract status information for OSA CHPID P1 has failed. The return code from the OSAINFO verb is shown in P2 ;the feedback code is P3 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
An attempt to extract the device numbers for channel path P1 has failed. The return code from the OSAINFO verb is shown in P2 ;the feedback code is P3 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
$IPSA13Z was called with a request to gather information for CHPID P1 , but P1 is not a valid channel path identifier. Valid values are character strings representing hexadecimal values in the range 00 to FF.
System Action:
The request is rejected.
User Action:
Repeat the operation, specifying CHPID=xx, where xx is a channel path identifier.
Reason:
An attempt was made to call the OSA/SF Application Program Interface, but the API load module (IOAEXEC) could not be found.
System Action:
The call fails.
User Action:
Ensure that the OSA/SF load library SYS1.SIOALMOD is available to your region, by including it in either the linklist or the region's steplib concatenation.
Reason:
An attempt was made to call the OSA/SF Application Program Interface, IOAEXEC, but the call failed. p1 is the return code, p2 is the reason code, if available.
Possible return code values are:
4 = Warning. Command completed, but something the user should be aware of prevented successful completion.
8 = Error. Command did not complete successfully.
12 = Severe Error. Command did not complete successfully.
20 = Catastrophic error. The command failed, and the error prevented any reason code or further explanation from being returned.
40 = Memory allocation error occurred while trying to get storage to send the command back to the API. No data could be displayed.
41 = Control block sent to the API was too small. It must always be a minimum of a base control block.
For more information, refer to IBM's Open Systems Adapter Support Facility User's Guide For OSA-2.
System Action:
The call fails.
User Action:
If the reason for the failure is not evident, contact CA Technical Support.
Reason:
This message starts a block of debugging data written by $IPSA13Z.
p1 is either 'query' or 'response'.
System Action:
None.
User Action:
None.
Reason:
This message is part of a block of debugging data written by $IPSA13Z.
p1 is a dump of data to or from OSA/SF, in hexadecimal and graphic formats.
System Action:
None.
User Action:
None.
Reason:
This message ends a block of debugging data written by $IPSA13Z.
p1 is either 'query' or 'response'.
System Action:
None.
User Action:
None.
Reason:
An attempt has been made to access OSA/SF for a resource. The resource definition specifies that OSA/SF is not to be used.
System Action:
The action is rejected.
User Action:
Select a different action.
Reason:
An attempt was made to call the OSA/SF Application Program Interface, but the OSA/SF started task is not responding.
System Action:
The call is cancelled and the action fails.
User Action:
If the system is heavily loaded, wait and retry the operation; otherwise, it may be necessary to restart the OSA/SF started task.
For information about how to restart the started task, see the Open Systems Adapter Support Facility User's Guide.
Reason:
An attempt has been made to access SNMP data for OSA resource P1. This functionality is only supported on z/OS 1.4 or later.
System Action:
The action is rejected.
User Action:
Update the OSA P1 resource definition so that 'Use SNMP?' is set to NO. If OSA/SF is available, you can set the field 'Use OSA/SF' to YES to get equivalent functionality.
Reason:
An attempt has been made to access SNMP data for OSA resource p1 using stack p2. Access was unsuccessful because no IP address could be determined for the stack.
System Action:
The action fails.
User Action:
From Command Entry, enter SELFTEST and check for errors that are related to the socket interface. If no errors are reported, issue a Netstat command to the stack to check whether there is a problem with the Netstat interface.
For assistance, contact CA Support at http://ca.com/support.
Reason:
An attempt has been made to access SNMP data for OSA chpid P1. The attempt was unsuccessful. The SNMP query found no entry for the selected chpid in the MIB table.
System Action:
The action fails.
User Action:
Ensure that the OSA resource definition specifies the correct stack name and that the IOBSNMP task is running for this stack. If the cause of the problem is not apparent, contact your support representative.
Reason:
An attempt to extract LPAR names for OSA monitoring or display has failed. The retcode and feedback values provide further information. The retcode values have the following meaning: 8 Map $NMMPLPR not found on OSCNTL 12 System not running authorized 16 Internal error. FDBK contains the internal error indicator.
System Action:
OSA monitoring/display continues, with LPAR data identified by relative LPAR number rather than name.
User Action:
Contact your systems administrator.
Reason:
No devices were found for the selected resource p1.
System Action:
The request is rejected.
User Action:
Review the resource definition. Ensure that the CHPID is valid and online.
Reason:
A query call to OSA/SF returned in error. p1 identifies the error.
System Action:
The request for information from OSA/SF fails.
User Action:
For more information about p1, see the IBM Open Systems Adapter Support Facility User's Guide.
Reason:
No details about the OAT were returned from OSA/SF.
System Action:
None.
User Action:
None.
Reason:
No stack interface is using the device. The device has no performance history to display.
System Action:
The request is rejected.
User Action:
None.
Reason:
No stack interface is using the device. The device has no interface traffic data to display.
System Action:
The request is rejected.
User Action:
None.
Reason:
The IP System P1 is not connected to this product region. The specified IP System must be the system image name loaded on this or a linked product region.
System Action:
Field is set in error.
User Action:
Use '?' to select from a list of available IP Systems. If the product region that you wish to view is not in that list then it may be because the product region is not started or the link to the product regions is not active.
Use the shortcut /LISTREG to show the linked regions and the system image names loaded on those regions.
Reason:
An unsupported simple statistics type was received by module $IPSD00W.
System Action:
Procedure terminates in error.
User Action:
Contact Technical Support.
Reason:
A request to display IP statistics for the p1 region has failed because of one of the following causes:
System Action:
No statistics are displayed.
User Action:
If the region has started recently, wait for statistics to build up; otherwise, review the activity log for related error messages (for example, IPFA0204).
List the configuration details of this region (/IPTEST), and investigate any errors.
Reason:
A request to present IP statistics cannot be satisfied for one of the following reasons:
System Action:
No data is presented.
User Action:
Check the status of the SSI region.
If the SSI is active, check why it is not running with the SSI parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, we recommend that you always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions are not available.
Only use a PALEVEL other than FULL if instructed by CA Support.
Reason:
The value P1 is not a valid value for the IP System field. The summary data cannot be displayed because the IP System specified is not valid.
System Action:
Field is set in error.
User Action:
Specify a valid IP System name. The name must be that of the local system's loaded system image or of a connected region's loaded system image.
Reason:
A request to present a prompt list of IP Systems failed because no systems exist whose loaded system image matches the prefix specified. P1 is the specified prefix.
System Action:
Field is set in error.
User Action:
Specify a valid IP System name or use ? to get a prompt list of available names to choose from.
Reason:
A request to refresh the IP Traffic or Condition summary data was not performed because there is no new data available; however, you can refresh at P1 when new data is available.
System Action:
None.
User Action:
Refresh the screen after P1 to get the next available data.
Reason:
A request to refresh the IP Summary data is being processed. This may take a while. The screen will be automatically updated when it is ready.
System Action:
None.
User Action:
None.
Reason:
A request to change the view of IP Condition Summary is made while the condition monitor is still initializing. The view will change after the condition monitor has completed initialization.
System Action:
The request is processed, and the view will change when initialization completes.
User Action:
None.
When the condition monitor has initialized, the display will change to the requested view.
Reason:
A request to change the view of the IP Summary completed successfully. The new view settings are P1.
System Action:
None.
User Action:
None.
Reason:
The parameter passed to the VIEW command is invalid. The passed parameter is P1.
System Action:
Command rejected.
User Action:
Enter a valid parameter for the VIEW command. The syntax for the command is:
VIEW [ ALL | [COND] [TRAFFIC] [EETRAFFIC] [ALERT] ]
If no parameters are specfied, ALL is assumed and all components of the summary display are displayed. You can abbreviate the component keywords to the smallest number of characters to make them unique.
Examples:
1. View all components of the summary display: VIEW
2. View only conditions and EE traffic: VIEW CO EE
3. View IP traffic and alerts: VIEW TRAF AL
Reason:
A request to change the auto-refresh settings of the IP Summary completed successfully. The new settings are P1.
System Action:
None.
User Action:
None.
Reason:
The parameter passed to the AUTOREF command is invalid. The passed parameter is P1.
System Action:
Command rejected.
User Action:
Enter a valid parameter for the AUTOREF command. The syntax for the command is:
AUTOREF [ ALL | [COND] [TRAFFIC] [EETRAFFIC] [ALERT] ]
If no parameters are specfied, ALL is assumed and all components of the summary display are auto-refreshed. You can abbreviate the component keywords to the smallest number of characters to make them unique.
Examples:
1. Auto-refresh all components of the summary display: AUTOREF
2. Auto-refresh only conditions and EE traffic: AUTOREF CO EE 3. Auto-refresh IP traffic and alerts: AUTOREF TRA AL
Reason:
Tracing is active for the Application Traffic Explorer.
This message displays a trace record.
p1 is the NCL ID.
p2 is the trace ID.
p3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A request to present detailed traffic statistics could not be satisfied because no statistics are currently available to display.
System Action:
Procedure terminates.
User Action:
Wait until statistics have had time to build up. Ensure that you have configured your system to gather packet and byte statistics for your IP stacks.
Reason:
The TCP/IP Application Traffic Explorer has failed because of an internal error, the reason is p1.
System Action:
The Application Traffic Explorer process terminates.
User Action:
Contact Technical Support.
Reason:
The TCP/IP Application Traffic Explorer has failed because of an internal error.
Message IPSD0110 has the failure details.
System Action:
The Application Traffic Explorer process terminates.
User Action:
Locate message IPSD0110 in the activity log.
Contact Technical Support.
Reason:
There are no p1 traffic statistics currently available.
p1 is:
System Action:
Procedure continues.
User Action:
Wait until statistics have had time to build up.
Reason:
There was no p1 traffic for the selected time slot.
p1 is:
System Action:
None.
User Action:
None.
Reason:
The Date field indicated by P1 is either greater than or less than (as indicated by P2 ) the date indicated by P3 . 'From Date' must not be greater than 'To Date' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date fields indicated.
Reason:
The Date and time fields indicated by P1 are either greater than or less indicated by P2 ) the date and time indicated by P3 . 'From Date' and 'From Time' must not be greater than 'To Date' and 'To Time' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date and time fields indicated.
Reason:
The P1 fields require valid values.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
The IP address search string contains invalid characters or does not follow the expected text representation of an IP address. An IPv4 address uses a dot to separate numbers ranging from 0-255. An IPv6 address uses a colon to separate hexadecimal numbers ranging from 0-FFFF and a double colon to compress consecutive zeros. Mixed IPv4 and IPv6 address notations are not allowed.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
The field P1 must be less than the value specified in the field P2. These values are used to construct a logical search expression each of which is connected via the logical operator AND. A value cannot be greater than value X and at the same time less than value Y when it is already known that X is greater than Y.
System Action:
Fields set in error.
User Action:
Specify a smaller value in P1 than in P2.
Reason:
The value specified for field p1 must not contain embedded blanks.
System Action:
Validation of the search criteria fails.
User Action:
Review the value for field p1 and remove the embedded blanks.
Reason:
The values specified for the From Date and From Time fields cannot be the same or later than the values in the To Date and To Time fields.
System Action:
Validation of the search criteria fails.
User Action:
Review the values specified in all the date and time fields, making sure that they are in proper chronological sequence.
Reason:
The p1 fields require valid values.
System Action:
The validation fails.
User Action:
Specify value in the p1 fields.
Reason:
The IP address search string contains invalid characters or does not follow the expected text representation of an IP address. An IPv4 address uses a dot to separate numbers ranging from 0 to 255. An IPv6 address uses a colon to separate hexadecimal numbers ranging from 0 to FFFF, and a double colon to compress consecutive zeros. Mixed IPv4 and IPv6 address notations are not permitted.
System Action:
None.
User Action:
Correct the entry.
Reason:
The value in the p1 field must be less than the value specified in the p2 field. These values are used to construct a logical search expression through the logical operator AND. A value cannot be greater than x and at the same time less than y when x is greater than y.
System Action:
The fields are set in error.
User Action:
Specify a smaller value in p1 than in p2.
Reason:
The Date field indicated by P1 is either greater than or less than (as indicated by P2 ) the date indicated by P3 . 'From Date' must not be greater than 'To Date' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date fields indicated.
Reason:
The Date and time fields indicated by P1 are either greater than or less indicated by P2 ) the date and time indicated by P3 . 'From Date' and 'From Time' must not be greater than 'To Date' and 'To Time' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date and time fields indicated.
Reason:
The P1 fields require valid values.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
The IP address search string contains invalid characters or does not follow the expected text representation of an IP address. An IPv4 address uses a dot to separate numbers ranging from 0-255. An IPv6 address uses a colon to separate hexadecimal numbers ranging from 0-FFFF and a double colon to compress consecutive zeros. Mixed IPv4 and IPv6 address notations are not allowed.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
The field P1 must be less than the value specified in the field P2. These values are used to construct a logical search expression each of which is connected via the logical operator AND. A value will never be greater than value X and at the same time less than some other value Y, when it is already known that X is greater than Y.
System Action:
Fields set in error.
User Action:
Specify a smaller value in P1 than in P2.
Reason:
The Date field indicated by P1 is either greater than or less than (as indicated by P2 ) the date indicated by P3 . 'From Date' must not be greater than 'To Date' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date fields indicated.
Reason:
The Date and time fields indicated by P1 are either greater than or less indicated by P2 ) the date and time indicated by P3 . 'From Date' and 'From Time' must not be greater than 'To Date' and 'To Time' which must not be greater than the current date.
System Action:
Validation of the search criteria fails.
User Action:
Correct the values entered into the date and time fields indicated.
Reason:
The P1 fields require valid values.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
The IP address search string contains invalid characters or does not follow the expected text representation of an IP address. An IPv4 address uses a dot to separate numbers ranging from 0-255. An IPv6 address uses a colon to separate hexadecimal numbers ranging from 0-FFFF and a double colon to compress consecutive zeros. Mixed IPv4 and IPv6 address notations are not allowed.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
An SNA session monitor is now active for the resource indicated by P1.
System Action:
The Session Awareness interface (SAW) is used to trace the logical unit.
User Action:
None.
Reason:
An SNA session monitor has terminated.
System Action:
None.
User Action:
None.
Reason:
An attempt to start a session monitor has failed because the terminal is already being traced.
System Action:
Tracing is not started.
User Action:
None.
Reason:
A session monitor has failed.
System Action:
Tracing is terminated.
User Action:
Report this error to the System Administrator.
Reason:
A session monitor has detected an application output operation. P4 is the calculated application response time (or N/A if not known). The output operation is indicated by P5 and the data length by P6.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected terminal input data. P4 is the input operation code. P5 is the length of the data.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a terminal response to application data. P4 is the time elapsed since the output operation.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a negative terminal response to application data. P4 is the sense code.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a Pacing flow between the two network nodes P1 and P2.
P4 identifies the direction of the flow as either:
INBOUND - From P3
OUTBOUND - To P3
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a session control flow. P4 indicates the request type.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a response to a session control request.
P4 is the time elapsed since the output operation.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a response to a session control request without receiving a response to an earlier request as indicated by P1.
System Action:
None.
User Action:
None.
Reason:
A session monitor has detected a negative response to a session control request. P4 is the time elapsed since the output operation.
System Action:
None.
User Action:
None.
Reason:
An SNA session monitor has detected that the NTS ACB has been closed.
System Action:
The session monitor terminates.
User Action:
A SAW STOP command has most likely been issued. Check when Session Awareness may be restarted and issue the SAW START command.
Reason:
The remote system is at a maintenance level that does not support this function.
System Action:
The session monitor terminates.
User Action:
None.
Reason:
An event monitor is now active for the connection.
System Action:
Events which relate to the connection will be displayed.
User Action:
None.
Reason:
An event monitor has terminated.
System Action:
None.
User Action:
None.
Reason:
An event monitor has detected an event that is of interest to the requestor.
P1 identifies the event attribute class.
P2 identifies the event name.
P3 identifies the message number associated with the specific event.
System Action:
None.
User Action:
None.
Reason:
The remote system is at a maintenance level that does not support the event monitoring function.
System Action:
Events which relate to this connection will not be detected. Other monitoring events, such as the solicitation of connection details continue.
User Action:
None.
Reason:
An action for a UDP socket failed.
P1 is the action being performed.
P2 is the socket ID.
P3 is the return code.
P4 is the feedback code.
P5 is the error code.
P6 is the vendor error information.
System Action:
Processing terminates.
User Action:
Check the &SOCKET error code and vendor error information in the Network Control Language Reference Guide to determine the appropriate action.
Reason:
The response to an SNMP request contains a structure that cannot be interpreted by NetMaster for TCP/IP.
System Action:
The request fails.
User Action:
None.
Reason:
This is the first message of a group of messages that show the results of an SNMP MIB walk function. The MIB accessed is located at address P3 and the first MIB object to be retrieved will be the one with an object ID greater than P1 , which is the starting object ID. SNMP GetNext requests will continue until the limit is reached.
System Action:
SNMP MIB walk continues.
User Action:
None.
Reason:
This is a detailed message from a SNMP MIB walk request. P1 is the object ID of the MIB object retrieved and P2 is the value of the object.
System Action:
SNMP MIB walk continues.
User Action:
None.
Reason:
This is the last message returned from an SNMP MIB walk request. It indicates that the walk limit has been reached and that no more objects will be retrieved.
System Action:
None.
User Action:
None.
Reason:
An SNMP send failed. P1 is the failure reason.
System Action:
The action terminates.
User Action:
Determine the cause, and retry the operation.
Reason:
An SNMP request to host P1 resulted in an error status of P2 . For some requests the SNMP Object Identifier for which the error was detected is shown as P3 . The error status can have the following values: tooBig noSuchName badValue readOnly genError
System Action:
The action terminates.
User Action:
Determine the cause of the error and retry. If the error status is noSuchName then ensure that the Object ID specified in the request is correct.
Reason:
An SNMP request was issued for the destination host P1 and the request timed out. Subsequently, the host was pinged and a negative response was received, indicating that it is unreachable. This may occur for one
of the following reasons:
System Action:
The action terminates.
User Action:
Contact your System Administrator for the device to determine the cause and action.
Reason:
An SNMP request was issued for the host P1 , but no response was received within the timeout period. This may be due to one of the following reasons:
- The requestor's IP address is not in the host's access list
- A community name (other than public) is not specified
- The host SNMP agent is not active
- The device does not support SNMP
System Action:
The action terminates.
User Action:
Contact the System Administrator for the device, to determine the cause. Possible actions includes the following:
- Add the requestor's IP address to the host's access list
- Supply the correct community name
- Activate the host SNMP agent
Reason:
An SNMP version 3 response from host P1 contained an authorization digest that did not match the value expected.
System Action:
The response is rejected.
User Action:
Determine the cause of the error and retry.
Reason:
An SNMP version 3 response from host P1 could not be decrypted.
System Action:
The response is rejected
User Action:
Contact Technical Support.
Reason:
An SNMP version 3 request received a 'REPORT' PDU. P2 indicates the REPORT content.
System Action:
The response is rejected.
User Action:
Contact Technical Support.
Reason:
An SNMP version 3 discovery was unsuccessful. P3 indicates the component was not returned by the SNMP engine.
System Action:
The response is rejected.
User Action:
Ensure that the remote SNMP is correctly configured to support SNMP V3.
Reason:
An SNMP request to host P1 returned no valid data. This condition occurs only with SNMP v2 or v3 hosts.
System Action:
The action terminates.
User Action:
Check the SNMP host details for P1. Host details are accessed via
/IPADMIN.S . If the host details say that SNMP Version 3 is to be used, check that the user specified is associated with a view that includes the ibmTCPIPmvs MIB.
Reason:
A SNMP SETREQUEST has failed because an invalid type value has been supplied by the calling program. Valid values for type are:
For SNMP Version 1:
SIMPLE.NUMBER SIMPLE.STRING SIMPLE.OBJECT SIMPLE.EMPTY APPLICATIONWIDE.COUNTER APPLICATIONWIDE.GAUGE APPLICATIONWIDE.TICKS APPLICATIONWIDE.ARBITRARY
For SNMP Version 2 or 3:
SIMPLE.INTEGERVALUE SIMPLE.STRINGVALUE SIMPLE.OBJECTIDVALUE APPLICATIONWIDE.IPADDRESSVALUE APPLICATIONWIDE.COUNTERVALUE APPLICATIONWIDE.TIMETICKSVALUE APPLICATIONWIDE.ARBITRARYVALUE APPLICATIONWIDE.BIGCOUNTERVALUE APPLICATIONWIDE.UNSIGNEDINTEGERVALUE
System Action:
The SET request fails.
User Action:
None.
Reason:
An SNMP request to host P1 to read the ifTable resulted in an error response P2.
System Action:
The action terminates.
User Action:
If P2 is NOSUCHOBJECT and you are using SNMP v3 to access the host, make sure your SNMP v3 user is associated with a view that includes the IF-MIB.
Alternatively, this error message may indicate a problem with the host's MIB.
Reason:
An SNMP request cannot proceed. The target address is IPv6, but the sockets API on region P1 supports IPv4 addresses only.
System Action:
The action terminates.
User Action:
Check the SOCKETS parameter group (/PARMS) on region P1. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
An SNMP request cannot proceed. The sockets interface in region P1 is not active.
System Action:
The request terminates.
User Action:
To activate the sockets interface, enter /PARMS and action the SOCKETS parameter group.
Reason:
The source address is not a valid home address for the stack shown in P1. The source address is specified as part of the IP node resource definition. This error occurs because of one of the following reasons:
System Action:
The SNMP request terminates with a socket error.
User Action:
Specify a valid value in the Source Address field of the IP node resource definition.
Reason:
No dataset name specified.
System Action:
The action terminates.
User Action:
Retry, specifying the dataset name. The dataset is specified using the DSN= and MBR= operands as follows:
For a physical sequential (PS) dataset: DSN= full dataset name
For a member of a partitioned sequential (PO) dataset (a PDS), use one of two options:
- DSN= full dataset name, including the member name in parentheses. Example: DSN=PROD.TCPIP.IPTRACE(TRACE1)
- DSN= dataset name and MBR= member name. Example: DSN=PROD.TCPIP.IPTRACE MBR=TRACE1
Note that a specific member name must be entered; generic member names are not supported.
Reason:
The dataset name does not conform to OS/390 dataset name standards.
System Action:
The action terminates.
User Action:
Retry, specifying a dataset name in the correct format. The dataset is specified using the DSN= and MBR= operands as follows:
For a physical sequential (PS) dataset: DSN= full dataset name
For a member of a partitioned sequential (PO) dataset (a PDS), use one of two options:
- DSN= full dataset name, including the member name in parentheses. Example: DSN=PROD.TCPIP.IPTRACE(TRACE1)
- DSN= dataset name and MBR= member name. Example: DSN=PROD.TCPIP.IPTRACE MBR=TRACE1
Note that a specific member name must be entered; generic member names are not supported.
Reason:
The dataset name specified by the DSN= parameter is a partitioned dataset but no member name was supplied.
System Action:
The action terminates.
User Action:
Retry, specifying the dataset name and member name.
For a member of a partitioned sequential (PO) dataset (a PDS), use one of two options:
- DSN= full dataset name, including the member name in parentheses. Example: DSN=PROD.TCPIP.IPTRACE(TRACE1)
- DSN= dataset name and MBR= member name. Example: DSN=PROD.TCPIP.IPTRACE MBR=TRACE1
Note that a specific member name must be entered; generic member names are not supported.
Reason:
The dataset name specified using the DSN= parameter has a dataset organization which is not supported. The dataset organization must be either PS or PO.
System Action:
The action terminates.
User Action:
Retry, specifying the correct dataset name.
Reason:
The dataset name, or member, either does not exist or is empty.
System Action:
The action terminates.
User Action:
Retry, specifying another dataset name.
Reason:
The dataset identified by the DSN= and MBR= operands exists, but no TCP/IP Services trace header messages were found. Trace header messages are identified by message N3B106.
System Action:
The action terminates.
User Action:
Ensure that the correst dataset name and/or member name were specified. Check the dataset to ensure that it is an extract from a SOLVE activity log that contains SOLVE TCP/IP Services trace messages.
Reason:
The trace dataset is read and IP trace Receive and Send blocks are extracted and saved in an MDO. The MDO assignment for a block of trace data has failed because the size of the MDO exceeds the design limits. The location where this occurred is indicated by the relative (Receive or Send) block count ( P1 ), and the input line number ( P2 ).
System Action:
The action terminates.
User Action:
The trace dataset must be split to multiple datasets. Use the line number as a guide - split the dataset at the beginning of a Receive or Send block preceeding the indicated line number.
Reason:
The associated PDU is an SNMPv3 PDU which is encrypted. The trace formatter is unable to decrypt the PDU. This means that some information (such as reqtype and OID#) is unavailable and will show blank in the selection list.
System Action:
Processing continues.
User Action:
The trace formatter will decrypt encrypted PDUs if a SNMP host details record exists for the remote IP address, and the record contains a privacy key applicable to the traced PDU. Check the host details using /IPADMIN.S
Reason:
The request to display the routing table for the specified host failed as the routing table cannot be accessed. Possible causes include:
- SNMP not authorized
- no routing table exists. This may be a gateway host or bridge.
System Action:
None.
User Action:
None.
Reason:
A procedure was passed an invalid keyword value. The keyword in error was P1 and the invalid value was P2 .
System Action:
The action terminates.
User Action:
Contact your System Administrator.
Reason:
An MDO assignment failed with ZMDORC 16 and ZMDOFDBK 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated for the TCP/IP Services.
Reason:
An MDO assignment failed. The MDORC was P1 , the MDOFDBK value was P2 , and the map where the error was detected was P3.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
An SNMP request cannot proceed. The target address is IPv6, but the sockets API on region P1 supports IPv4 addresses only.
System Action:
The action terminates.
User Action:
Check the SOCKETS parameter group (/PARMS) on region P1. For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
An error occurred loading the object ID translate table. The following message is a more specific explanation of the problem.
System Action:
The object ID translate table is not used.
User Action:
Check the following message in the log for cause and action details.
Reason:
A vartable error occurred. The vartable action was P1 and the feedback code was P2 . If relevant, P3 contains the key value which experienced the problem.
System Action:
The action fails.
User Action:
Determine the cause of the error based on the feedback code.
Reason:
You have entered an incorrect value in the IP address/mask field.
P1 may provide additional information.
System Action:
The value is rejected.
User Action:
Enter a valid IP address/mask.
The following are valid for IPv4:
The following are valid for IPv6:
Reason:
You are attempting to do a COPY but the IP address/mask specified already exists.
System Action:
The IP address/mask field is highlighted.
User Action:
Enter a new IP address/mask value.
Reason:
You have entered an IP address/mask containing an address range. The range overlaps an aready defined address range, P1 .
System Action:
The IP address/mask field is highlighted.
User Action:
Enter a different IP address/mask.
Reason:
The Security Level value indicates either authentication or privacy. One or other of the fields specified in P1 and P2 is required.
System Action:
The two fields are highlighted.
User Action:
Enter a value in field P1 or P2 .
Reason:
An invalid value has been entered in field P1 . Correct values for this field are described in P2 .
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
The field P1 has been omitted. This field is required when field P2 has the value P3 .
System Action:
The omitted field is highlighted.
User Action:
Enter a value in the field.
Reason:
You have specified V3 for the SNMP version but the IP address/mask field has a mask or range value. A version 3 definition can only be built for a single IP address.
System Action:
The value is rejected.
User Action:
Enter a single IP address.
Reason:
You have entered a password in a non-display field. This message prompts you to re- enter the password for confirmation.
System Action:
Processing continues.
User Action:
Re-enter the password.
Reason:
The password value entered for confirmation differs from the value first entered.
System Action:
The password value is rejected.
User Action:
Re-enter the password.
Reason:
An SNMP details record does not exist for the selected IP address/mask. It has been deleted since the selection list was last refreshed.
System Action:
The selection fails.
User Action:
Press F6 to refresh the selection list.
Reason:
An attempt has been made to generate an authentication or privacy key using the supplied user ID and password. The attempt failed. The key generation processs may need to access the remote host to discover the host's engine ID. This process can fail if the remote host is not currently available.
System Action:
The key is not generated.
User Action:
Either manually enter a key in the highlighted field, or retry later.
Reason:
Update is in progress on this definition by another user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
An attempt has been made to call $IPSP21U without supplying an IP address in MDO $IPDATA.
System Action:
The call is rejected.
User Action:
Contact Technical Support.
Reason:
A request to sample interface statistics for stack P1 failed because the stack's home address could not be determined.
System Action:
Interface sampling for the period is not performed.
User Action:
Check the status of the stack.
Reason:
An attempt to perform IP, TCP, and UDP monitoring failed. P1 shows the error message.
System Action:
No sample is taken.
User Action:
See message P1 for more information.
Reason:
An attempt was made to start the TCP/IP Trend Event Listener but it was already running.
System Action:
The existing TCP/IP Trend Event Listener continues processing.
User Action:
None.
Reason:
The TCP/IP Trend Event Listener encountered an error when trying to do a P1 command on the IPFILE database. The return code is P2. The TCP/IP Trend Event Listener will not accumulate this hourly summary data into the total summary for this 4-hour or daily period.
System Action:
The TCP/IP Trend Event Listener ignores this event and continues processing. The accumulated trend record(s) for the device/attribute shown will not include the data from this hourly summary event.
User Action:
Determine why the NDB error occurred. Contact your Systems Administrator for further assistance.
Reason:
The TCP/IP Trend Event Listener has set its profile and is ready to receive and process summary trend events from the IP Node Monitor, CISCO Interface Processor, and TCP/IP Stack.
System Action:
The TCP/IP Trend Event Listener commences processing.
User Action:
None.
Reason:
An MDO ASSIGN error occurred. The MDO is identified by P1 the ASN1 map name by P2 the return code by P3 and the feedback code is P4 .
System Action:
The TCP/IP Trend Event Listener terminates. No trend data can be collected until this problem is rectified and the procedure restarted.
User Action:
Contact your Systems Administrator. Probably an installation error. Ensure that the ASN1 map named in the message has been correctly installed.
Reason:
The TCP/IP Trend Event Listener encountered a P1 that it did not recognize for resource P3 , attribute P4 . The value of the unknown
P1 was P2 .
System Action:
The TCP/IP Trend Event Listener ignores this trend event and continues processing.
User Action:
None.
Reason:
The TCP/IP Trend Event Listener generated a key length that was too long for IPFILE. The length of the key was P1 and the value of the key was " P2 ".
System Action:
This record is not added to IPFILE. The data for the resource and attribute shown in the key are not accumulated in any trend data. The Trend Event Listener ignores this event and continues processing.
User Action:
None.
Reason:
An IPFILE record was found for key P3 but the existing record type of
P2 does not match the incoming event type of P1
Possible internal causes include: More than one monitor using the same attribute identifier. A monitor changing its definition of the attribute identifier.
System Action:
The Trend Event Listener will ignore this event and continue processing.
Report data for this resource/attribute will be incomplete.
User Action:
Contact your Systems Administrator.
Reason:
The incoming trend event for resource ID P3 attribute P4 contains a summary P1 field value " P2 " which has an incorrect date or time format.
System Action:
The Trend Event Listener ignores this event and continues processing.
User Action:
None.
Reason:
The incoming trend event for resource ID P3 attribute P4 has an invalid P1 total field value of " P2 ".
System Action:
The Trend Event Listener ignores this event and continues processing.
User Action:
None.
Reason:
The incoming trend event for Resource ID P4 Attribute P5 has at least one invalid gauge avg/min/max value.
System Action:
The Trend Event Listener will ignore this event and continue processing.
User Action:
None.
Reason:
The incoming trend event for Resource ID P3 Attribute P4 has an invalid enumerated period/value pair. The period in minutes is " P1 " and the value is " P2 "
System Action:
The Trend Event Listener will ignore this event and continue processing.
User Action:
None.
Reason:
The number of trend events waiting to be processed by the Trend Event Listener has exceeded your system's NMIQLIM setting. All trend events exceeding this limit are discarded.
System Action:
The Trend Event Listener continues processing. Lost data cannot be accumulated and subsequent totals are inaccurate.
User Action:
Investigate why the message build up occured. If you are collecting trend data in a very large network, you may have maximum NMIQLIM value. Consider redesigning your application or contact Technical Support.
Reason:
A run time error was encountered by Trend Listener procedure $IPTD21W. This message heads a message group consisting of multiple instances of message IPTD2114. These contain details of the specific error, and information identifying the trend or summary event that caused the error
System Action:
The summary or trend event that caused the error is discarded. Processing continues with the next event.
User Action:
If this message appears continually, contact your Systems Administrator.
Reason:
This is part of a message group issued for run-time Trend Listener errors. It contains run- time error details, and information from the event that caused the error.
System Action:
The event is discarded. Processing continues with the next event.
User Action:
None.
Reason:
The trend report data for the resource and attribute referred to in the file key P1 is too long to be contained in a single IPFILE record. This is usually results when regular Trend Data Rollups have not been run. Trend Data Rollups delete old, expired data from the file, making room for the newest data to be added.
System Action:
The accumulated data for this period/resource/attribute is not updated. The new data is discarded and will not be reflected in future reports for this resource. The Trend Event Listener continues processing.
User Action:
Ensure that the Trend Data Rollup procedure $IPTD23W runs regularly. It should automatically run whenever the region starts: check the Activity Log for any errors. You can also set a regular daily rollup time using Customizer ( /PARMS ) Parameter group IPFILES 'Time of day to extract' files.
Reason:
An attempt was made to start the TCP/IP Trend Event Rollup Procedure but it was already running.
System Action:
The existing TCP/IP Trend Data Rollup Procedure continues.
User Action:
None.
Reason:
The TCP/IP Trend Data Rollup encountered an error when trying to do a P1 command on the IPFILE database. The return code is P2. The TCP/IP Trend Data Rollup can therefore not accumulate the data referenced by this key.
System Action:
Processing continues. The data for the resource and attribute shown in the key will be disregarded and will not be reflected in any totals.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
The TCP/IP Trend Event Rollup generated a key length that was too long for IPFILE. The length of the key was P1 , the value of the key was " P2 "
System Action:
This record will not be added to IPFILE. The data for the resource and attribute shown in the key will not be accumulated in any trend data. The Trend Event Rollup will ignore this data and continue processing.
User Action:
None.
Reason:
An MDO ASSIGN error occurred. The MDO is identified by P1 the ASN1 map name by P2 the return code by P3 and the feedback code is P4 .
System Action:
The TCP/IP Trend Data Rollup procedure terminates. No sequential IPTREND dataset will be produced.
User Action:
Contact your System Administrator. Probably installation error. Ensure that the ASN1 map named in the message has been correctly installed.
Reason:
An existing rolled into record was found, but its type did not match that of the rolled up record.
System Action:
Probable duplicate attribute IDs.
The Trend Data Rollup will ignore this data and continue processing.
User Action:
None.
Reason:
The TCP/IP Trend Data Rollup encountered an error when trying to do a P1 command on the IPTREND sequential file P4 . The action was P1 , the return code was P2 . Additional message information - " P3 "
System Action:
The unload step terminates. A sequential IPTREND dataset can not be produced.
User Action:
Determine why the error occurred. Ensure that the file is allocated, and the DSN is specified on the TCP/IP Administration (Reporting) panel. Check that the file has not run out of space. Contact your System Administrator for more assistance.
Reason:
The TCP/IP Trend Data Rollup procedure has finished with return code P2 For a 0 return code, IPTREND dataset P4 has been successfully produced. A code of 4 indicates a file error on either the IPFILE UDB VSAM file, or the IPTREND sequential dataset. A code of 8 indicates an ASN1 Mapping Services error.
System Action:
None.
User Action:
If the code was zero, the IPTREND file may now be transferred to the PC. For a non-zero code, check the log for detailed error messages and attend to these error conditions. Contact your System Administrator for more assistance.
Reason:
The TCP/IP Trend Data Rollup procedure is in progress. P1 indicates the current stage of processing.
System Action:
Processing continues with the step indicated.
User Action:
None.
Reason:
This message begins a message group detailing the processing just performed by a successful TCP/IP Trend Data Rollup. These details are for information only. P1 identifies the group being processed.
System Action:
None.
User Action:
None.
Reason:
This subheading or total line is part of message group IPTD2310.
P1 = "***" indicates the start of a subgroup.
P1 = "Total" indicates the end of a subgroup.
P2 identifies the subgroup of the group identified in message IPTD2310.
P3 in the Total line identifies the number of records affected.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of IP Node Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of CIP Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of Stack Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of VIPA Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
A run time error was encountered by Trend Rollup procedure $IPTD23W. This message heads a message group consisting of multiple instances of message IPTD2317. These contain details of the specific error, and information identifying the record that caused the error.
System Action:
Processing terminates. The IPTREND file is not updated.
User Action:
Contact your Systems Administrator.
Reason:
This is part of a message group issued for run-time Trend Listener errors. It contains run- time error details, and information from the record that may have caused the error.
System Action:
Trend Rollup Processing is abandoned. The IPTREND file is not updated.
User Action:
Contact your Systems Administrator.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of IBM 2216 records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of OSA records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of CSM Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of Address Space Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of Enterprise Extender Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
This detail line is part of message group IPDT2311.
P1 is the number of CICS Monitor records in this group.
System Action:
None.
User Action:
None.
Reason:
The Telnet connection diagram display utility encountered an internal error while processing a vartable.
P1 was the vartable action being attempted
P2 was the feedback code
P3 was the key (if relevant)
System Action:
The diagram is not displayed.
User Action:
Determine the cause of the error and retry.
Reason:
You requested an action on an object displayed on a Telnet connection diagram. The requested action is not supported by that object.
P1 is the name of the object.
System Action:
None
User Action:
Correct the action request, or retry on another object.
Reason:
An MDO assignment failed. The MDORC was P1 the MDOFDBK value was P2
System Action:
The action terminates.
User Action:
Refer to the NCL User Reference for details of the codes.
Reason:
You attempted to execute a command against a connection when a link name has been specified. This option is not available when viewing connections on a remote link.
System Action:
None.
User Action:
None.
Reason:
You attempted to obtain MAI session information when a link name has been specified and the link is to a system that is running a version of management services less than version 3.4. To be able to obtain MAI information, the remote SOLVE system must be running at version 3.4 or later.
System Action:
None.
User Action:
Upgrade the remote system or use NTS to obtain MAI session information.
Reason:
A response from the SOLVE system was not received within 20 seconds when issuing the command P1 .
System Action:
Could not complete requested function.
User Action:
Determine why the SOLVE system is not responding to the command and correct problem. Check for the message IPTN3107 in the log which will contain the last message received. If no messages were_received, this message will not be in the log.
Reason:
This message is written to the log due to a command not completing within 20 seconds. P1 is the text of the last message that was received before the command timed-out. The command that was issued is identified in the message IPTN3106 in the log.
System Action:
Could not complete requested function.
User Action:
Determine why the SOLVE system is not responding to the command and correct the problem.
Reason:
You attempted to obtain MAI session information but there is no INMC link to the SOLVE system that you wish to obtain the information from.
System Action:
None.
User Action:
Start an INMC link to the P1 SOLVE system. Note that this system must be running management services V3.4 or later.
Reason:
Userid P3 has issued a command to drop the telnet connection for LU P2 from the P1 IP connection.
System Action:
None.
User Action:
None.
Reason:
You attempted to obtain session information but there are no links to any SOLVE system on the same SSCP as the command target.
P1 is the CDRM name containing the target.
System Action:
None.
User Action:
Start an INMC link to a SOLVE system on the correct VTAM domain.
Reason:
A session monitor process has been requested to terminate.
System Action:
A STOP message is queued to the session monitor.
User Action:
None.
Reason:
Connectivity tests to the Telnet Server and Telnet Client are in progress.
System Action:
A PING is requested for the network components.
User Action:
None.
Reason:
A connectivity test to the Telnet server failed. No response was received within the timeout period.
System Action:
None.
User Action:
This indicates a failure in the IP network. Perform a traceroute for the Telnet Server IP address to determine the nature of the connectivity problem. If necessary, report the error to your Network Administrator.
Reason:
A connectivity test to the Telnet client failed. No response was received within the timeout period.
System Action:
None.
User Action:
This indicates a failure in the IP network. Use the TRACEROUTE function to determine the nature of the connectivity problem. If necessary, report the error to your Network Administrator.
Reason:
There are no log records currently stored for viewing.
System Action:
None.
User Action:
Wait for network connectivity tests to complete.
Reason:
Connectivity tests to the Telnet server and Telnet client are already in progress.
System Action:
Refresh processing continues.
User Action:
Wait for the current tests to complete before issuing the Refresh command.
Reason:
A session monitor start has been requested when the session monitor is already active.
System Action:
None.
User Action:
Wait for the session monitor to receive VTAM Session Awareness trace information or use the MONSTOP command to terminate the session monitor.
Reason:
A session monitor stop has been requested when the session monitor is not active.
System Action:
None.
User Action:
Use the MONSTART command to activate the VTAM session monitor.
Reason:
The NTS component is not available on the local system.
System Action:
None.
User Action:
Check that SNA components are licensed and available.
Reason:
The CALLTYPE parameter passed to the function is not supported.
System Action:
None.
User Action:
Report the error to your product support representative.
Reason:
A request to start or stop the monitor was accepted at the indicated time (P1). The action to be performed ( P2 ) is one of the following:
STARTED - the monitor has been started.
STOPPED - the monitor has been stopped.
System Action:
When the monitor is started, the connection will be tested approximately every 60 seconds (see note) until either the connection closes, or the monitor is stopped.
Note: If you leave this display to view another display (for example, by pressing F8=Alerts) while MonStart is active, the MonStart activity is suspended. When you return to the Transaction Path Analysis display after viewing the other display, MonStart activity and the update of displayed information resumes.
User Action:
None.
Reason:
Connectivity tests to the server and the client are in progress.
System Action:
A PING is requested for the network components.
User Action:
None.
Reason:
A connectivity test to the server failed. No response was received within the timeout period.
System Action:
None.
User Action:
This indicates a failure in the IP network. Perform a traceroute for the Telnet server IP address to determine the nature of the connectivity problem. If necessary, report the error to your Network Administrator.
Reason:
A connectivity test to the client failed. No response was received within the timeout period.
System Action:
None.
User Action:
This indicates a failure in the IP network. Use the TRACEROUTE function to determine the nature of the connectivity problem. If necessary, report the error to your Network Administrator.
Reason:
There are no log records currently stored for viewing.
System Action:
None.
User Action:
Wait for network connectivity tests to complete.
Reason:
A monitor start has been requested when the monitor is already active.
System Action:
None.
User Action:
None.
Reason:
A monitor stop has been requested when the monitor is not active.
System Action:
None.
User Action:
Use the MONSTART command to activate the monitor.
Reason:
A request to start the monitor has failed because the connection has closed.
System Action:
None.
User Action:
None.
Reason:
This message is the heading line for connection time samples for the Transaction Path Analysis facility. The details for each time sample is shown in message IPTP0712. The details in these messages are as follows:
P1 Time The time that the sample was taken.
P2 Bytes Out The number of bytes sent from the server to the client since the socket was opened.
P3 Kb/Sec The approximate data transfer rate for the difference in the number sent from the client to the server since the last sample.
P4 Bytes In The number of bytes sent from the client to the server since the socket was opened.
P5 Kb/Sec The approximate data transfer rate for the difference in the number sent from the server to the client since the last sample.
P6 Idle The time that the socket has been idle.
P7 (Warning Message) A warning message if there are apparent problems:
FTP HUNG An FTP connection (the client and/or server is using the FTP-D port) has been idle for over 60 seconds.
System Action:
The message is written to the Transaction Path Analyzer log.
User Action:
None.
Reason:
Refer to IPTP0711.
System Action:
Refer to IPTP0711.
User Action:
Refer to IPTP0711.
Reason:
A request to get the latest details for a specific connection was issued at the indicated time ( P1 ). The request failed as the connection has closed.
System Action:
The refresh and monitor functions are disabled. If monitoring was active it is stopped.
User Action:
Exit the TPA display.
Reason:
The CALLTYPE parameter passed to the function is not supported.
System Action:
None.
User Action:
Report the error to your product support representative.
Reason:
A request to get the latest details for a specific connection has failed as more than one connection details was returned by the NETSTAT processing routine. The number of connections returned was P1.
System Action:
No time sample is obtained but processing continues.
User Action:
This is an internal error which should be reported to your product supplier.
Reason:
The handler procedure $IPTP08H for the TCP/IP Transaction Path Analyzer failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and the procedure terminates. Control is returned to the procedure which called $IPTP08H.
User Action:
Contact your system administrator.
Reason:
This is a TRACERTE summary message which shows the destination host name ( P1 ), the number of hops ( P2 ) from the local host to the destination host, and the number of hops that have alerts ( P3 ). The path from the local host to the destination ( P4 ) is shown as a series of IP addresses.
For a hop to have an alert, it must be defined to the IP Node Monitor and have one or more active alerts.
System Action:
None.
User Action:
None.
Reason:
A transaction path analysis process has detected that the web client has exceeded a 10 minute inactivity timeout limit. This limit is used to prevent an accumulation of long running processes when the client has terminated without notifying the host.
System Action:
The process terminates.
User Action:
Limit the use of the 'Freeze graph' function to less than 10 minutes.
Reason:
The request connection no longer exists.
System Action:
The process terminates.
User Action:
Refresh the connection list to view an updated list.
Reason:
The TCP/IP external interface procedure $IPCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $IPCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The TCP/IP procedure $IPTN30S failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $IPTN30S terminates.
User Action:
Contact your System Administrator.
Reason:
The TCP/IP external interface procedure $IPCALL failed because a required parameter was omitted from the call to $IPCALL. One of either ADDRESS, HOSTNAME or HOST must be specified.
System Action:
The request is rejected and procedure $IPCALL terminates. Control is returned to the NCL procedure which executed $IPCALL. If $IPCALL was executed from OCS, control is returned to OCS.
User Action:
Contact your System Administrator.
Reason:
An MDO error occurred. The MDO is identified by P1 the map name by P2 the MDO return code by P3 and the feedback code is P4.
System Action:
The procedure terminates.
User Action:
Contact your System Administrator.
Reason:
A non-numeric value was entered for the field identified by P1 .
System Action:
The field in error is highlighted.
User Action:
Correct the field value and repeat the operation.
Reason:
A value was entered for the field identified by P1 which was not in the range specified by P2 and P3.
System Action:
The field in error is highlighted.
User Action:
Correct the field value and repeat the operation.
Reason:
The Traceroute operation failed because no entry for the host could be found.
System Action:
None
User Action:
Check the details entered are correct and retry the operation. If an error still occurs, contact your System Administrator.
Reason:
The Traceroute operation experienced a temporary failure.
System Action:
None
User Action:
Retry the operation. If an error still occurs, contact your System Administrator.
Reason:
No entries were returned for display.
System Action:
Control returns to the Primary Menu and the error message is displayed.
User Action:
Correct the entry in the Host Name field and retry.
Reason:
The Traceroute operation failed due to a nameserver error.
System Action:
None
User Action:
Contact your System Administrator.
Reason:
The Traceroute operation failed because the host does not support the protocol used.
System Action:
None
User Action:
Contact your System Administrator.
Reason:
There are currently no history details to present for P1. The sampling interval may not have expired and hence there may not be any data at this time.
System Action:
None.
User Action:
Ensure that statistics collection is set for the resource group that the resource belongs to.
Reason:
An MDO assignment failed. The MAP was P1 , the MDORC was P3 , the MDOFDBK value was P4 , and the MDO component involved in the last operation was P2.
System Action:
The action terminates.
User Action:
Refer to the NCL Reference for details of the codes.
Reason:
An MDO assignment failed with ZMDORC 16 and ZMDOFDBK 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated for TCP/IP Services.
Reason:
A request for IP Node Monitoring details for P1 was rejected because the resource is not being monitored.
System Action:
The action is rejected.
User Action:
Add the resource to those currently being monitored and ensure that the resource is in a resource group that has statistics collection active.
Reason:
You entered an invalid value in the Protocol field. Valid values are UDP or ICMP.
System Action:
The field in error is highlighted.
User Action:
Correct the field value and repeat the operation.
Reason:
The traceroute request did not reach the destination IP address within the number of hops specified.
System Action:
Traceroute terminates
User Action:
Increase the traceroute hop count and retry.
Reason:
The traceroute request terminated in error before reaching the destination IP address. The error P1 is one of the following:
System Action:
Traceroute terminates.
User Action:
If the error is Timeout, then increase the traceroute time-out value and retry. For all other errors, there is no recovery.
Reason:
Chorus TSF initialization failed while attempting to load the NMTSFREG product TSF registration module.
System Action:
Initialization is terminated.
User Action:
Ensure that the TSF registration module delivered with this product is accessible from this region. If this region is not using a //STEPLIB concatenation, specify the data set that contains the required module in the TSF Registration Library field in the $CH CHORUS parameter group.
For assistance, contact CA Support at http://ca.com/support.
Reason:
The Chorus TSF Date Feed was initiated, but it could not obtain an exclusive lock as another instance of this process is already running.
System Action:
This instance of the data feed process is terminated.
User Action:
Review the activity log for TCP/IP socket error messages that may prevent the data feed process from completing.
If necessary, take the following actions:
For assistance, contact CA Support at http://ca.com/support.
Reason:
An attempt to send data to Chorus TSF was terminated because Chorus TSF data feeds have been disabled in the $CH Chorus parameter group by specifying NONE for TSF Suffix.
System Action:
This instance of the data feed process is terminated.
User Action:
None.
Reason:
No data was collected for TSF Data Feed because of logic errors in the internal data retrieval routines.
System Action:
This instance of the data feed process is terminated.
User Action:
To determine the failing data retrieval routines, review the activity log entries before this message.
For assistance, contact CA Support at http://ca.com/support.
Reason:
The TSF Data Feed process for a CA Chorus instance ended with errors. P1 is the TSF suffix that identifies the instance.
System Action:
Processing continues.
User Action:
To determine the error, review the activity log entries before this message.
For assistance, contact CA Support at http://ca.com/support.
Reason:
The value of the specified parameter passed is invalid.
System Action:
None
User Action:
Correct the parameter and retry.
Reason:
The specified parameter is required for this call but has been omitted.
System Action:
None
User Action:
Specify the parameter and retry.
Reason:
This message is used by the S:NM-TCP/IP unsolicited system message facility to notify of registration or deregistration of interest in messages for a specified jobname
System Action:
None
User Action:
None
Reason:
TCP/IP Services registration of interest in unsolicited system messages has tried to notify a message listener process that resgitration has occurred but the notification process has failed with the return code shown.
System Action:
No messages can be receiver for this jobname
User Action:
Contact Technical Support.
Reason:
The S:NM-TCP/IP unsolicited system message registration facility has successfully updated message registration. This change is effective immediately.
System Action:
If registration was requested, messages will now be received for the requested jobname. If deregistration was requested, messages will no longer be received for the requested jobname, or for any jobname if no jobname was specified.
User Action:
None.
Reason:
The S:NM-TCP/IP unsolicited system message registration facility has been requested to deregister interest in receiving messages from a specific jobname or from all jobnames. The request has not caused any change because no registrations exist.
System Action:
None.
User Action:
None.
Reason:
The value of the specified parameter passed is invalid.
System Action:
None
User Action:
Correct the parameter and retry.
Reason:
The specified parameter is required for this call but has been omitted.
System Action:
None
User Action:
Specify the parameter and retry.
Reason:
The parameter shown is not allowed on this call but has been specified.
System Action:
None
User Action:
Remove the parameter and retry.
Reason:
An invalid request has been received by the TCP/IP Services unsolicited system message receiver.
System Action:
The request is ignored.
User Action:
Contact Technical Support.
Reason:
An unexpected message has been received by the TCP/IP Services unsolicted system message receiver.
System Action:
The message is logged and processing continues.
User Action:
Contact Technical Support.
Reason:
The TCP/IP Services unsolicited system message registration facility has attempted to register to receive job messages from Automation Services but the registration call has failed.
System Action:
No messages can be received from the specified job
User Action:
Contact Technical Support.
Reason:
The TCP/IP Services unsolicited system message registration facility has attempted to deregister for job messages from Automation Services but the deregistration call has failed.
System Action:
None
User Action:
Contact Technical Support.
Reason:
The VIPA is active on stack P1 on LPAR P2 but this stack is not defined to the managing NetMaster region on this LPAR.
System Action:
The port distribution table is not obtained.
User Action:
Check why the stack is unknown to the NetMaster region on LPAR P1.
Reason:
The VIPA is active on LPAR P1 but there is no NetMaster region in this LPAR to retrieve the port distribution table.
System Action:
The port distribution table is not obtained.
User Action:
Check the status of the NetMaster region on LPAR P1.
Reason:
A CR command has been actioned against VIPA P1. No connections are currently active for this VIPA.
System Action:
The command is rejected.
User Action:
Choose another command, or another VIPA resource.
Reason:
The displayable limit for VIPA connections has been reached.
System Action:
The list is truncated.
User Action:
Use $GLBL $VPDISPLIM nnnn to set the limit to a value up to 9999.
Reason:
The M command for a VIPA resource has been canceled.
System Action:
None
User Action:
None
Reason:
VIPADYNAMIC statements cannot be generated because errors were detected. The preceding messages in the activity log are prefixed with the link name of the system where the error occurred.
System Action:
The edit panel is shown with an incomplete set of VIPADYNAMIC statements.
User Action:
Update the VIPADYNAMIC statements as required. To determine the cause of the errors, do the following:
DOM link_name
If you are unable to determine the nature of the error, contact Technical Support.
Reason:
No value was selected from the selection list displayed.
System Action:
None
User Action:
None
Reason:
The stack P1 is invalid, because it is not known to this system.
System Action:
None
User Action:
Specify a different stack name or type '?' in the field to display a selection list of all known stacks.
Reason:
The stack P1 is invalid, because it is not an IBM stack. A dynamic VIPA can only be defined on an IBM stack.
System Action:
None
User Action:
Specify a different stack name.
Reason:
The stack P1 is invalid, because it is not on the same sysplex. The M command only supports VIPA modification within its current sysplex.
System Action:
None
User Action:
Specify a different stack name.
Reason:
You have entered the name of a PDS in the Obeyfile field. A member name is required. Please amend the dataset name to include a member name.
System Action:
None
User Action:
Add a member name to the end of the datasetname; for example, dataset(member). The member can be new or existing. If an existing member name is specified, the member will be overwritten.
Reason:
You have entered the name of a dataset in the Obeyfile field which has a format unsuitable for this function.
System Action:
None
User Action:
Enter the name of a dataset with PS or PO format. If a PDS is specified, include a member name (new or existing).
Reason:
The VIPA makes use of a stack on LPAR P1 but there is no NetMaster region on this LPAR to provide management information.
System Action:
The information for this LPAR is not obtained.
User Action:
Check the status of the NetMaster region on LPAR P1.
Reason:
The VIPA makes use of stack P1 on LPAR P2 but this stack is not defined to the NetMaster region P3 on this LPAR.
System Action:
The information for this LPAR is not obtained.
User Action:
Check the status of the NetMaster region P3.
Reason:
VIPA monitoring is not able to provide a total value for attribute P1 because the required component data is unavailable from LPAR P2.
System Action:
The total value is not provided.
User Action:
Check the status of the region on the named LPAR.
Reason:
VIPA monitoring is not able to provide a total value for attribute P1. This attribute depends on the sampling results of attribute P2. Attribute P2 has been marked INACTIVE in the VIPA definition.
System Action:
The total value is not provided.
User Action:
Change the status of attribute P2 to active, or change P1 to inactive.
Reason:
The VIPA is active on stack P1 on LPAR P2 but this stack is not defined to the managing NetMaster region on this LPAR.
System Action:
Monitoring of the associated VIPA attribute fails.
User Action:
Check why the stack is unknown to the NetMaster region on LPAR P1.
Reason:
An attempt to sample the distributedconnects or distributedlisteners attribute for a VIPA failed. A display of the VIPA's distribution port table returned no entries.
System Action:
Monitoring of the associated VIPA attribute fails.
User Action:
Check why the distribution port table is empty.
Reason:
An attempt to monitor the behaviour of a sysplex distributor VIPA has failed. The 'D TCPIP,SYSPLEX,VIPAD' output indicates that the VIPA is not distributing.
System Action:
Monitoring of the associated VIPA attribute fails.
User Action:
If this is not a sysplex distributor VIPA, inactivate the distributor attributes in the VIPA definition.
Reason:
An attempt to collect performance data for VIPA attribute P1 failed.
P2 contains the detailed error message.
System Action:
No data for VIPA attribute P1 is recorded for this interval.
User Action:
See the help for message P2 for more details.
Reason:
A request for information about VIPA P1 has failed. The VIPA is not known to the local stack P2.
System Action:
The request fails.
User Action:
Confirm that the VIPA resource definition specifies the correct local stack.
Reason:
A request to sample the performance of VIPA P1 has failed. Local stack
P2 is inactive.
System Action:
None
User Action:
Check why the stack is inactive.
Reason:
An attempt to check whether the VIPA resource P1 exists on a linked region has returned error message P2. This check is performed when the local stack resource has the field Create VIPA Resources? set to YES.
System Action:
The check process terminates for this VIPA.
User Action:
Investigate the cause of the error. The help for error message P2 may provide more information.
Reason:
An attempt to create a dynamic VIPA resource for VIPA P1 has returned error message P2. The resource is being created because the local stack resource has the field Create VIPA Resources? set to YES.
System Action:
The creation fails.
User Action:
Investigate the cause of the error. The help for error message P2 may provide more information.
Reason:
A request to display connections to a VIPA has failed. No stacks are available to display.
System Action:
None
User Action:
Check the status of stacks participating in this VIPA. The stacks may be inactive or they may be currently inaccessible to this region.
Reason:
A display of the connection routing table has been actioned against VIPA P1 . This display is supported only for sysplex distributor VIPAs.
P1 is not defined as a sysplex distributor VIPA.
System Action:
The action is rejected.
User Action:
Choose another action, or another VIPA resource.
Reason:
The VIPA is active on stack P1 on LPAR P2 but this stack is not defined to the managing NetMaster region on this LPAR.
System Action:
The connection routing table is not obtained.
User Action:
Check why the stack is unknown to the NetMaster region on LPAR P1.
Reason:
The VIPA is active on LPAR P1 but there is no NetMaster region in this LPAR to retrieve the connection routing table.
System Action:
The connection routing table is not obtained.
User Action:
Check the status of the NetMaster region on LPAR P1.
Reason:
An error occurred during a call to the CDI service. P1 is the error description.
The CDI service runs in the SSI region and is used to retrieve VIPA status information from the perspective of the sysplex.
System Action:
If the failure is not recoverable, the region reverts to retrieving the sysplex information through a system command, which can cause excessive output in the system log and the stack's JES job log if you are monitoring multiple VIPAs.
User Action:
Report this message to Technical Support.
Reason:
This is a hexadecimal dump of the invalid data returned from the CDI service used to extract dynamic VIPA information.
For more information about the error, see the IPVP1212 message preceding this block of messages.
System Action:
None.
User Action:
Report this message to Technical Support.
Reason:
An attempt to retrieve information about a dynamic VIPA through the CDI service has failed.
The CDI service runs in the SSI region and is used to retrieve VIPA status information from the perspective of the sysplex.
System Action:
VIPA monitoring reverts to retrieving the information using a system command. This can cause excessive output in the system log and the stack's JES job log if you are monitoring multiple VIPAs.
User Action:
Investigate why the CDI service is not available. It is enabled through SSI parameter CDI=YES.
Reason:
A background process to monitor VIPA movement has started or stopped for stack P2 . The process runs if the stack resource has the field Create VIPA Resources? set to YES.
System Action:
None
User Action:
None
Reason:
After Web Server initialization has completed, the TCP/IP product will be available for access via the URL P1 .
System Action:
None.
User Action:
Wait for the Web Server to become active, then use a browser to access the indicated URL.
Reason:
The web server has deregistered the TCP/IP product for access via the port P1 .
System Action:
None.
User Action:
None.
Reason:
An attempt to translate an object into an XML document for transmission to a data warehouse failed. The data was sourced from application P1, data class P2. The error occurred in mapping the object, the return code and feedback codes for the action were P3. P4 is the name of the component in error.
System Action:
The object is discarded and processing continues.
User Action:
Contact your local support representative.
Reason:
An attempt to translate IP sampling data for transmission to a data warehouse failed. The type of data is P1. The error message received was P2.
System Action:
The data is ignored and processing continues.
User Action:
Contact your local support representative.
Reason:
An attempt was made to run the IPTREND Data Warehouse Conversion Utility but the dataset name of the sequential IPTREND file to be converted was not specified via the DSN= keyword. The utility attempted to use the default IPTREND dataset name, but this has not been set. (The default name is usually set when a name is specified for the IPTREND dataset in the TCP/IP Administration / Set System Parameters / Reporting Configuration menu).
System Action:
The IPTREND Data Warehouse Conversion is not performed.
User Action:
Specify the dataset name of the IPTREND file using the DSN= keyword.
Reason:
The IPTREND Data Warehouse Conversion Utility encountered a file error attempting an operation on the sequential IPTREND file P5
System Action:
The IPTREND Data Warehouse Conversion is terminated. Conversion of all eligible IPTREND file records may not be complete.
User Action:
Correct the dataset error and retry the conversion.
Reason:
This is an informational message indicating that dynamic VIPA P1 has moved from lpar- stack P2 to P3.
System Action:
None
User Action:
None
Reason:
The message contains status information about the progress and status of the IPTREND Data Warehouse conversion.
System Action:
None.
User Action:
If the conversion fails, examine the log for specific error messages.
Reason:
The IPTREND Data Warehouse Conversion Utility could not correctly parse the sequential IPTREND file. There is a mismatch between the field seperator value present in the file (usually a comma) and the value of the DELIM keyword (defaults to a comma).
System Action:
The IPTREND Data Warehouse Conversion is terminated.
User Action:
Examine the IPTREND file to see what delimiter it was created with, and re-run the conversion specifying the correct DELIM value.
If the file delimiter is a comma, the default will be correct.
If the file delimiter is a semicolon, specify DELIM=SEMICOLON
If the file delimiter is the tab character (X'05'), specify DELIM=TAB
If the file delimiter is any other character, eg. / specify DELIM=/
If the DELIM keyword is omitted, a comma is used.
The delimiter or field seperator used in an IPTREND file is set on the NetworkIT NetMaster TCP/IP region that created the IPTREND file, in the Administration/Set System Parameters/Reporting Configuration menu.
An IPTREND file created on one NetMaster region may be converted to Data Warehouse format by another NetMaster region, providing:
a. The delimiter is correctly specified, if different from a comma.
b. The NetMaster regions run on the same OS/390 system. This is because the Sysplex and System ID from the converting region are assigned to any Resource records created by the conversion process.
Reason:
The IPTREND Data Warehouse Conversion Utility encountered a error while attempting to queue a Data Warehouse update for converted IPTREND file data. This message indicates the return codes from the Data Warehouse Adaptor code and details that identify the fact entry being added.
System Action:
The IPTREND Data Warehouse Conversion is terminated. Conversion of all eligible IPTREND file records may not be complete.
User Action:
Contact your support representative. Provide any Activity Log output associated with the failing conversion.
Reason:
An attempt was made to run the IPTREND Data Warehouse Conversion Utility but no Data Warehouse Services Servers have been defined on this region to receive the data.
Data produced by IPTREND file conversions, as well as live reporting data produced by a NetMaster Network Management for TCP/IP region, requires a Data Warehouse Services Server to be defined and active on the same region.
Sample and converted data is converted to an XML document format understood by the ReportCenter Data Warehouse Adaptor. These documents are placed on a queue in your VFS file for processing by the DWS Server.
The DWS Server takes documents from this queue and forwards them to the Data Warehouse Adaptor.
If too many documents accumulate in the queue without any active servers to forward them, queue overflows and consequent loss of data are likely.
System Action:
The IPTREND Data Warehouse Conversion is not performed.
User Action:
Define and activate at least one Data Warehouse Services Server, then retry the conversion. Servers are defined using Option MS.WS from this region's primary menu.
Reason:
An attempt to perform connection workload monitoring failed. P1 shows the error message.
System Action:
No sample is taken.
User Action:
See message P1 for more information.
Reason:
The connection workload monitoring procedure found that the Packet Analyser does not know about the P1 stack.
The most likely cause is that this is a CA TCPaccess stack that does not have the requisite level of maintenance for Packet Analyzer support.
System Action:
No connection workload monitoring is performed for this stack.
User Action:
Do the following:
If the cause of the problem is not apparent, contact Technical Support.
Reason:
An error has occurred during setup of FTP or Telnet workload monitoring. The event receiver has discovered the same hostname P3 is used by both stack P1 and P2 .
System Action:
All FTP workload for host P3 will be reported under stack P2. Any Telnet workload for host P3 that uses a telnet server running in its own address space will be reported under stack P2.
User Action:
Review why the two stacks have the same hostname. The event receiver uses the UNIX hostname command and DNR to extract stack hostnames.
Reason:
An error occurred while manipulating an NCL VARTABLE for Telnet or FTP workload monitoring. P1 is the resource being processed at the time of the error. P3 is the feedback code from the vartable P2 verb.
System Action:
None.
User Action:
Notify your systems administrator.
Reason:
During registration of stack P1 for FTP or Telnet workload monitoring, an attempt to invoke the UNIX HOSTNAME command failed. P2 is the error message returned from the UNIX interface.
System Action:
The failed operation is retried at intervals, if required. While the failure persists, the workload monitoring data for P1 may be incomplete.
User Action:
Notify your systems administrator.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
An internal error occurred because map P1 was not found in the map dataset.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
An internal error occurred. Map P1 experienced the error described by MDORC= P2 and MDOFDBK= P3 .
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
The site file loader utility has issued a system command to the operating system for execution but it has not been passed successfuly.
System Action:
None.
User Action:
None.
Reason:
The request to obtain workload manager information using the IWMSRSRS macro has failed. P1 contains the reason code describing the failure.
System Action:
None.
User Action:
Refer to IBM's MVS Workload Management Services manual for a description of the reason code.
Reason:
The request to obtain workload manager information has failed because an invalid parameter was passed.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The request to obtain workload manager information has failed because this region is not running APF authorized. APF authorization is required to issue workload manager macros.
System Action:
None.
User Action:
None.
Reason:
No TCP/IP stacks are registered with the Workload Manager.
System Action:
None.
User Action:
None.
Reason:
No stacks are registered with Workload Manager for the P1 Telnet cluster.
System Action:
None.
User Action:
None.
Reason:
There are no Telnet clusters registered with WLM for P1. Telnet clusters are registered using the WLMCLUSTERNAME statement.
System Action:
None.
User Action:
If the command was issued against a stack, the Telnet server may be running in its own address space. Issue the command against the ASMON resource for the telnet server. (Your site can define ASMON resources of type TNSERVER for such servers.)
Reason:
The stack or address space selected for the command is inactive.
P1 is the resource class.
P2 is the resource name.
System Action:
The command is rejected.
User Action:
None.
Reason:
The selected stack is not known to the system.
System Action:
The request is rejected.
User Action:
Enter ? in the Stack field to obtain a list of stacks.
List this region's configuration details (/IPTEST), and investigate any errors.
| Copyright © 2012 CA. All rights reserved. |
|