|
|
|
Reason:
The requested action requires a key field (P1) but it was not provided.
System Action:
None.
User Action:
Provide the field and retry.
Reason:
The low/only and high range values for a field (P1) do not represent a valid range. Either:
System Action:
None.
User Action:
Specify a correct range and retry. A correct range is either:
Reason:
All criteria were omitted; at least one field must be entered.
System Action:
None.
User Action:
Enter one or more fields.
Reason:
You have selected to update the default Connection Awareness Application Name Entry. Only certain fields of the default record can be updated. These fields are: Name Base and all the fields in the Processing Options section. Attempting to change any of the other values will result in an error.
System Action:
None.
User Action:
You may only change the fields listed above. Fields not specified may not be updated.
Reason:
A field on this panel (P1) has been omitted. It is a required field when the condition (P2) exists.
System Action:
Processing will not continue.
User Action:
Correct the value in the field, or cancel the operation.
Reason:
You have specified one IPv4 and one IPv6 address for the Remote Address criteria. This is not supported.
System Action:
Processing terminates.
User Action:
Correct the fields so that IPv4 or IPv6 addresses are specified. If you want to include other addresses, set up another rule.
Reason:
Stack management definitions for the local NetMaster region may not be purged if they are part of the current system image.
System Action:
None.
User Action:
Review on-line help for the TCP/IP : Packet Analysis Request List. This list provides the background to stack management requests, the impact of purging definitions, and how to remove definitions for the local region.
Reason:
The export of application definitions to the P1 data set is commencing the WRITE phase of processing.
System Action:
Processing continues.
User Action:
None.
Reason:
P1 lines of Packet Analyzer definitions have been written to the nominated export data set. The data set name is shown as part of activity log message FADBADF01.
System Action:
None.
User Action:
You can use the data set to import the definitions to another region using the Packet Analyser Utilities Menu. Because definitions are visible to all regions in an LPAR, you need only import definitions from one region.
Reason:
An FTP server FTP policy ruleset has been loaded. In the message:
P1 is the ruleset name.
P2 is the user ID who loaded the ruleset.
P3 is the region where the ruleset was loaded.
System Action:
The FTP server FTP policy, as defined by the named ruleset, is now active.
User Action:
None.
Reason:
An SSI database buffer pool has exceeded 80%.
P1 is the database type.
P2 is the SSI's SSID.
P3 is the SSI's job (or started task) name.
P4 is the current usage (%).
System Action:
An alert is raised. The alert is automatically cleared when the used percentage drops below 80%.
User Action:
The action depends on the database that is reporting the problem.
TRACE Database
The TRACE database stores IP packets traced by SmartTrace requests. Traced packets remain in the SSI database until they expire.
To reduce database usage:
DYNAMIC Database
The DYNAMIC database stores transient Packet Analyzer data such as connections, including connection history (closed connections). The IP application definitions determine how long a closed connection remains in the database. Closed connections are retained to enable viewing on a list of connections (shortcut /CONNCH).
To reduce database usage:
The Expiry Period column specifies the time (in minutes) that connections for this application remain in the database.
The changes are applied to any new connections and are not applied to existing open or closed connection records.
SYNCH Database
The SYNCH database contains in-storage copies of records that are stored on the SSIDB. This includes the Application Name Definition records described above.
To reduce database usage:
Increasing the database size
If this condition occurs frequently, consider increasing the database size on the next restart of the SOLVE SSI region. Database size is set by the following SSI startup parameters:
PTRCDBSIZE specifies the size of the TRACE database.
PDYNDBSIZE specifies the size of the DYNAMIC database.
PSYNDBSIZE specifies the size of the SYNCH database.
Reason:
This message indicates that a Packet Analyzer request to the SOLVE SSI has failed. The message includes the following details:
P1 is the API return code
P2 is the API feedback code
P3 is the MDO Key of the error field (if applicable)
P4 is the description for the API feedback code
System Action:
The request fails.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A Packet Analyzer request has failed because the data provided in the application MDO is mapped using an incorrect map name:
P1 is the package function that was called.
P2 is the map name that maps the data passed.
P3 indicates the expected map name.
System Action:
The request fails.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A Packet Analyzer request failed because the state for a persistent request action ( P1 ) is invalid. For example:
(a process can have only one active connection to the SSI)
System Action:
The request fails.
User Action:
Contact Technical Support.
Reason:
A request failed because the requesting user ID ( P1 ) does not have sufficient authority for this function ( P2 ). This function requires Administration and Definition authority (SF0511).
System Action:
The requested action is not performed.
User Action:
Contact your Security Administrator if access to this function is required.
Reason:
This message indicates that a Packet Analyzer request to the SOLVE SSI has failed. The message includes the following details:
P1 indicates the connection state when the error was detected:
Receive - when receiving data
Connresp - when receiving the response to a connect request
P2 describes the error reason.
System Action:
The request fails.
User Action:
This is an internal error. Contact Technical Support.
Reason:
This message indicates that a Packet Analyzer request to 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:
70 No SSI Connection 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 Sub-System Interface.
For all other errors, contact Technical Support.
Reason:
A request to read the next record in a selection sequence has failed because there are no more records. This message corresponds to a Packet Analyzer API feedback code of 8.
System Action:
The request fails.
User Action:
None.
Reason:
A request to read a record failed because the record does not exist. This message corresponds to a Packet Analyzer API feedback code of 10.
System Action:
The request fails.
User Action:
None.
Reason:
A request to add a record failed because the record already exists. This message corresponds to a Packet Analyzer API feedback code of 12.
System Action:
The request fails.
User Action:
None.
Reason:
A request to delete a default record failed. The default record may not be deleted.
System Action:
The request fails.
User Action:
None.
Reason:
A request to add or update a record failed because the SSIDB file is full. This message corresponds to a Packet Analyzer API feedback code of 28.
System Action:
The request fails.
User Action:
Delete one or more records, or reallocate the database.
The SSIDB file contains the following record types:
Reallocating the SSIDB
The SSIDB is permanently allocated to the SSI region and is included in the JCL (using the SSISYSIN member).
To reallocate the SSIDB
Note: Stopping the SSI region results in the loss of all historical data, such as TCP/IP statistics; therefore, we recommended that this occurs as part of a scheduled change management procedure only, for example, during an IPL.
Record Deletion
Obsolete records can be deleted using the administration facilities in your region as follows:
Use the /IPAPPLS shortcut to display the Application Name Definition List. Use the D=Delete action to delete any entries no longer required.
Use the /IPPKT.L or /SMART.L shortcut to display the SmartTrace : Packet Trace Definitions. Use the D=Delete action to delete any definition no longer required.
Use the /IPPAREQ shortcut to display the Packet Analysis Request List. Use the P=Purge action to delete any records no longer required.
Use the /FTADMIN shortcut to display the File Transfer : Administration Menu. Select option R - Maintain File Transfer Rulesets to display a list of rule sets. Use the D=Delete action to delete any rule set no longer required.
Reason:
A request of type P1 to the packet analyzer in the SSI region has failed because the SSI region is currently experiencing a short of storage condition. If P1 is OPEN or SNAPSHOT, the storage shortage is in the Trace Database. For other values of P1, the storage shortage is in the SSI region private storage.
System Action:
The request fails.
User Action:
Storage shortages are usually transient. Wait a while and try again.
If the condition persists, review the following:
To see the current SSI trace database size, use /IPTEST.
For Trace Database short of storage:
For SSI private storage shortage:
Reason:
A request to the Packet Analyzer in the SSI region has failed because of an incompatible Packet Analyzer level.
p1 identifies the Packet Analyzer level within the SSI.
p2 identifies the required Packet Analyzer level.
System Action:
The request fails.
User Action:
Ensure that the SSI region in use contains the correct Packet Analyzer level.
To see the Packet Analyzer level
This record displays information about the Packet Analyzer. The majorVersion and minorVersion fields contain the Packet Analyzer level.
Reason:
A Packet Analyzer request to the SOLVE SSI did not complete within a reasonable time. The SSID ( P1 ) and system ( P2 ) identify the SSI region where the request is issued to obtain or store data. This may be either 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:
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 Packet Analyzer map name.
P4 is the SSID that identifies the SOLVE SSI region.
P5 is the system name where the region is running.
P6 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 has failed because the SSI interface has not been defined (SYSPARMS SSID=NO).
System Action:
The request fails.
User Action:
Enable the SSI interface. To do this: * Display the list of Customizer parameter groups (/PARMS) and update the SSI group (from the INTERFACES section).
* Enter the SSID value that corresponds to the SOLVE SSI region that includes Packet Analyzer support.
* Action the parameter group and save the changes.
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:
Note: Only one SOLVE SSI region (per LPAR) can include support for the packet analyzer.
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:
A Check Expression call returned an error. This is an internal error.
System Action:
The request fails. More information is available in the &$FAData MDO.
User Action:
Contact CA Support.
Reason:
The CAS procedure $CAFK000 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 $CAFK000 terminates. Control is returned to the NCL procedure which executed $CAFK000. If executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $CAFK000. If executed from OCS, check the command entered on the command line and retry.
| Copyright © 2012 CA. All rights reserved. |
|