GSVX737E (MAIN) XMDS req 050D failed in ASID n/a, rc 00000010 rs 00000034 ec 00000000 00000000

Products

• SYSVIEW Performance Management

Issue/Introduction

I applied the z/OS 2.5 compatibility PTF-s and the prerequisites of CA SYSVIEW, and when I restarted the started tasks, I got the following message in the stc output SYSVIEW:
GSVX737E (MAIN) XMDS req 050D failed in ASID n/a, rc 00000010 rs 00000034 ec 00000000 00000000 

I found it in the Messages Guide, and it states that it is informational only.
If it is really not an error, but only an info message then why doesn't it end with letter 'I" ? Why ends this message ID with letter "E" ?

 

Environment

Release : 16.0

Component : SYSVIEW

Resolution

For the GSVX737E (MAIN) XMDS req 050D failed in ASID n/a, rc 00000010 rs 00000034 ec 00000000 00000000  error message, tuning of the cross system command timeout parms will have to be undertaken as described below: 

 

In SYSVIEW, display your parmlibs:

Browse the SYSTEM parmlib for the XSYSTEM member to view the timeout values:

This member tells SYSVIEW how long to wait for a cross system command connection. In this particular parmlib member example, the timeout is 5 seconds for a session and 15 seconds for a connect.

This cross system service will time out periodically when the system it is trying to access is running at maximum capacity.

This error is not an E level error despite the name because it may work fine a few seconds later if more resources are freed up on the system being connected to.   Thus it is considered informational only.  Rather a gray area on the E vs I message level in this case.

 

The recommendation from past timeout error messages with other customers is edit the XSYSTEM member to increase the timeout values in increments of 3 from the value that you have set in your xsystem parmlib member.  These are older notes so your timeout settings may be different.  Increasing them by 3 secs to find the best tuning spot to eliminate as many of the cross system timeout errors as possible is still recommended.

You may also want to check your SITE parmlib to see if the XSYSTEM member is there also and make the appropriate changes to the timeout parms there.