Trace initialization failed, R15=&1(X,X,4) R00=&2(X,X,4)
R15=0x00000024 indicates that a validation check of trace structures failed.
In R00=0x000000nn, nn has one of the following values:
4: Could not locate TCA
8: TCA version is unsupported
12: Requested trace component is unsupported
16: Could not locate TCAC eyecatcher
20: TCAC component name does not match request
24: TCA length is unrecognized
An attempt has been made to dynamically allocate a dataset to store VIP packet trace data. This message should have been preceeded by the following VIPOUT message:
VIP03200000MW DYNALLOC failed: R15=nn S99ERROR=nn S99INFO=nn
Verify that the IPTRxxxx parameters in the hlq.VIPINST(VIPPARM1) member are correct. In particular, verify that the user ID associated with the VIP agent is authorized to create a dataset with the specified prefix (IPTRCHLQ parameter – VIP IP Trace High-Level-Qualifier with a maximum length of 12) and volume (IPTRVOL parameter – VIP IP Trace Files Vol Ser Num for allocation).
Also verify that there is available space on the specified volume to create a new dataset.
Note: If the site has an SMS rule to handle the high-level qualifier specified by the IPTRCHLQ parameter, then specify IPTRVOL=******. The trace datasets will be placed on the volume specified in the SMS rule.
R15=0x0018 or R15=0x00000020, with R00=0x0030 in this VIP02050000ME message indicates that the user ID associated with the VIP agent task is not authorized to execute PKTTRACE commands. In that case the following message will also be logged in VIPOUT:
VIP00140000MI EZZ0059I MVS.VARY.TCPIP.PKTTRACE COMMAND FAILED: NOT AUTHORIZED
R15=0x00000020 and R00=0x00003044 indicates a rejected RACF check regarding MVS.VARY.TCPIP.PKTTRACE. VIP agents check RACF on the user’s behalf when the user requests a trace through either the VIP browser interface or a VIP batch job.