SVNET (Messages and Codes)


Number

Description

SVNET000I

ALL-NET RECORDER ACTIVATED

Explanation: The ALL-NET recorder has been invoked and is now processing.

User Response: No action is required.

SVNET001I

INVALID KEYWORD, IGNORE

Explanation: The option specified is invalid and ignored.

User Response: Correct error and rerun.

SVNET002I

NORECORD OPTION SET

Explanation: The option, NORECORD specified has been set.

User Response: No action is required.

SVNET003I

NODATA OPTION SET

Explanation: The NODATA option is in effect.

User Response: No action is required.

SVNET004I

DEBUG OPTION SET

Explanation: The option, DEBUG specified has been set.

User Response: No action is required.

SVNET005I

TEST OPTION SET

Explanation: The option, TEST specified has been set.

User Response: No action is required.

SVNET006I

SPIKES OPTION SET

Explanation: The VTAM ECSA spike simulator option has been set.

User Response: No action is required.

SVNET008I

RESETTING ALL NADRS

Explanation: The NADR data structure is used internally by Global Record to keep track of active VTAM sessions in the MVS system. This structure contains PIU discard flag. This flag is used when there was no Global Recording Request satisfying the capture of the session and the subsequent messages will not be examined any further. When new Global Recording Request is added or restated, this flag has to be reset. If the request contains wild-carded filter, we have to reset all NADRs and this message will be sent to the Global Recording tasks log.

User Response: No action is required.

SVNET009I

ALL-NET RECORDER SHUTDOWN ACKNOWLEDGED

Explanation: Received a shutdown request and start shutting down VTAM ECSA copier.

User Response: No action is required.

SVNET304W

HVCOMMON BUFFERS NOT LARGE ENOUGH, nnnnnnnn PIUS Lost SO FAR

Explanation: The PIU collection buffers are full and no empty buffers were available. nnnnnnnn represents the number of data streams lost.

User Response: If this message occurs only at Global Record startup, and no 3270 or APPC requests are active, ignore this message. Otherwise, complete the following steps:

  • Ensure the started task dispatch priority is below VTAM, but above all VTAM applications on the system. If WLM goal mode is active, dispatch rate is determined by the VELOCITY of the performance group. The IBM default group, SYSSTC, is a good starting point for most systems.
  • Access the Statistics panel from the Product Menu panel by issuing the primary command STATS; then access the VTAM panel by issuing VTAM on the command line. Use the information displayed on this panel to determine how to modify the Global Record capture buffer settings. If your traffic volumes vary throughout the day, turn on the statistics function to evaluate volume trends. See Performance Test Advanced Configuration Guide to learn more about monitoring traffic volume and optimizing Global Recording performance.
  • If you do not capture APPC traffic, specify ENABLE_APPC=NO (NOAPPC) in member HSCMnnnn from the common PARMLIB to reduce buffer utilization.
  • If you do not capture LU1/LU3 traffic, specify GLOBAL_RECORD_CAPTURE_LU1=NO (GRLU1CAP=NO) in member HSCMnnnn from the common PARMLIB to reduce buffer utilization.
  • If you do not capture LU0 traffic, specify ENABLE_LU0=NO (NOLU0) in member HSCMnnnn from the common PARMLIB to reduce buffer utilization.
  • If capture is on a production system, specify NFLS=NO (NONFLS) in member HSCMnnnn from the common PARMLIB to enhance buffer utilization and CPU usage.

SVNET401E

BUFFER OVERRUN, PLEASE CALL COMPUWARE CUSTOMER SUPPORT

Explanation: An error was detected in a PIU collection buffer.

User Response: Contact BMC Support. If possible, do not stop the started task; BMC support may be able to gather important debugging information

SVNET410I

PIU EXIT xxxxxxxx INITIALIZED AT yyyyyyyy

Explanation: The module xxxxxxxx was initialized at yyyyyyyy.

User Response: No action is required.

SVNET910I

MORE NADRS NEEDED

Explanation: The NADR data structure is used internally by Global Record to keep track of active VTAM sessions in the MVS system. The initial number of NADRs obtained is controlled by the MAXIMUM_3270_SESSIONS (SESSCNT) parameter. This message appears if Performance Test has to keep track of more VTAM sessions than are specified on the MAXIMUM_3270_SESSIONS parameter.

System Action: Performance Test tries to obtain additional NADRs.

User Response: Eliminate this message by setting a MAXIMUM_3270_SESSIONS (SESSCNT) value larger than the maximum number of simultaneous VTAM sessions on your system. For each occurrence of this message, increase the existing MAXIMUM_3270_SESSIONS value by minimally 25%. For example, if the existing MAXIMUM_3270_SESSIONS is 1000 and you receive three of these messages, increase the MAXIMUM_3270_SESSIONS to 1750. Setting an appropriate MAXIMUM_3270_SESSIONS value improves performance.

SVNET911I

MORE NADRS OBTAINED

Explanation: The NADR data structure is used internally by Global Record to keep track of active VTAM sessions in the MVS system. The initial number of NADRs obtained is controlled by the MAXIMUM_3270_SESSIONS (SESSCNT) parameter. This message appears if Performance Test has obtained additional NADRS to keep track of more VTAM sessions than are specified on the MAXIMUM_3270_SESSIONS parameter. If Global Record is not successful in obtaining more NADRs, this message does not appear.

User Response: This message appears after message SVNET910I, providing the system is able to obtain more NADRs. The action required to eliminate SVNET910I also eliminates this message.

SVNET930W

NULL VSBE DETECTED, BYPASSED

Explanation: During processing of a PIU collection buffer, an invalid PIU was encountered.

System Action: Processing of the related PIU collection buffer was halted.

User Response: Regular occurrence of this warning may indicate a serious issue and loss of PIUs. Contact BMC Support.

SVNET931W

HVCOMMON BUFFER HAS NOT BEEN FILLED UP YET.

Explanation: When a Global Record capture buffer becomes full, the Global Recording task empties the buffer. However, if the individual VSBE has not yet been completely copied, the Global Recording task displays this message. Then, it waits 1/100th second and re-examine whether the copy of VSBE has completed. If it fails after 100 attempts (approximately 1 sec), the SVNET932W message is displayed, and processing continues. If the SVNET932W message does not appear, the copy of all VSBE completed successfully.

 User Response: No action is required.

SVNET932W

HVCOMMON BUFFER MAY CONTAIN BAD VSBE(S).

Explanation: After checking for the completion of VSBE copy 100 times, VSBE copy had not completed.

User Response: Contact BMC Customer Support.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Performance Test 17.02