The following trace messages are produced by the CAICCI Component Trace.
Reason:
The requested STOP was processed by component.
Action:
None.
Reason:
The requested PAUSE was processed by component.
Action:
None.
Reason:
The requested RESUME was processed by component.
Action:
None.
Reason:
Trace ID traceid was deleted by component.
Action:
None.
Reason:
Trace ID traceid was either defined and enabled by component or had its status set to the enabled state.
Action:
None.
Reason:
Trace ID traceid was either defined and disabled by component or had its status set to the disabled state.
Action:
None.
Reason:
Trace ID traceid was modified by component.
Action:
None.
Reason:
In response to a STATUS command, component displays: if tracing is ON or OFF; if it is paused, YES or NO: if it is connected to an external writer, YES or NO; and the number of loss trace records.
Action:
None.
Reason:
In response to a STATUS command, component displays all the Event ID Groups that are defined to some Trace ID Set.
Action:
None.
Reason:
In response to a STATUS command, it was determined that no Event ID Groups were active for component.
Action:
None.
Reason:
In response to a LIST command, it was determined that no Trace Sets were active for component.
Action:
None.
Reason:
In response to a LIST command, component found Trace Set tttt defined; status is ENABLED or DISABLED; Count is the number of trace records recorded. If xxx is XAJ then JOBNAMEs and ASIDs in messages CAW4015I and CAW4016I are for exclusion.
Action:
None.
Reason:
In response to a LIST command, it was determined that no Event ID Groups were active for component.
Action:
None.
Reason:
In response to a LIST command, component found Trace Set tttt defined. The Event ID Groups are listed.
Action:
None.
Reason:
In response to a LIST command, component found Trace Set tttt defined with filtering on the listed ASIDs.
Action:
None.
Reason:
In response to a LIST command, component found Trace Set tttt defined with filtering on the listed JOBNAMEs.
Action:
None.
Reason:
In attempting to disconnect the external writer, component determined that a buffer needed to be written. The hexadecimal return code is displayed (even if successful).
Action:
None.
Reason:
A request to disconnect the external writer was received by component but the external writer was not connected.
Action:
None.
Reason:
A request to connect the external writer was received and successfully completed by component.
Action:
None.
Reason:
A request to disconnect the external writer (either explicitly or from a STOP) was received by component; the external writer has been disconnected.
Action:
None.
Reason:
An invalid parameter was detected by component. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
An invalid combination of parameters was detected by component. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
A request to create a new Trace ID was received by component but all available slots are in use. The request was not processed.
Action:
Possibly delete a defined trace id and re-issue the request.
Reason:
A request to create Trace ID tttt was received by component but a race condition resulted in another command created the requested id. The request was not processed.
Action:
Determine who created the trace id or choose another id
Reason:
A request to create a new Trace ID was received by component but there were no Event ID Groups specified. The request was not processed.
Action:
None.
Reason:
A request specifying Trace ID tttt was received by component but that id is not defined. The request was not processed.
Action:
None.
Reason:
An abend was intercepted by component. The system code is displayed along with the base address (module starting address) and the address of the next instruction. Message CAW4107E (multiple) will display the registers at the time of the abend. The request was not processed.
Action:
Collect diagnostic information and contact customer support.
Reason:
This follows message CAW4106E and will be repeated four times: rN0-rN3 = R00-R03, R04-R07, R08-R11, R12-R15.
Action:
Collect diagnostic information and contact customer support.
Reason:
A request specifying ASID filtering was received by component but the number of ASIDs exceed the maximum. The request was not processed.
Action:
Re-issue with fewer ASIDs.
Reason:
A request specifying JOBNAME filtering was received by component but the number of JOBNAMEs exceed the maximum. The request was not processed.
Action:
Re-issue with fewer JOBNAMESs.
Reason:
The parsing subroutine of component detected a parameter that was too long. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected an invalid parameter. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected a duplicate parameter. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected a trace id longer than 4 characters. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected an event id longer than 8 characters. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected that the specified event id is invalid. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected specified parameters conflicted. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected that a required parameter was not specified. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected that no action was specified. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected that the value specified for LIMIT was invalid. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
CTRACE for component was successfully started through either the “TRACE CT,ON,COMP=component” command or a parmlib member.
Action:
None.
Reason:
A previous “TRACE CT” command for component was still executing when this command was entered. This command was not processed.
Action:
Try the command again. If this error persists, stop the Component Trace (Issue “TRACE CT,OFF,COMP=component”) and then restart it. If the error still persists, contact customer support.
Reason:
In response to an EXTEND or RESET command, if component determines that the data space must be extended to support the request, it first displays the current data space allocation for its trace buffers in bytes and 4K blocks, followed by message CAW4404I.
Action:
None.
Reason:
In response to an EXTEND or RESET command, if component determines that the data space must be extended to support the request, it first displays message CAW44403I and then displays the needed data space allocation for its trace buffers in bytes and 4K blocks.
Action:
None.
Reason:
In response to an EXTEND or RESET command, if component determines that the data space must be extended to support the request it first displays message CAW4403I and CAW44404I, followed by this message. This message displays the number of blocks that the data space is extended to support the increased buffer quantity and/or size allocation.
Action:
None.
Reason:
In response to an EXTEND or RESET command, component determined that the request did not require an increase in the data space size; its current allocation is sufficient. This message displays the number of bytes that the last 4K block of the data space was extended to support the increased buffer quantity and/or size allocation.
Action:
None.
Reason:
In response to a RESET command, component first extends the data space, if necessary and then releases (i.e. clears) the entire data space. This message displays the number of 4K blocks that are released, which should be the current block allocation.
Action:
None.
Reason:
In conclusion to a RESET command, component first displays the current buffer size, the current number of allocated buffers and the current maximum number of buffers to which the data space could be extended for the given buffer size. This message is followed by message CAW4409I.
Action:
None.
Reason:
In conclusion to a RESET command, component first displays message CAW4408I followed by this message. This message displays the requested (i.e. new) buffer size, the number of allocated buffers and the maximum number of buffers to which the data space could be extended for the given buffer size.
Action:
None.
Reason:
In conclusion to an EXTEND command, component displays the requested number of buffers that have been added to the CTRACE buffer pool followed by message CAW4413I.
Action:
None.
Reason:
In conclusion to an EXTEND command, component first displays message CAW4412I followed by this message. This message displays the total number of buffers that are now available in the CTRACE buffer pool.
Action:
None.
Reason:
The parsing subroutine of component detected an invalid Event ID. Valid EIDs are any alphanumeric string up to 4 characters in length. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected invalid OPTIONS parameter syntax in the response to the CTRACE WTOR:
R nn,OPTIONS=(…)”. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected invalid RESET option syntax in the response to the CTRACE WTOR:
“R nn,OPTIONS=( …,RESET(#buffers,buffer_size),…)”. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
The parsing subroutine of component detected invalid EXTEND option syntax in the response to the CTRACE WTOR:
“R nn,OPTIONS=( …,EXTEND(#buffers),…)”. The request was not processed.
Action:
Re-issue the corrected command.
Reason:
One of the options (e.g., EXTEND) specified in the response to the CTRACE WTOR: “R nn,OPTIONS=(…) is not valid on the first issuance of “TRACE CT,ON,COMP=component” (i.e. until after the CTRACE data space has been created). The request was not processed.
Action:
Re-issue the command after the first issuance of the “TRACE CT,ON,COMP=component”.
Reason:
The response to the CTRACE WTOR: “R nn,OPTIONS=( …,RESET(#buffers,buffer_size),…)” specified a buffer_size that was less than 64 or greater than 8192. The request was not processed.
Action:
Re-issue the command with a buffer_size between and including 64 and 8192.
Reason:
The response to the CTRACE WTOR: “R nn,OPTIONS=( …,RESET(#buffers,buffer_size),…)” specified #buffers number of trace buffers. This value is greater than max_#buffers which is the largest number of buffers that can be allocated within a data space having a buffer size of buffer_size. The request was not processed.
Action:
Re-issue the command with #buffers having a value less than or equal to max_#buffers.
Reason:
The response to the CTRACE WTOR: “R nn,OPTIONS=( …,EXTEND(#buffers),…)” specified #buffers number of trace buffers. This value is greater than max_#buffers which is the largest number of buffers that can be allocated within a data space having the current buffer size. The request was not processed.
Action:
Re-issue the command with #buffers having a value less than or equal to max_#buffers.
Reason:
The creation of the data space during the first issuance of the “TRACE CT,ON,COMP=component” failed. The contents of R15 and R0 contain the pertinent diagnostic information. The request was not processed.
Action:
Ensure that the CAMASTER address space has been started and is still active. Otherwise, collect diagnostic information and contact customer support.
Reason:
The releasing of the data space that occurs during the processing of the EXTEND option has failed. The contents of R15 and R0 contain the pertinent diagnostic information. The request was not processed.
Action:
Ensure that the CAMASTER address space is still active. Otherwise, collect diagnostic information and contact customer support.
Reason:
The extending of the data space that occurred during the processing of the EXTEND or RESET option has failed. The contents of R15 and R0 contain the pertinent diagnostic information. The request was not processed.
Action:
Ensure that the CAMASTER address space is still active. Otherwise, collect diagnostic information and contact customer support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |